Actually, I thought of a serious answer to this dilemma.
I was thinking of putting a "-- pass [sys msg name]" in every blank
system message handler Constellation creates. That way the user could
un-comment the "pass". Like Chipp, most of the time I find the "pass"
in a default handler unneeded.
The other approach is to include a pass on those system message
handlers where it is likely to be needed--those being the ones that
the Rev IDE counts on your passing, in particular.
Jerry
Buy Constellation from Runtime Revolution!
http://revstudio.runrev.com/section/revselect/constellation/
On Mar 17, 2006, at 1:37 AM, Chipp Walters wrote:
Yep, I'd prefer Constellation not place a 'pass' automatically in
handlers. I'm sure Jerry will add it as a preference some day :-)
-Chipp
But, you gotta love the tabbed browsing AND the GREAT debugger
which doesn't flake out for no apparent reason. Jerry's told me
he's worked really hard on making the debugger as robust as
possible..and it shows.
Thomas McGrath III wrote:
That is correct. I finally see how powerful Constellation is in
my work flow.
On Mar 17, 2006, at 12:22 AM, J. Landman Gay wrote:
Thomas McGrath III wrote:
The reason I ask is that when I insert a new command it throws
in a pass with that commands name by default.
This isn't native Revolution behavior. Are you using Constellation?
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
