Umm yeah, orignaly I had the class doing it all. Then I changed that by
putting the key stuff
in a global mod. (now the class doesn't handle the key, just checks.)
I did have something along these lines, in the Window.open event
GlobalMod.key = "ummm....doughnuts.."
GlobalMod.name = "d'oh"
however It didn't work there. So I moved it to the very first instance
of my class and put
it in it's open event and it worked and other instances seen it as
valid, even though
it was just in one place.
I just tried it in the App.open event and it works as well.
I guess it would be up to the developer, to some degree, as to where to
put the
"key" stuff. If you just have one instance of the class then, in its
open event, would
seemed to be a good place for it.
I don't think there is away to "force" someone to put the key stuff in
the App.open,
instead of and instance, though I could be wrong.
rblists at oatmealandcoffee dot com wrote:
>I think you might be muddling things by having the class actually set the key
>each time a new instance is created, when you might really only need it set
>once. The key could be set in the App.Open event and then the classes check to
>see if the key is correct when they're created. If you absolutely must have
>the class set the key, then you could have it check to see if a key has been
>set in the global module first, and if it hasn't, then enter the key. If the
>key has been set, then check to see if the key is correct and take the
>appropriate course of action.
>
>HTH!
>
>
>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|