Mini GUI => Show test properties dialog: Tiny space to move dialog around

[rowo360]

Description:
I opened the "Test properties dialog" from the Mini GUI view mode and tried to move the dialog around. I almost gave up and thought that this is not be supported. Until I notice that there's a tiny space available to start the move operation.

It might be the case that this observation is depending on OS or screen resolution.
So, here are my numbers: I use Windows 11 and my laptop has screen resolution 1920x1080 (OS scaling factor 150%)

Reproduction:

1. Switch to Mini GUI view mode
2. Select one test node in tree
3. Open context menu => Select 'Properties..'
   => The "Test properties dialog" is opened

Now try to move the dialog around by grabbing the dialog title bar with the mouse and move around...
Here's a screenshot - the operation is only possible in the green marked area.

Expected behavior:
I expect that the entire dialog title bar can be used for the move operation.

Environment:

• TestCentric Version 2.0.0-beta5 and main developer branch
• OS: Windows 11
• Target Runtime for your test assembly: .NET Framework 4.8

[CharliePoole]

I've noticed this before although it's not so bad on my Windows 10 system. I have an additional clickable area of about the same size under the name of the test. Anyway, it's minor but worth fixing if we can.

Problem is due to the fact that there is no actual title bar. The "Title" is a label. Two possible fixes, I think...

1. Create an actual title bar and set the text of the dialog rather than the label when a new test is selected. In that case, you could enable only the exit button eliminating my hand-drawn X. Trick will be to get the pin button to lay on top of the title bar. This is extremely old code from NUnit V2. I think I wrote it around 2004 and didn't know any other way at the time.

2. Figure out the correct setting to make the label transparent to mouse clicks or to pass them to the dialog itself. I have done this before but can't remember the details off the top of my head. It may not be a setting ... we might have to pass the actual events to the dialog, which is a bit messy and probably not worth the extra complexity.

Leaving these ideas for the future unless you have an urge to work on this. It's low priority at the moment.