I counter your rant with my own...
 
<rant>
T7 has its quirks, but the screwy things that you see happening are because of all the hoops we need to jump through to keep running Tas 5, Tas 6, and Tas 7 programs all under one menu. Now if all our users can keep paying us for a year or two but don't ask for anything new or to fix this and fix that. Then we could get rid of the old TAS 5 (BK programs) and Tas 6 (T6 programs) and move to full GUI. But I live in the real world, so I know this is not going to happen.
</rant>
 
There, I feel better...
 
Colin,  
 
  The Evo Menu currently runs all the programs on the menu with a NEWRUNTIME option, this basically tells the exe to launch a new instance of itself that does not know about the existence of the parent menu. That worked fine for the Tas 5 programs as the exe did something special to those programs to keep them as children windows. Something hard coded in the TASPRO 7 exe.  We need to run all the old code with this newruntime option or else when any program ended it will cause AV and Memory errors. Now the new T7 programs when run with newruntime run, but as their own instance and thus are allowed to fall behind the parent menu. I have spent the last week rewriting those programs so they can run without the NEWRUNTIME and will not fall behind the Menu.. its my " no one left behind " plan. It is running but I have two issues left to fix. One is the X button on the top right of the window used to close the program is causing an AV error (but the ESC or Exit button do not..), and Two when it encounters a record lock and that message comes up and says there is a lock on such and such filename do you want to try again Yes / No (no will terminate)  well No to terminate seems to be calling the same code as the X button.. AV error. Once I nail down these last two things I will release the new stuff.
 
Will that be today.. I hope so, but I can't say just yet, AV errors are the hardest to find and fix.

Isn't that the definition of an expert: someone who knows more and more about less and less till they know absolutely everything about nothing...
 
i'm working on it...
 
 

Quote from GasGiant on 03/29/07 at 07:22:24:

 
I'm not a huge fan of how Evo minimizes anyway. I've never seen another app that shrinks to just the titlebar and still is on screen when you minimize it. It's just plain wrong I tell you. Now, I've seen that behavior in child windows but the main evo screen shouldn't act like that. I actually like it when minimized windows disappear completely and exist only in the task bar.

Quote:

 
No that is not what I said. The way we are being forced to use it , or rather misuse it, is causing some screwy things to happen. I am not saying that it is the best development environment, but it is better then scrapping everything that existed to start over from scratch, like some other company that I won't name did, and they are still trying to get it to work four years later...

Meanwhile, creation of a web interface continues apace  

Quote from GasGiant on 03/29/07 at 10:53:08:

 
You know, I wouldn't mind it so much if a lot of DBA related functionality, heck even the entry screens, eventually got recoded in PHP. It would potentially make things a lot more portable and truly WAN friendly (wide area network for you non-techies... sort of think the internet.) There is nothing really to stop people from doing that themselves. In fact, once I get my btrieve tracer to work better it'll be even easier.

Quote from Dale on 03/29/07 at 13:58:52:

 
As do I, so no grumbling required.  
 
Floppies? No such thing when I got started. Mag tape on Miltope vacuum tensioning tape drives were the rage when I started. Punch cards for data entry, teletypes for user interfaces, and green bar for reports. No sissy names like Dimension or Inspiron for our milspec computers, no sir. We had "PDP 11/45" and "AN-UYK 7" to bandy about. Reminiscing helps me to recall why I'm bald. Trying to run payroll for 800 people on a Yuk 5 would make any poor slob rip his hair out.