|
Larkin Wizard
Joined: 25 Mar 2003 Posts: 1113 Location: USA
|
Posted: Tue May 13, 2008 5:57 pm
[2.25] Don't double-click a variable in another package |
I wanted to see exactly where a certain variable was located while editing a trigger in one of my packages. I double-clicked it in the Scintilla editor window. My tree selection changed, but it didn't take me to my variable.
1. Open untitled session.
2. Create variable with some value (in the untitled package).
3. Create new package with an alias that uses this variable in some way.
4. Double-click the variable in the Scintilla editor frame.
My PE sometimes gets very confused as to what I'm clicking on after this occurs, though it's not consistent. |
|
|
|
Larkin Wizard
Joined: 25 Mar 2003 Posts: 1113 Location: USA
|
Posted: Thu May 29, 2008 4:49 pm |
Just want to bump this, as it seems to have fallen very far down the list of threads while Zugg was away.
And, since I can't find a thread on it, I'll just briefly mention here that I still see the issue where I open the PE and see the "Lusternia" tab selected and the contents for one of my added auxiliary packages is what's really showing below... |
|
|
|
Zugg MASTER
Joined: 25 Sep 2000 Posts: 23379 Location: Colorado, USA
|
Posted: Thu May 29, 2008 4:57 pm |
Thanks for bumping this...I had completely missed it with all of the other threads. I've added it to the bug list.
|
|
|
|
|
|