What does it mean?
Ok. Can anyone put that in English? 
It is in English! I believe the question you’re looking for is: “Why am I getting this error?”
(Hint: You might also want to supply some more information, such as what was going on when this error occured, if there was a specific line causing the error, etc.)
its for my lyrics grabber…usually its when its trying to get lyrics…but it does it somewhat sporadically…it doesn’t really affect the program though…like sometimes it finds the lyrics then i shows the error but then it keeps running normally.
hendo13, you should consider the way in which your posts are perceived by others before you potentially drive people away who might actually help you. Perhaps you might put some thought into what you’re asking of us, and maybe even put a little work into your own projects before trying to get us to figure it out for you. How on earth could we possibly make any assumptions about what you’ve messed up in your app without having it in front of us… without even having a brief portion of it’s code to look at?! Errors and crashes happen for SPECIFIC REASONS, not just at random. Telling us that it’s “when something is happening” or, “when I click a button it doesn’t work…” doesn’t give me ANYTHING to work from. In fact, I don’t really care what your app DOES, but I’m willing to try and help figure out why it doesn’t do whatever it is that it does when you don’t seem to know what your doing… as long as you help me to help you. As bruce says, the error and it’s definition ARE in english, and they’re all you get.
The next step is for you to learn to be an insightful programmer… which means that you need not only to learn to write good code, but also how to recognize BAD code. As bruce also says, we need CODE. Not all 500 lines of ALL of your code, either! :mad: You may find some people here that will actually read all of your code and try to help, but if I come across a post with hundreds of lines of code, I don’t bother to read past the first two or three. If you’ve not picked apart your own code to try to find the problem, why the heck should I bother? You know your code more intimately than any of us, and it SHOULD be easy for you to find the problems. If you’re working on a particular section, and then you run it and get an error, you’re probably going to find the problem in the code you just updated. Generally, making radical changes in multiple locations is not good style, and just leads to troubleshooting nightmares. Just take it one step at a time and build/run often.
Try commenting out lines… all of them in the problem block, actually… except for the key ones that are part of handlers and necessary to the operation of the app. Then, uncomment them one-by-one until you find the problem line(s). Applescript works linearly, meaning that code starts executing from the top and ends when it gets to the bottom. Get in the habit of placing log messages before and after suspected bad lines of code, so you can see if errors appear in certain lines or routines. Pay attention. You don’t seem to have any clue where the errors are originating from. There must be something triggering them… something finite… because computers don’t just spit out crap at random. As much as we’d like to think that our machines are out to complicate things for us, they really don’t care. If something’s going wrong, it’s your fault… making it your responsibility to reconcile. Applescript is really easy to troubleshoot if you just sit and think about it for a minute.
I’m sorry if this seems harsh, but it’s reality. I’ve said it before and I’ll say it again… most of us are here by choice. I choose to come here and help YOU… because I want to and because I can. But, I don’t have the entire applescript terminology memorized, and I don’t have a built-in compiler in my head. I’m also not a mind reader, so post some code and put in a little intelligent effort before having such grand expectations of US.
I am “compensated” for my time only by what you choose to put in in terms of assistance and appreciation, and by the satisfaction of helping out. If that payoff is compromised, I’ll find it difficult to give your needs a second thought.
j
did it ever occur to you that I am still extremely new to Applescript, and when it comes to finding errors, I just don’t know where to start? I admit I am a horrible programmer trying to get better, but we all have different learning styles. I learn by example, by people showing me. This is how I learn things. I mean, you don’t need code for everything. If someone said I am getting an NSRecieverEvaluationScriptError automatically you know they are referencing something wrong, or have made a spelling mistake or have forgot to check something off in IB. It doesn’t matter what their code is you just know without having to look at their code (although sometimes it helps) All I was asking is why do you generally get these kinds of errors? What tends to cause them. I did not realize that these kind of errors are very specific, so I am sorry for all you experienced people out there who have to listen to noobs ask questions, because they don’t know what errors are what. I appreciate all the help everyone has ever given me here, and I feel bad having to constantly post stupid questions, but I have one eat that is really bad o mix with programming…impatience, it’s who I am I can’t help it I am extremely impatient. Maybe that is why I so quickly ask for help here. I will stop bothering everyone in the future.
No, you asked: “What does this mean?” Also, I had never heard of this error before, but a quick search turned up the actual meaning of it.
Did it ever occur to you that you can ask? 
meh, i just gave up on it. didn’t have the patience for it.
Come on hendo13, where’s the fun in that? 
the fun is gone…i’m not a good enough problem solver to program. It almost makes it stressful.
No one asked for that, but if you’re unwilling to listen to the needs of others then perhaps that’s best. I think it should be obvious though, that despite our criticisms we keep offering you our help. The regulars here enjoy your patronage, and understand that it is your participation that keeps this ball rolling.
Who ever said programming was supposed to be fun!?
Seriously, it sounds like you need to turn that frown upside down. Software development is hard, and unless you want to have a whole hard drive full of “hello world” apps, you’re in for a wild ride every time you decide to let your ambitions run wild. I have applications that I’ve been developing for years, and have yet to release publicly. This sh*t takes time and a considerable amount of energy, but it’s all worth it in the end… especially if you intend to write software for an end user other than yourself.
For more than two years I’ve spent a great deal of time answering questions here at macscripter. When I first came here, I knew nothing about applescript. In fact, I’ve been using macs since the mid-80’s and I never until a few years ago realized discoverd how versatile applescript makes a machine. And then :o I found applescript studio. Finally my dreams became reality. Now I consider myself to be quite familiar and comfortable with applescript… and I’m getting better writing in objective-c every day. But I didn’t get that way because I have a long history in programming. I didn’t read any programming books, and I’m not a retired computer engineer. I’m just a guy who likes to develop my own software, and I learned by motivation, intuition, and lots of first-hand experience. Finding answers about these questions is hard, in fact you sometimes just have to write your own answers. But it’s the journey, not just the destination that makes it all worthwhile. If you’re not a good problem solver, then look at this as your call to learn to become one. Google is your friend, and the archives of posts here at macscripter is second to none. The apple docs, some “other” applescript websites out there, and the sample projects that came with the developer tools are also very valuable tools if you take the time to familiarize yourself with them. Everything I ever wanted to learn about applescript studio I found on the internet. It’s out there, you just have to get smart about how and where you look for it.
One thing that never got me where I am is impatience, though. To you, your zealousness is probably envigorating and drives you to learn quickly. Your “noobiness”… while sometimes an obstacle in communicating our points… is ultimately a trivial factor in why we help you. I’m well aware of what level you are at with your scripting abilities, and I don’t care about that. I give and receive help with development to many people, some below and some well beyond my abilities. The common thread that all of my good working relationships with other developers share is respect. While you may not view your actions as disrespectful or offensive, others may get uncomfortable working with you because you don’t seem to be putting in what you’re getting out. I’ve had this conversation many times before, and I’m not interested in playing a check and balances game with you or anyone else. I don’t expect to be able to contact you and have you help me to solve my problems or give me insight into my obstacles. If I did, though, I would expect you to contribute to the best of your abilities. Likewise, when I am able to help you, I do so gladly and in good faith.
I would NEVER encourage your decision to stop asking questions or to run away from macscripter. This is one of the few places I consider to be a “second home” and I value the relationships I have with all of the other members I come into contact with. I only ask that you dispense with the impatience and wade through the muck like the rest of us have. The fast track is rarely the best track, and finding ways to find your own answers will not only save you time and aggravation, but it will illustrate to us that you are deserving of our respect as our peer. This will be the last long-winded post I write about this (for a while anyways 
). I’m not trying to scare you away, but rather to impress upon you (and a few others) how important your perception of our responsibilities to you as your peers truly is. All of the contributors at macscripter could offer you a great deal of assistance and guidance, and I encourage you to listen to their needs. Being familiar with the Posting guideleines is a good start. The golden rule is generally the best rule, and I’m happy to respect you if you’re willing to do the same.
Take care, and stick with it…
j
I am just a 16 year old kid, that started programming, because i thought it was cool. I developed one ok app (Play MiniTunes.) that I relased on MacUpdate. I see where your coming from, and I understand. Thanks for helping me. Maybe I’ll open source this particular program (if ican’t get rid of that error), and just let other more experienced people make it the best program it can be.