Hi,
Quote from: dandelO on November 16, 2008, 09:10:38 PM
I get that too but instead of properly minimizing, TG just 'falls behind' any other open windows I have on my screen, then it takes several clicks on the TG taskbar button to restore it to the top.
This is a very important point. I have never had TG2 actually
minimise when closing one of its windows. Minimising is when the window itself is no longer on the screen, and the only representation of it is the button in the task bar. If TG2 were minimised then if you close the windows of all other applications you had running you would not see the TG2 window on the screen. However, what I have seen before is what dandelO describing. This where another window comes to the front instead of the TG2 window you were expecting. If you were using other applications with their windows maximised then when their window came forward it might look like TG2 was minimised. The difference would be that if you close the windows of all other applications the TG2 window would still be visible on the screen. It's pretty important that we're clear what is happening, and making a distinction between actual minimising and just another window coming to the front.
TG2 actually minimising when clicking a window's close button would be a new problem, one I've never seen before and something pretty weird.
However, the problem with another window coming to the front is a longstanding one, and one I've spent quite some time looking into. After messing around with other Windows apps, with TG2 not running, I've found it's actually not possible to 100% predict which window will come to the front when another window is closed. My feeling is that this is something inherent to Windows, but it's more obvious with TG2 because we use windows in a way which isn't that common. It is a pain, but at this point I'm not sure it's something fixable.
QuoteIt usually happens if I close a settings panel that's not in the main node network view. e.g. a shader inside another network tree, or object.
Yes, it seems most likely to happen with a window which is floating, like a settings panel ( official name is "param floater" ). However I think it could also happen with other windows as well. I can actually reproduce the problem using the main window and a couple of param floaters, but I can't figure out why it causes another application's window to come forward. I'll will look into it more during the beta period, I may have a "Eureka" moment :-).
Regards,
Jo