Project

General

Profile

Bug #2715

After using the minimize all windows function, the MDI windows sometime fail to come into focus and weird behaviour

Added by Jonathan Kay over 3 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Interface
Target version:
Start date:
06/03/2016
Due date:
% Done:

0%

Estimated time:
Operative System:
All
Regression:
No

Description

Note: I frequently use Window>Minimize/Hide All Windows and get this weird behaviour. After a lot of trial and error, I think I have a solid repro.

1. Open up AdiIRC.
2. Connect to a server and join at least 3 channels, autojoin is fine or you can do it yourself. For example, join #test1,#test2,#test3.
3. Choose the Window menu and choose Minimize/Hide All Windows.
4. Using either the Treebar and Switchbar, select the 2nd last channel, and then the first channel. For example, click on #test2, then #test1.
5. Then choose the 2nd last one again and the third one. For example, #test2, and finally #test3.

The last channel will now not be in focus, although the textbox in the window will be. The Treebar and Switchbar will report that you are still looking at the 2nd last channel (#test2). If you send a message to the channel, it will appear as though there was a new message (red coloured). If you maximize the channel window, it will not integrate itself into the main window as the normal MDI windows do and instead maximize itself with its own titlebar in the workspace.

As a workaround when this happens, you can choose Minimize/Hide All Windows again and then select the broken channel, which will now come into focus.

Tested on both 2.3 and 2.4 beta, both on Windows 10 and Windows 7.

I attached a quick video demo to show this, the effects and then showing the workaround.


Files

adiirc mdi focus bug.mp4 (21.6 MB) adiirc mdi focus bug.mp4 Demo of bug Jonathan Kay, 06/03/2016 09:32 AM

History

#1

Updated by Per Amundsen over 3 years ago

This is a known bug I like to call the "stuck window" bug, it's a .NET MDI bug with no known fix or workarounds.

#2

Updated by Per Amundsen over 2 years ago

I was able to fix the stuck window in this example, I don't know if it fixes every case, the fix will be in next beta.

#3

Updated by Per Amundsen over 2 years ago

  • Category set to Interface
  • Status changed from New to Resolved
  • Assignee set to Per Amundsen
  • Target version set to 2.7

The original cause have been found and should be fixed, if not let me know.

#4

Updated by Per Amundsen over 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF