Script Editor Bug Reports

[Daniels & Mara]

1. Saying some "doesn't work" isn't really reporting a bug.
2. I need to know what system and version of everything you're running. This info is in your profile. If the system you're running is the same one that's in the profile, please say so.
3. I have to replicate the problem in order to fix it.
4. THEREFORE, tell me what you did that led up to the anomalous behavior of the Script Editor.

[Mike Kerner]

Shift-Clicking on objects to add them to a selection causes RR performance to grind to a halt.

RR 2.9.0 with GLX2 2.1b110. Click on first object. Shift-click on second and things start to grind. Shift-click on third and things are really crawling now. Shift-click on fourth and it takes ten seconds for the object to join the selection. Shift-click on the sixth and it's 30 seconds.

I have tried disabling the GLX2 status bar and the GLX2 Property editor but that doesn't cut it. I've also tried disabling the GLX2 props frontscript.

Disabling the GLX2 frontscript restores performance immediately.

[Mark Wieder]

Can't verify this. I just made a new test stack and grabbed eight radio buttons with and without the props editor open and can drag them around and change values without a problem. Any other frontscripts running? Anything that might be grabbing mouse events?

[Stephen Barncard]

This just cropped up for me. Since I use the vertical tab (VT) character a lot, I make it a constant like this

CONSTANT VT = " " ( invisible vertical tab character (DEC 11) pasted in from elsewhere)

But the GLX2 editor doesn't seem to like VT characters imbedded in scripts and thus changes it to a paren "(" and the handler that expects it will fail.

How do I do this? Constants can't be defined a compile time;

this won't work:
CONSTANT VT = numToChar(11)

So what to do?

1. Make it a global variable and define it on openstack (yuk)
2. put numToChar(11) everywhere the character is needed (redundant)
3. Use another editor (not a chance)

So how do we code as CONSTANTS such invisible characters in Rev with GLX2 on top?

IMHO VT should be a Rev constant anyway....

[Mark Wieder]

How about

function VT
return numToChar(11)
end VT

Not really a constant, I know, but probably as close as you're gonna come for the present. I filed rev bugzilla #1241 back in February 2004 for support of aggregate constants and it's still marked as "new". But I'd also be very wary of putting invisible characters in my scripts, even with a comment explaining it. But then, that's just me - lines of spaces for commenting creep me out, too...

local tEightSpaces = " "

[Stephen Barncard]

That function would have been my #4, but I forgot. Not optimal.

Another point of my post was to mention that this problem with the VT character by the GLX2 editor was not present in the Rev editor. And it must have worked in earlier versions of GLX, as I have done this VT thing in older scripts. Maybe Jerry would know some what to 'escape' some invisible characters in this editor.

[Mark Wieder]

...and "DEC 11" takes me back many years...

http://www.columbia.edu/acis/history/pdp11.html

[Éric Miclo]

Very funny bug:

1. place an object on a card
2. open its script in GLX2 Script Editor 2.2ß2 under Rev 3.0 (bug isn't there under 2.9)
3. place the insertion cursor between the beginning and ending command
4. press the Delete Key 2 times to delete the unique blank line and then the last char of the first lien

and then Rev quits without any warning!

The bug is not there in Rev's script editor.

[Mark Wieder]

Eric- it works fine for me here in both Leopard and XP. I tried it with all permutations of rev 3.0/2.9 and GLX2 2.1b119 and 2.2b2. Do you have some other plugin interfering with things?

[Éric Miclo]

Hello Mark,

I don't know what to say but this morning everything runs just fine.
Yesterday evening I could reproduce the bug as many times I wanted and upon several Rev sessions (only in verson 3.0) with no other plugin installed.
Very strange.

Best,

ÉrIC

[Mike Kerner]

2.2b4 using 2.9.whatever in win xp/sp3

I just created a new button, then tried to edit the script. GLX2 puts the cursor at the end of the on mouseUp line. So I down-arrow so I can actually add something useful to the script - but down-arrow doesn't do anything. I have to click on the 2nd line to add any code.

[Daniels & Mara]

Mike, I cannot get that one to replicate here. After clicking and typing some code, can you use the arrowkeys after that? Or are they permanently disabled?

[Mike Kerner]

They are NOT permanently disabled. It's just at the beginning when I'm trying to start adding code. So the cursor starts on the on mouseUp pMouseBtnNo line. Down arrow doesn't get me into the blank line. Clicking and editing then using the arrow works from there. I wonder if somehow the script editor is losing the focus.