I've spent days on my tiny script with a heck of a lot of help from Al and Alex. Just when I think I've got one problem sussed, a bit of code that has been working perfectly all along suddenly, without any change in that part of the script stops working.

I don't know whether it's me or the program but since I haven't done anything . . .

I feel as if I've wasted my time and everyone else's as well

Frank

Hi, Frank

I've been watching your posts, as well as the replies given. My advice is, if you have the time to devote to it, don't give up. Alex, and the other guys here on this forum have been very helpful and don't seem to mind questions from people who are trying. Of course, those who ask questions but don't put any effort into learning are a little tiresome. I'm still a beginner with Quest myself (see my earlier posts), but have gotten a lot of great help from members of this forum.

Anyway, that's just my opinion.

Hi Frank

I've spent days on my tiny script with a heck of a lot of help from Al and Alex. Just when I think I've got one problem sussed, a bit of code that has been working perfectly all along suddenly, without any change in that part of the script stops working.

I don't know whether it's me or the program but since I haven't done anything . . .

I feel as if I've wasted my time and everyone else's as well

Stick with it Frank! Sometimes the reason why something doesn't work is down to a seemingly innocuous unrelated change elsewhere in your script and this can be extremely frustrating experience - but then programming does tend to be like that. Once you get your head around the way the whole thing hangs together you'll find you get a better feel for where to look for the problems, but that takes time and a lot of practice.

QDK might shield you from the typing side - but you are still doing programming whether it is obvious or not.

You'll also find that programs are never perfect and some errors just have no logical reason that you can see. As you know Typelib 'threw a wobbly' on the de-aliasing of indirect objects in a player command - I never could see why that happened, I just erased the function call which had worked perfectly in the past, retyped it exactly as before and then it worked again... Has to have been some corrupted bytes in typelib. Quite why it surfaced then is one of those mysteries of programming life.

You suffered from the corruption in my version of typelib because I e-mailed you a version from my PC if you recall, so that extremely frustrating wierdness really wasn't down to anything you did at all.

"Getting over the hump" of learning enough to have your first piece work as you want is the hard bit, the trick is to not be over ambitious and finish something really simple first - it does wonders for your confidence and then you can go back and 'improve' it, knowing that you are starting with something you know works!

Al (MaDbRiT)

I wouldn't worry about annoying people by asking questions about how to do this or that. That's the sort of things these forums are for.

We all get better some way. I learned most of it from reading manuals extensively while coding (any language). I asked my share of questions too. If you have problems and you don't ask questions then it's much harder to find the answer.

Persistance rules. If you keep at it, you will eventually finish it. Don't be discouraged by problems that might keep reappearing. If you download the latest version of MPlayer at winsite.com (search for MPlayer, it should be listed under Music Player in the first few lines), you'll see that there are many bugs in that program. I wrote it, and I've kept going, even though I must of had at least 100 problems so far.

I'd just like to mention that I haven't gone away entirely. I'm lurking in the background while trying to write my adventure in other systems. Once I'm sure I know what I'm doing I'll be having another go at getting it working in Quest.

I appreciate all the help and encouragement this forum, especially Alex and Al, have given - not all systems have a community as alive and helpful as this one!!

Frank Lane

that's what we're here for

EagleWing wrote:not all systems have a community as alive and helpful as this one!!

Frank Lane

depends what you're after really

[deleted another seemingly pointless list of links from our good friend "slippy" - Alex]

Slippy obviously has a lot more time than I have!

slippy wrote:[deleted another seemingly pointless list of links from our good friend "slippy" - Alex]

Alex pwnz j00 slippeh

i'll say. I've never known such odd behaviour

007bond wrote:i'll say. I've never known such odd behaviour

I've known worse, if you get me