Am I missing something in Version 3.0

no1g8tor · Post by **no1g8tor** » Fri Oct 17, 2008 4:36 am

When I watch the Video of new features, it demonstated that you would be able to click on a handler or function in one script and it would open up the script that has it in it. When I try it, nothing happens unless its in the same script.

Am I doning something wrong? Is there a preference setting I need to turn on.

This was on of the highlights I was looking forward to in the new version.

Thanks

Mark · Post by **Mark** » Fri Oct 17, 2008 8:27 am

Dear no1g8tor,

How did you find this video? I don't think I have seen it myself.

Best,

Mark

SparkOut · Post by **SparkOut** » Fri Oct 17, 2008 9:54 am

http://www.runrev.com/whats-new/product-overview/

on the top right is the video for the script editor and debugger. At 3:15 into the video it indicates that you can right-click a custom definition and "go to definition" where the editor will open a new tab with that handler's script.

The option to right-click and "go to definition" is greyed out for me too, unless the handler is defined in the same script.

This is on Windows (XP).

Mark · Post by **Mark** » Fri Oct 17, 2008 10:11 am

You're right, Sparkout and no1g8tor, same here. Seems to be a bug. I believe this needs to be reported to the QCC.

Best,

Mark

Tim · Post by **Tim** » Fri Oct 17, 2008 10:26 am

Hi all,

I was trying this too and could not get it to work. However, after talking to Oli (chief architect of the new script editor) I know what I was doing wrong. If the handler that you are trying to "go to definition" is NOT in the message path then it will not be selectable --- i.e. the menu option is greyed out.

To test this I had 2 buttons. One with a function "foo" and the other called "foo". If I right clicked on the "foo" call in button 2 the "go to definition" was greyed out. But as Oli pointed out to me, this is because the "foo" command in button 2 is not in the message path for button 1 ...

Moving the "foo" command into the stack script sorted this.

He did however point out a known bug. You MUST have mouse focus in the handler you are trying to find - i.e. you must have the caret inside "foo" in this example.

Anyway,

I hope this helps and you are able to get this feature working for you.

Best Regards,

Tim

Mark · Post by **Mark** » Fri Oct 17, 2008 10:33 am

Hi Tim,

No, it doesn't work with libraries.

Best,

Mark

Tim · Post by **Tim** » Fri Oct 17, 2008 12:26 pm

Hi Mark,

If you are trying to get it to jump to the definition of things that are part of the IDE libs then you need to set gRevDevelopment to true.

Best.

Tim.

Jerry Daniels · Post by **Jerry Daniels** » Fri Oct 17, 2008 1:52 pm

Linking to handlers that are part of libraries works in GLX2 Script Editor. The linkage is made apparent by using the link style. Italicized links indicate the handler is outside of the current script.

This feature has been part of Galaxy and GLX2 for a couple years now and it works well.

Mark · Post by **Mark** » Fri Oct 17, 2008 3:50 pm

Hi Tim,

I just wanted to make it "jump" to a handler in my own library, after I removed its password. It doesn't work.

Best,

Mark