If I'm reading what you've done correctly, you should be handling
*all* of your registration information in a global module so that all
of your classes call to that one object to see whether or not the
proper key was put in place, as opposed to keeping in a class, which
like you said, can have more than one instance. The class instead
would have a simple "DemoMode" boolean property that gets set by a
quick "CheckMode" when the object is created. Does that make sense?
On Jul 30, 2007, at 08:21, Eric Richards wrote:
> Hi -
>
> I have a Registration key thing set up in a class. Everything works
> fine, however for every instance of it the user would have to enter
> the
> "key" info. Since I don't think a user would have many instances
> of it, its not a big deal, but there has to be something better.
>
> Any ideas on how to have each instance check/know that it has a valid
> "key" but only setting it once ?
>
> Thanks
>
> Eric
>
>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
--
Philip Regan
http://www.oatmealandcoffee.com
Mac OS 10.4.9, RB2k7r3
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|