Zugg Software :: View topic - CMUD 225 - Windows (other than the main session window) won't minimize

Posted: Fri May 09, 2008 4:58 am

I created a floating window and while I am able to maximize it, and even close it, by clicking on the appropriate buttons on the upper right hand corner of the window, the minimize button won't work unless the window is first maximized in which case it returns it to how it was before the maximize. My intent is, of course, to keep the window active and out of the way. I have not done anything new, this was my configuration under 2.18. I am using CMUDpro.

EDIT: Something else that is different, and perhaps is the cause of the problem: When I move the window, the docking protocol becomes enabled, in CMUD218 this was not the case since all I was doing was moving the window out the way so that I can see what was beneath. Now, maybe the fact that the window thinks that I want to dock it is the correct procedure, but I would like a way to move the window just as I did in the previous CMUD version.

EDIT: I found the problem with the windows trying to dock, this happens when the layout is unlocked. Never noticed it before, because I run with it locked unless I am trying to delete a tab, in which case I am not going to notice any windows trying to dock because I am not moving them.

Posted: Fri May 09, 2008 6:18 am

Yes, thats a bit annoying. Use 'rollup' instead in the mean time.

Posted: Fri May 09, 2008 7:00 am

Another strange thing is that the fly-away windows have gone away, probably intentionally, and for the most part, I doesn't bother me. However, I do use the Status Window and I am wondering where it has gone. I am sending data to it, so it has to be somewhere.

Posted: Fri May 09, 2008 7:49 am

Menubar>Window>Status Window

Posted: Wed May 21, 2008 11:28 pm

I am pushing this item up the list. The inability to minimize a floating window is a solid bug.

Posted: Wed May 28, 2008 7:06 pm

Confirmed and added to bug list. Looks like a problem with the window docking system that I'm using. Not sure why nobody mentioned this before during the beta testing. v2.18 used an older version of the docking system, so this looks like a new bug that they introduced in their newer version.