Possible bug

ScottMattes

Member³
My FindAll plugin is almost done, but I have a problem that I need clarification on.

When invoked, my plugin grabs the editor handle and uses that for the entire process. It use to only grab the editor handle when the user clicked on a found line, but if the topmost window wasn't the one that was topmost when the plugin was invoked it didn't do what was desired.

Now, after doing the search, I change which PLSD window is topmost and then click on a found line in my plugin, the topmost window AND the window that was topmost when the plugin was invoked change the current line in response to the plugin doing IDE_SetCursor.

I looked and looked and could not find an API call that gives the index number of the topmost window so that my plugin could always make it topmost first.

------------------
------------
Scott Mattes
 
I'm not sure what you mean, but the IDE_SelectWindow and IDE_ActivateWindow functions allow you to select a specific window (0 = top) or bring one to the top.

------------------
Marco Kalter
Allround Automations
 
Originally posted by mkalter:
I'm not sure what you mean, but the IDE_SelectWindow and IDE_ActivateWindow functions allow you to select a specific window (0 = top) or bring one to the top.


When I activate my plug in, how do I know which window is the top one? If the user brings up my plugin and then changes the top most PLSD window I want my plugin to bring the correct window to the top before changing the line pointer.

------------------
------------
Scott Mattes
 
Back
Top