Hi Mark,

As Al says it has been my experience that users very rarely read the messages 
when an error occurs, I always used to key in second level text to explain 
exactly what went wrong(or as close as I could) now I seldom bother as the 
users first reaction is normally to hit cancel followed by picking up the 
phone. I use a *MSGF file whenever I can (call me old fashioned if you will  
:-) Although I have recently just been adding constants in some programs and 
outputing to a field in the display, saves the users having to press reset, 
they get tired pressing too many keys. :-) (apologies to any users who may be 
watching)), however I am confused as to what these 500 messages are that you 
are refering to. Are these to catch errors/miskeys etc. in the project you are 
developing? If so then if you don't key them in 1 by 1 in relation to the bit 
of code you just added or changed then isn't some "power tool" going to be even 
more generic than the *MSGF, how will it be able to say exactly what you want 
it to say without some manual intervention by you? 

I also agree with Al about the multi-lingual functionality of *MSGF, what could 
be easier? And if some "power tool" does exist how much will the damn thing 
cost to cover all the languages that may be required?

My two ha'porth anyroad.  :-)

Steve

-----Oorspronkelijk bericht-----
Van: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]Namens Mark Villa
Verzonden: maandag 24 juli 2006 16:50
Aan: midrange-l@xxxxxxxxxxxx
Onderwerp: Do you still use *MSGF exclusively?


I know that folks have put message files in data files by key, that is
nice for certain cases.
If you use *MSGF do you sit and type them 1 by 1, or do you use a
"power tool"  for heads down entry of the 500 messages in front of
you?
 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.