There's actually a couple of really good articles on RBLibrary.com
that get into how to do registration algorithms and the like, and
then the article about creating a dictionary-based preferences class
pairs with it really well because it shows just how easy it (prefs)
can be. I keep a very obfuscated registration text file in one of
the special folders that RB gives native access to that gets read
when the app opens to tell it if it's registered or not.
But at least try the global mod.
Cheers
On Jul 30, 2007, at 15:23, Eric Richards wrote:
> Ahh.. ok.
>
> Yeah I have my class handling it all right now.
>
> I guess something could be done using files(i.e. pref's) but
> might be more trouble than its worth.
>
> Ok I'll try a Global Mod and see how it goes.
>
>
> Philip Regan wrote:
>
>> 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:
>>
>>
>
>
> _______________________________________________
> 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>
|