CEA - Custom Event Actions

[admin]

Next beta has some numbers in the title bar of config. Please show me.

[LittleBiG]

100% is possibly 96 dpi

This problem happens on the 1st monitor?

If I use only one monitor (notebook display OR the monitor) they are ok. But when they are used at the same time in extended mode, the problem appears on both, doesn't matter on which I start XY.

I have a very important accidental find in this!!! If I look at a text file content in a hover box, it recovers the Configuration window! (And it remains okay until the next restart) Is it because XY rechecks the monitor before showing the hover box?

[admin]

100% is possibly 96 dpi

This problem happens on the 1st monitor?

If I use only one monitor (notebook display OR the monitor) they are ok. But when they are used at the same time in extended mode, the problem appears on both, doesn't matter on which I start XY.

I have a very important accidental find in this!!! If I look at a text file content in a hover box, it recovers the Configuration window! (And it remains okay until the next restart) Is it because XY rechecks the monitor before showing the hover box?

Interesting, that's a hot trace! One second too late for this beta release.

[LittleBiG]

Next beta has some numbers in the title bar of config. Please show me.

Here you are.
Also, I have an animated GIF about the weird recovery if you need it.

[klownboy]

But, FYI, I've also been thinking about a multiline tooltip (on hovering the cell) that shows the whole script (if it fits). I'm to opinions...

To see the entire script file/path/name in a tooltip would certainly be a big plus. But, if you are going to do that why not have the blue or red dot alone and hover to see the entry. It would certainly have a cleaner look and you wouldn't have as many issues of stuff being off screen. Either way you still have to click to edit an entry.

[admin]

But, FYI, I've also been thinking about a multiline tooltip (on hovering the cell) that shows the whole script (if it fits). I'm to opinions...

To see the entire script file/path/name in a tooltip would certainly be a big plus. But, if you are going to do that why not have the blue or red dot alone and hover to see the entry. It would certainly have a cleaner look and you wouldn't have as many issues of stuff being off screen. Either way you still have to click to edit an entry.

Yes, that was my idea, too.

[autocart]

But, FYI, I've also been thinking about a multiline tooltip (on hovering the cell) that shows the whole script (if it fits). I'm to opinions...

To see the entire script file/path/name in a tooltip would certainly be a big plus. But, if you are going to do that why not have the blue or red dot alone and hover to see the entry. It would certainly have a cleaner look and you wouldn't have as many issues of stuff being off screen. Either way you still have to click to edit an entry.

Obviously, I am all for the script column showing the first few chars of the code. After all I am the one who brought up the idea.
The idea is, as Don already hinted at, to put an identifying comment in the first line, which then shows in the script column, in order to have a visual quick confirmation that the right script really is assigned to the right event. Maybe its just me, but I think that all with a bad short term memory like me would benefit greatly from it. It is not about checking the code itself, much less about editing it. It's only about quickly checking the assignments. If you think that you check the assignments only once and then never ever want to look at it again, be my guest. I do definitely not think that it is done once and then never again. It would also help a great deal with debugging, in case that comes up sometimes.

Regarding the tooltip... I never understood what is so great about tooltips, but again that is just me. I find them bothersome.. either they pop up too slowly or they are constantly in the way of something else and, besides, one has to move the hand in order to see it, not just the eyes. Besides, what good does seeing the code in the tooltip? I can't figure it out.

But anyway, Don, of course you must do what is best in your eyes.

[admin]

There's time. There won't be big changes before phase 2.

[LittleBiG]

Next beta has some numbers in the title bar of config. Please show me.

So, immediately after the start I have this:
1920 x 1080, 1036/52, Height=774

After appearing any hover box, and reopen the configuration window I get new values:
1920 x 1080, 1030/0, Height=811

In the second case, tabs in Configuration are ok, no vertical scrollbars appear.

[admin]

Next beta has some numbers in the title bar of config. Please show me.

So, immediately after the start I have this:
1920 x 1080, 1036/52, Height=774

After appearing any hover box, and reopen the configuration window I get new values:
1920 x 1080, 1030/0, Height=811

