Hi Dave, this really is a "hard fact" assuming I will never have same object names as others, what is less risky, living in germany :) Thanks for reminding
Tiemo -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Dave Cragg Gesendet: Freitag, 22. Juni 2007 13:14 An: How to use Revolution Betreff: Re: Best Practices using globals vs. custprops? On 22 Jun 2007, at 09:50, Tiemo Hollmann TB wrote: > I really don't see any difference between using globals or properties > yet. Scott pointed out some of the problems of using globals. One particular problem in Rev is that we can easily share stacks with each other. If you use someone else's stack (as a plugin, a library, or as part of your application), and if there is a global in that peron's stack that has the same name as one in your own stack, unexpected things are likely to happen. That is why it's usually advisable to use some kind of naming strategy for your globals. For example, start all gloabls with "g" plus your applications name. gMyAppUserName, gMyAppUserID, etc. But that's only reducing the risk of name conflicts; it doesn't remove it. Custom properties don't have this problem as thy are tied to objects (stacks, cards, etc.) therefore it's OK to have custom properties with the same name. (the userID of stack "myApp" versus the userID of stack "herApp"). Cheers Dave _______________________________________________ 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
