Application fails to minimize

Author

Message

Topic Search

Topic Options

rdhd

Senior Member

Joined: 13 August 2007
Location: United States
Status: Offline
Points: 954

Post Options

Post Reply

Quote rdhd

Report Post

Thanks(0)

Quote

Topic: Application fails to minimize
Posted: 10 August 2009 at 12:20pm

Open and build the ribbon sample.

Start the sample app.

Maximize the window.

Hit the "Windows+m" key. the app minimizes.

Right-click the ribbon sample icon in the task bar.

Click "restore". the app restores to the maximize state.

Hit the "Windows+m" key. The app fails to minimize.

rdhd

Senior Member

Joined: 13 August 2007
Location: United States
Status: Offline
Points: 954

Post Options

Post Reply

Quote rdhd

Report Post

Thanks(0)

Quote

Posted: 10 August 2009 at 4:36pm

I have found that if I hit the restore icon on the command (frame) ribbon one time, it "fixes" the problem.

I have also set a conditional break point is our lowest level windows message processing loop looking for the WM_SYSCOMMAND. After I run the steps to duplicate the problem, no such message is trapped (until I perform the above). This one doesn't seem to be related at all to the window styles as I have also oberved the frame's styles before and after the repro and they are identical. Its as if Windows doesn't "see" our app has been restored after we get a WM_SYSCOMMAND to restore the app.

Anyone (Oleg) have any thoughts on a work-around for this one?

jpbro

Senior Member

Joined: 12 January 2007
Status: Offline
Points: 1357

Post Options

Post Reply

Quote jpbro

Report Post

Thanks(0)

Quote

Posted: 10 August 2009 at 7:38pm

I don't think this is a problem with CJ - I notice the same behaviour for windows from every other app that I try these steps with on Vista 32-Bit Home.

Product: Xtreme SuitePro (ActiveX) version 16.2.6
Platform: Windows XP - SP3

Language: Visual Basic 6.0 SP6

znakeeye

Senior Member

Joined: 26 July 2006
Status: Offline
Points: 1672

Post Options

Post Reply

Quote znakeeye

Report Post

Thanks(0)

Quote

Posted: 11 August 2009 at 2:59am

I agree. This is why I stepped away from Win+M to Win+D, since the former does not work in all cases.

PokerMemento - http://www.pokermemento.com/

rdhd

Senior Member

Joined: 13 August 2007
Location: United States
Status: Offline
Points: 954

Post Options

Post Reply

Quote rdhd

Report Post

Thanks(0)

Quote

Posted: 11 August 2009 at 10:17am

I tried this with Office '07 and Visual Studio '08 without reproducing. So I stopped there. However I just did it with the Visual Studio '07 help app. And I can also duplicate it with Windows Explorer. I also found that if I hit the restore icon on those apps, it doesn't always fix the problem. But I move the window a bit after hitting restore and then windows+m affects the app. So jpbro is correct. I'll send this one to Microsoft and see what they say. Probably a 25 year old KB article out there somewhere that details how in 39 easy steps we can work-around the bug. I'll try it on Windows 7 too. So far our experience with Windows 7 is that all the Win 98 through Vista bugs have made the Windows 7 cut.

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
rdhd Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 August 2007 Location: United States Status: Offline Points: 954	Post Options Post Reply Quote rdhd Report Post Thanks(0) Quote Reply Topic: Application fails to minimize Posted: 10 August 2009 at 12:20pm
	Open and build the ribbon sample. Start the sample app. Maximize the window. Hit the "Windows+m" key. the app minimizes. Right-click the ribbon sample icon in the task bar. Click "restore". the app restores to the maximize state. Hit the "Windows+m" key. The app fails to minimize.

rdhd Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 August 2007 Location: United States Status: Offline Points: 954	Post Options Post Reply Quote rdhd Report Post Thanks(0) Quote Reply Posted: 10 August 2009 at 4:36pm
	I have found that if I hit the restore icon on the command (frame) ribbon one time, it "fixes" the problem. I have also set a conditional break point is our lowest level windows message processing loop looking for the WM_SYSCOMMAND. After I run the steps to duplicate the problem, no such message is trapped (until I perform the above). This one doesn't seem to be related at all to the window styles as I have also oberved the frame's styles before and after the repro and they are identical. Its as if Windows doesn't "see" our app has been restored after we get a WM_SYSCOMMAND to restore the app. Anyone (Oleg) have any thoughts on a work-around for this one?

jpbro Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 12 January 2007 Status: Offline Points: 1357	Post Options Post Reply Quote jpbro Report Post Thanks(0) Quote Reply Posted: 10 August 2009 at 7:38pm
	I don't think this is a problem with CJ - I notice the same behaviour for windows from every other app that I try these steps with on Vista 32-Bit Home.
	Product: Xtreme SuitePro (ActiveX) version 16.2.6 Platform: Windows XP - SP3 Language: Visual Basic 6.0 SP6

znakeeye Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 26 July 2006 Status: Offline Points: 1672	Post Options Post Reply Quote znakeeye Report Post Thanks(0) Quote Reply Posted: 11 August 2009 at 2:59am
	I agree. This is why I stepped away from Win+M to Win+D, since the former does not work in all cases.
	PokerMemento - http://www.pokermemento.com/

rdhd Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 13 August 2007 Location: United States Status: Offline Points: 954	Post Options Post Reply Quote rdhd Report Post Thanks(0) Quote Reply Posted: 11 August 2009 at 10:17am
	I tried this with Office '07 and Visual Studio '08 without reproducing. So I stopped there. However I just did it with the Visual Studio '07 help app. And I can also duplicate it with Windows Explorer. I also found that if I hit the restore icon on those apps, it doesn't always fix the problem. But I move the window a bit after hitting restore and then windows+m affects the app. So jpbro is correct. I'll send this one to Microsoft and see what they say. Probably a 25 year old KB article out there somewhere that details how in 39 easy steps we can work-around the bug. I'll try it on Windows 7 too. So far our experience with Windows 7 is that all the Win 98 through Vista bugs have made the Windows 7 cut.