Windows filepro splash screen

[Brian K. White]

> Thanks much for the clarification, Bill.  I'm also hearing now that
> that splash behavior was not always in the Windows version and that there is
> at least one easy-to-apply work-around.  Regardless, had I been working with
> Windows filepro when this splash behavior was first applied, I would have
> been screaming and kicking.  Forcing extra time, keystroke on end-user in
> moving from one menu script to another menu - just not acceptable.

Exactly as I did when I first hit this new behavior a couple years ago.
(screamed and kicked, described the reasons in clear detail, found the work-around, described the work-around here)

This has been brought up before. And not just as an "i don't like this" which should be enough frankly, but I described the exact way this turned an existing working app into a pretty bad downgrade in user experience, and the exact reasons why making the necessary changes to the app to avoid the problem is an unreasonable amount of work to inflict out of the blue, for no gain, just to keep an existing app working more or less as well as it already was working.
Completely inexcusable and intolerable.

We just don't sell the windows version of FP any more.
All customers who used to be the market for a windows version of our software, when upgrade time came around we just convinced them to switch to a serverless (from their point of view) subscription version of the same software, where they use facetwin or other terminal emulator to one of our unix/linux/freebsd servers.
The offensive splash was just one reason, and not even the main one, but it sure helped solidify the policy.

-- 
Brian K. White    brian at aljex.com    http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro  BBx    Linux  SCO  FreeBSD    #callahans  Satriani  Filk!