I'm sorry if this is a repeat thread, but I didn't see another thread mentioning this.
I used AGS 2.62 for Prodigal, and this is the first time I'm coding with the new command structure introduced in AGS 2.7. I haven't learned all of the new commands yet, so I NEED the context sensitive drop downs when I'm working on a script...but they don't always work! ARGH! This is really driving me nuts, because it makes something that would normally take me 2 seconds take 5 minutes as I then have to go into the help files and figure out what the command is. What is going on with this? Is this a bug, and if so is there a work around?
(It doesn't always happen, but every time I enter a script, it is a dice roll as to whether or not it'll work. Even if it worked in the SAME script 3 minutes ago, it may not work.)
Any help would save my sanity,
Trisk
It's working perfectly for me, so I suppose you're either doing something wrong or expecting too much.
Have you tried moving the cursor to the left and typing another period after the first keyword?
I find it mostly doesn't work when I've done something 'wrong' - if I've mispelt a pointer (e.g. cEog for cEgo) or tried to use a new pointer before saving the script, for example, it won't give the drop-down menu or auto-completes. Not getting the parameters for functions was the other big problem I had, but that seems to have been resolved.
Are there any commands that are more likely not to work than others? (In case it is a bug that just hasn't come up before.) Anyone else had/still having this problem?
OK, let's assume for the rest of this thread that I'm not a TOTAL IDIOT, so I'm not going to respond to the "standard idiot checks." :P
When it doesn't work it doesn't work. There is no rhyme or reason to it, but it will not type ahead for anything. cEgo won't be recognized, and the period after it brings up no drop downs. I can delete the word and retype it 'till my keyboard breaks, it won't ever recognize it, or any other keywords, ever. Furthermore, it'll work one time, then not work 1 minute later when I access the exact same script.
As a work around, I found that if I went to the "Edit script" window instead of the "interactions" window, it worked from there. I'm going to keep doing that and see if it solves the problem.
C'mon...somebody else must be experiencing this...?
QuoteAs a work around, I found that if I went to the "Edit script" window instead of the "interactions" window, it worked from there.
Yep, the autocomplete won't always show the list if you write the scripts via the Interaction editor. Probably, because not all the script file is parsed that way.
Personally, I always use the Edit Script method as it also allows to see the surrounding script code.