Richard,
You may have not doubted my code, but I did! Rev was not the culprit
here, it was my code that triggered an untimely exit from the
editBackground state which in turned triggered the reselection and
delete of the group.
In any case: problem diagnosed, fixed, tested and ready for users to
download via GLX2 Help menu.
Thanks to Mark Swindell and others for their report and for Sarah for
her help with the code and alerting me to the anomaly in the first
place. I was busy doing project work when Sarah let me know we had a
"bogey" comin' in at 2 o'clock.
Best,
Jerry Daniels
Daniels & Mara, Inc.
Makers of GLX2
http://www.daniels-mara.com
On Oct 8, 2007, at 7:21 PM, Richard Gaskin wrote:
Jerry,
I never doubted your code for a second. On the contrary, my
question was why does the *Rev IDE* do all the extra twists and
turns with the delete when the engine's native behavior is just
fine as it is?
1. It turns out that after deleting an object in a group, Rev
switches to non-editbackground mode and reselects the group.
2. At that point a secondary delete key message is sent and
the entire group is deleted UNLESS some code intervenes and
stops it!
--
Richard Gaskin
Managing Editor, revJournal
_______________________________________________________
Rev tips, tutorials and more: http://www.revJournal.com
_______________________________________________
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
