2009/9/18 Richard Gaskin <[email protected]> > > Using "the long if" works with all objects, and in my experience this > easiest-to-obtain form consistently provides reliable results. >
There is a case, where the long id stops working which was intoduced since 3.5 and behaviors. Though I have not had time to track down the cause. I have filed it here <http://quality.runrev.com/qacenter/show_bug.cgi?id=8014> : It totally baffles me but sometimes "the long id of the target" fails to convert an object reference form the form "control id 1234 of stack XXX" - I've set a breakpoint in a crucial handler so I can clearly see the script and variables when it fails - but can;t reproduce it except to note it only happens occasionally with this behavior type reference. Anyway... What would be the ideal solution to make short and long IDs of stacks most > consistent with the rest of the language? I'd go for returning the short name of the stackas equivalent to a unique "id" of an object - unless there is a use for the current id (number) returned. _______________________________________________ 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
