AGS 3.1.2 SP1: Wrong script mistake marking

Started by Crimson Wizard, Thu 16/04/2009 00:08:01

Previous topic - Next topic

Crimson Wizard

Quite a small bug, but could be annoying sometimes.
In dialog scripts when there is a " ' " (apostrophe) symbol somewhere between "(" and ")" in character speech, as soon as I print ")", editor marks the ")" with a red colour as if there is some syntax mistake.

Example, that can cause this:

Code: ags

Ego: Okay, I will do this (actually I won't).

NOTE: you have to type ")", copy/paste doesn't reproduce the bug.


Also, just a remark: I found it a bit excessive that editor marks "(" / ")" pairs by yellow colour in character speech lines... only my opinion.

Trent R

Don't you know that the script editor is supposed to mark them yellow and red? Yellow means that the braces are matched, red is the opposite.

I do believe it would be nice if the dialog editor could recognize and ignore syntax text formatting like that, but I'd much rather have new features instead.


~Trent
To give back to the AGS community, I can get you free, full versions of commercial software. Recently, Paint Shop Pro X, and eXPert PDF Pro 6. Please PM me for details.


Current Project: The Wanderer
On Hold: Hero of the Rune

Khris

Quote from: Trent R on Thu 16/04/2009 01:22:54
Don't you know that the script editor is supposed to mark them yellow and red?
I'm pretty sure he does.
Like he said, the editor doesn't mark the closing brace yellow but red, as if there were a mistake.

Trent R

Ooops, sorry CW. I probably sounded a bit conceited before....

~Trent
To give back to the AGS community, I can get you free, full versions of commercial software. Recently, Paint Shop Pro X, and eXPert PDF Pro 6. Please PM me for details.


Current Project: The Wanderer
On Hold: Hero of the Rune

monkey0506

Although you probably do have a point that the dialog editor should have a better way of handling this (interpreting which lines are dialog script and ignoring all syntactical candy and which lines are script script (spaces first!) and detecting the appropriate information...).

Crimson Wizard

Quote from: Trent R on Thu 16/04/2009 02:55:10
Ooops, sorry CW. I probably sounded a bit conceited before....

~Trent
No problem :)

Quote from: monkey_05_06
Although you probably do have a point that the dialog editor should have a better way of handling this (interpreting which lines are dialog script and ignoring all syntactical candy and which lines are script script (spaces first!) and detecting the appropriate information...).
Well, that's exactly what I meant.

Pumaman

Yes, the problem is that the dialog script editor isn't yet clever enough to know how to distinguish dialog lines from scripting lines. It does need to be fixed but is not a priority as it's just a cosmetic issue.

SMF spam blocked by CleanTalk