Peter Haworth wrote:
The problem is, I'm probably going to need a front script anyway because
plugins don't get revxxx messages for all the events I need to know about
(e.g., the creation/deletion of a control). Not sure why the revxxx
messages are quite so selective.
I'm also running
Good to hear. I always get concerned that I might be going in the wrong
direction when I discover a new way of doing something that duplicates an
existing method. I already have fornt scripts in place so will stick with
them.
Pete
lcSQL Software http://www.lcsql.com
On Wed, Aug 15, 2012 at
I've been told my IQ is probably as high as my age, so I guess I'm almost half
smart!
On Aug 15, 2012, at 8:59 AM, Richard Gaskin wrote:
Noble as that goal may be, this is a development tool; it not only plays by
very different rules given its radically different nature, but its audience
I'm confused about the purpose of these messages. As an example, consider
the revPreOpenStack and its equivalent preOpenStack
If I register my plugin to receive revPreOpenStack messages, then I get
that message when any stack is opened in the IDE which is great but is
there any advantage to
On 8/14/12 8:23 PM, Peter Haworth wrote:
I'm confused about the purpose of these messages. As an example, consider
the revPreOpenStack and its equivalent preOpenStack
If I register my plugin to receive revPreOpenStack messages, then I get
that message when any stack is opened in the IDE which
Thanks Jacque.
The problem is, I'm probably going to need a front script anyway because
plugins don't get revxxx messages for all the events I need to know about
(e.g., the creation/deletion of a control). Not sure why the revxxx
messages are quite so selective.
I'm also running into issues