In the second case, tabs in Configuration are ok, no vertical scrollbars appear.

That's without moving XY to the other monitor?

[admin]

Checked the code. Showing the hover box does NOT explicitly update any screen metrics related values. I don't understand what's going on.

[LittleBiG]

That's without moving XY to the other monitor?

Yes, I do everything on the primary monitor. As a test, I moved XY to the second monitor and the unnecessary vertical scrollbar is back, showing hover box won't help. But moving XY back to the first monitor, Configuration window is ok again. Incredibly strange.
I am showing you how the magical thing happens:

[LittleBiG]

XYplorer gets something from the second monitor on start, however, it runs on the primary one exclusively. Here is the proof. I changed the resolution of the second monitor to be in sync with the ratio of the primary one, to 1280 x 720.
screen; became this:
Screen
XYplorer 21.30.0014 - Windows 10 Enterprise, 64-bit, Release 1909, Build 18363.1198

Virtual Screen: (0, 0) - (3200, 1080)

Screen.Width (screenW) = 1920 (1920)
Screen.Height (screenH) = 1080 (1080)
Current Monitor: 1 (Primary)
Current Work Area: (0, 0) - (1920, 1030)

Number of Monitors: 2
Monitor 1 Area: (0, 0) - (1920, 1080) = 1920x1080
Monitor 1 Area Work: (0, 0) - (1920, 1030)
Monitor 2 Area: (1920, 147) - (3200, 867) = 1280x720
Monitor 2 Area Work: (1920, 147) - (3200, 827)

Startup Work Area: (0, 0) - (1920, 1030)
GetCursorPos = 1401, 66
XY Main Window: (-9, -9) - (1929, 1039) = 1938x1048

Screen DPI: 120 (125%) twX: 12 (12) Stretch: 1 sLF: 1,25 Toolbar Zoom: 1 (1;1)
Screen Color Depth: 32
DPI awareness: Per monitor
Auto Scaling: Yes, Yes

UseDPIAwareIconSizes: Yes, Yes
Icon Size: Small=16, Large=32
Icon Size Controls: Small=20, Large=40
Icon Size Recommended: Small=20, Large=40

And the configuration window appeared like this:

[klownboy]

Obviously, I am all for the script column showing the first few chars of the code. After all I am the one who brought up the idea.
The idea is, as Don already hinted at, to put an identifying comment in the first line, which then shows in the script column, in order to have a visual quick confirmation that the right script really is assigned to the right event. Maybe its just me, but I think that all with a bad short term memory like me would benefit greatly from it. It is not about checking the code itself, much less about editing it. It's only about quickly checking the assignments. If you think that you check the assignments only once and then never ever want to look at it again, be my guest. I do definitely not think that it is done once and then never again. It would also help a great deal with debugging, in case that comes up sometimes.

Honestly, it's not that big a deal to me. I thought seeing "load D:\Tools\XYplorer\Scripts\CEA_MiddleClickMenu.xys" or even a part of it was a bit much and not that aesthetically pleasing. Yes, I did put a comment in front of one to see how that looked. I can live with that and I will, but it doesn't look that great either. /*Double-Click script*/ ... and of course that ends up in the ini file as well.

To the contrary I may end up changing scripts more frequently than most users. I wrote a small script that's sole purpose is to be able to change the script assignment for these on the fly by assigning the script to a variable as you can see in my post here viewtopic.php?f=7&t=22172

I'll be happy with whatever Don comes up with and glad he's bringing both new and old CEAs to the Configuration GUI.

[admin]

Next beta has some numbers in the title bar of config. Please show me.

So, immediately after the start I have this:
1920 x 1080, 1036/52, Height=774

After appearing any hover box, and reopen the configuration window I get new values:
1920 x 1080, 1030/0, Height=811

In the second case, tabs in Configuration are ok, no vertical scrollbars appear.

Ha!, I finally found the code that's called before showing the hover box, and it's only called in a multi-monitor situation! I will now use the same code before showing config, that should solve it. Remains a mystery why it's necessary, but Windows is full of mysteries...