popup update * show statements

John Esak john at valar.com
Fri Jan 8 18:46:30 PST 2010


Richard,
Unfortunately, I think you have run into one of the difficulties with
original filePro design. You can get around it, but only with a hammer.  I
started using this hammer about 10 or 15 years ago and I've never looked
back or done it any other way ever since. You need the -d on your command
line. In other words by putting the -d on the calling line filePro "doesn't
display" (is the best mnemonic I can think for it) all the default prompts
at the times it normally displays these.  I know you've probably used the -d
a lot, but the times you don't that old behavior creeps up and hits you when
you least expect it.  There is only one drawback to using -d, and that is
*you* must provide all the prompts yourself... And that entails taking down
prompts that are on the screen when you want a new prompt.  It all becomes
second nature after a while, and your programs are SO much more usable since
at every point the prompt and the keys available can be displayed precisely.
I am absolutely anal about making sure this is always correct. In other
words the user of my programs will never see a highlighted key-prompt if it
won't work. In other words if I popup a screen and there are prompts for the
screen under that popup which are not appropriate for that popup, I take
down the old prompt and put up the new one.... Even for plain show messages,
I clear away non-appropriate prompts which remain. I give the user no chance
intimation that some key might work if it wont. Why? Because the user really
has no idea what a popup is, or a show message, or any idea at all how
filePro is really working. If they see something that says H-hardcopy and
its not going to work, then it shouldn't be visible, period.  There are very
limited times when I will put up an error message without clearing away the
underlying prompts... But not often.  If you think about it, you know that
when an errorbox or mesgbox is up, the only key that will work is the ENTER
key so why leave up prompts like "Press ESC ESC to Record, DEL to Cancel."
or similar.  Neither of those keys will work while the message is up waiting
for the ENTER key, so I take the trouble to cls("21") just before putting up
the errorbox/mesgbox and then immediately after they press ENTER I put back
up the previous prompt, or whatever is appropriate.  

I know the -d key (don't display prompts) has a huge impact on how the
application looks, and I know it takes a lot of programming to put every
prompt up myself, but if I had to pick the single reason why my applications
look like applications instead of looking like "filePro"... The -d key is
it. It allows you to provide the definitive touch of professionalism to the
apps you write.  It's worth it.

John
 

> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Richard Kreiss
> Sent: Friday, January 08, 2010 5:01 PM
> To: 'filePro List'
> Subject: popup update * show statements
> 
> I am moving address fields from the primary data screen in a 
> file.  One
> piece of information that the record holds is an address.  To 
> make room on
> the primary screen, I moved the address information to a popup screen.
> 
> This screen is editable.
> 
> Popup update -,"pop_address",24;CLEARP;SAVE
> 
> @wef24 if:
> Then: Show 'Enter Name";END
> 
> Problem: Show statement does not appear.  Just F10-Save 
> ESC-Cancel.  This is
> not a prompt I am putting up.
> 
> Anyone know why my show statement is not working?
> 
> I can replace the show with show popup("18","-1") "Enter 
> Name" and then
> CLEARS to clear it. 
> 
> 
> Richard Kreiss
> GCC Consulting
> rkreiss at gccconsulting.net
>   
> 
> 	
> 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
> 



More information about the Filepro-list mailing list