RobRoy Posted October 29 Share Posted October 29 How about making sure the completion dialog box is in front so it doesn't go behind then log window when completed? Link to comment Share on other sites More sharing options...
dbminter Posted October 29 Share Posted October 29 That is a bit of an annoyance. There are 2 temporary workaround that might work. One is to dock the Log window with the ImgBurn main interface window. I haven't tried that yet but it might work. What DOES work is what I've done. I moved the OK completion window well to the right side of the Log window so it can't go behind the Log window. It's a bit of an inconvenience and isn't pretty but it works. Link to comment Share on other sites More sharing options...
LIGHTNING UK! Posted October 29 Share Posted October 29 All the message boxes within the app behave the same way (they flow through one function). Generally speaking, the 'owner' window parameter of the MessageBox Windows API call is set to the one that's active when they're displayed. For the 'operation successfully completed' ones, that would be the main window. I'm not sure why it would be going behind the log window as I'd expect it to be centred relative to its owner. Where is your log window in comparison to the main window? Is it maximised? I don't really recall it being a problem, but we are going back 10+ years! Link to comment Share on other sites More sharing options...
dbminter Posted October 29 Share Posted October 29 For me, the Log window is its "default size" at some distance separated from the main ImgBurn window. In other words, it's not snapped/docked to the main ImgBurn window. Link to comment Share on other sites More sharing options...
Recommended Posts