Larger Or Expandable Window For Quick Sequence

[SteveMyres]

My lines often scroll offscreen in a Quick Sequence editing window.

So it would be cool to have the option to expand the window like you can with F6 for expressions, or a stretchable window.

It would be even nicer not to have to do it every time, so just start it out big, or maybe allow the user to stretch it larger or smaller and remember the stretched size the next time that dialog is invoked. That way a user could set it to match his coding style as well as for things having to do with the current project; monitor size and so on and it would stay until he needed to adjust it for some reason.

Thanks!

[AzeoTech]

This is just a workaround: don't put the code in a quick sequence. Make a sequence and simply call it from the quick sequence (as a function). If you are worried about having too many sequences to manage, create a class to hold all your events and then just instantiate it once. Something like:

class CEvents
function MyComponentClick()
//.....
endfunction

etc..
endclass

global Events = new(CEvents)
[/CODE]
Then in the quick sequence, put:  Events.MyComponentClick()
You'll have to come up with a naming convention.  Feel free to create several different objects do group your events, say one for component events, one for channel events, etc, or one per page.  Its up to you.
There are a couple advantages of doing it this way, including of course that you get a better editor: you can edit multiple events from one screen, which is very useful if they contain similar code.  This will also possibly lead to you using a single function, probably with parameters, that can handle several events.  
Note that typically you'll put the instantiation code in a startup sequence instead of in the sequence with the class.  You need to run the sequence with the class before instantiation, but there is no reason to keep reinstantiating.  Every time you change a function in a class, all you need to do is run the sequence with the class declaration to get the function to update in all instantiated classes.  Of course if there is a thread currently in that function, the function will need to return first before being changed (the same as with a sequence).  Not reinstantiating allows you to maintain state of your objects, assuming you have member variables.

[SteveMyres]

Good idea. I had thought of replacing the QS's on a one-to-one basis but as you noted that seemed very messy. This approach you outlined looks promising though. Even if there were a better editing window at the component level, I might actually prefer this approach. You can see all the code at once, very quick to duplicate analogous components that perform the same function on different variables, etc.

Thanks!

[AzeoTech]

Plus, you can open that code in a modeless separate window and leave it open at all times. Especially nice if you run multiple monitors.