Trap Valentina license time limit

[Barry G. Sumpter]

Hi Thorsten,

Thanks again for your replies.

In the context of a public news list, I'm not just asking for myself but
hoping to get a simple example and get help in improving it to make it a
standard that everyone could use if they choose to.

Again, not looking for someone to do it for me.  But to get me started in
the right direction. Etc.

I see the logger class as the server error trapping.
Bit silly having a dialog with an OK button when no one is sitting at the
server keyboard. LOL 

The dialog box would be for the user to find out that database can't process
The transaction because the licences number used is for Valentina v1.1 and
NOT for Valentina v3.1 or the server is not longer running, etc...

I'm maintaining Valentina legacy code v1.1. and porting some to v3.1 and
discussing how to handle Valentina errors here.
So this is the right place.

Its funny because the RB-NUGs tell me to come here if I mention Valentina at
all.  LOL

Anyway, all the best,
     Barry G. Sumpter 


-----Original Message-----
From: valentina-bounces at lists.macserve.net
[mailto:valentina-bounces at lists.macserve.net] On Behalf Of Thorsten Hohage
Sent: Saturday, 7 July 2007 5:29 AM
To: Valentina Developers
Subject: Re: Trap Valentina license time limit

Hi Barry,

On 2007-07-06, at 19:26, Barry G. Sumpter wrote:
> Hmm, I wonder, does anyone have a methodology for a professional  
> standard
> error trapping routine?

Yes, I've got one. But what does this answer does help you? I'm  
afraid not much. When asking if I can provide you with code, then the  
answer would be disappointing, too. Because this code is so much  
integrated in my basic framework, that you need to use if fully or  
reject it.

So I'm afraid I'm not able to provide you with code here.


> Where the DialogBox has options to Log the error to a file, send an  
> email to
> product support, ignore, or terminate execution, etc.

I wouldn't go the way to extend a DialogBox to do i.e. logging. There  
are many situations where the GUI is already frozen, but code is  
still executable. I'll go the other way, write you a logger class, so  
you're able to handle different logs and logging styles (i.e screen  
logging, file logging, message logging for serious bugs) and open a  
dialog box out of this logging class or separately after.

Even more there are several situations in REALbasic, where a modal  
dialog box will change the way of code execution completely.

But IMHO these are questions that should asked on the RB-NUG or on  
the RS-Forums.


regards

Thorsten Hohage
--
objectmanufactur.com - Hamburg,Germany


_______________________________________________
Valentina mailing list
Valentina at lists.macserve.net
http://lists.macserve.net/mailman/listinfo/valentina