Windows filepro splash screen

[Bruce Easton]

Bill Randall wrote Wednesday, March 12, 2008 6:44 PM:
> 
> ----- Original Message ----- 
> From: "Bruce Easton" <bruce at stn.com>
> Sent: Wednesday, March 12, 2008 6:31 PM
> Subject: Windows filepro splash screen
> 
> 
> > Is there any way to get rid of the splash screen in Windows filepro 
> > when
> > moving from one menu to another when a script is used for the 
> > calling menu?
> >
> > I am creating custom menu system on Windows, and the software 
> > requires me to
> > set PFQUAL going into each part of the application, which I would 
> > like to do
> > within menu scripts, since I am mixing new parts of the application 
> > that do
> > not expect a qualifier with ones that do (and I want the options as 
> > close to
> > each other as possible).  I don't want to modify the application - I 
> > just
> > want to call some original menu options from a custom menu.
> >
> > I see that if I use ! in front of the called menu in Windows, the 
> > splash
> > screen is bypassed.  But since I need the script to set PFQUAL via 
> > scripts
> > followed by a "p <menuname>" call for some options, then I see no 
> > way to
> > bypass the splash screen when the operator is just trying to 
> > navigate
> > through secondary menus.  Have I missed something?  Or is this one 
> > of those
> > fp Windows inconveniences?
> 
> You don't say the version of filePro but that is a very old issue that 
> has been resolved in newer licensed versions.  So....upgrade?
> 
> Bill

It looks like it is 5.0.11, and I am just doing some add-on work 
for the client.  

But Bill - are you saying that under a more recent version of 
Windows filepro that if I call p <menuname> from a menu 
script, that I would not get a splash screen?  I didn't see 
anything in the online manual or release notes about that. I 
did see in the release notes this entry for 5.0.11:

(Windows) #649
The initial splash screen now responds immediately to a keypress.

but I don't see how the splash screen can be eiminiated 
altogether for menu calls that need to come from 
p <menuname> vs. !menuname (from another menu option).

Bruce

Bruce Easton
STN, Inc.