3.80.2 update

Last night I struggled until 5am to prepare a new update to Process Lasso. It includes some enhancements to the system tray tooltip for English users (other languages coming soon), a fix for certain customized ProBalance settings, indication of hard-coded ProBalance exclusions in the GUI, and a fix for the pane positioning errors (blank/corrupt GUI window).

Regarding the child window positioning errors that could cause a corrupt looking Process Lasso user interface - I finally determined how this was occurring. It was due to the rewrite of the sizing code, and the new ability to hide the graph. Basically, if people tweaked the pane positions around, then changed the main window size .. the result could sometimes be 'out of whack'. It took a specific set of changes to induce this. Typically it would occur if the user maximized the window, reduced the graph size, then restored the window. For some unlucky people, who wanted to tweak the pane positions in a particular way, they'd always encounter this. For the majority of other people, they'd never see this problem. I can tell you that from now on I'll be resizing these panes every which way, and resizing the window in every conceivable fashion during my testing ;o.

For now, I've just forced these pane positions to reset when the main window size changes. Don't worry, for all those who want their pane positions remembered, I will have a proper fix in v3.80.3. I simply had to have a reliable build that didn't have this annoying issue - that was the top priority.

I don't know how many users encountered this, but it doesn't 'sit well' with me to think that people evaluating the product ended up with a corrupt looking user interface. Sure, they could have used the View menu option 'Reset window positions' to fix it, but they didn't know that. This could have ruined the entire Process Lasso 'empire' .. a simple mistake to some window sizing code because I wanted to be sure to preserve relative pane sizes and positions upon main window resize. In other words, I wanted a tweaked user interface to have its tweaked state preserved even when the main window size changes. Previous versions worked like this, and v3.80.3 will again behave this way.

Yes, since I use straight C++, I must do all this painful window resizing code myself. If I used a high level language, or other abstraction layer, it'd all be done for me. However, the GUI would eat up considerably more resources. I hope my users appreciate the slim product in the end, and its worth it.

Did you see this user interface anomaly in v3.80 and v3.80.1? I'd love to know how many people actually saw it. Did you NOT see it? I'd even more love to hear from those who DIDN'T see it, lol.