XYplorer Beta Club

admin wrote:Are these still your settings?

(Unfortunately) yes.

admin wrote:Yep, those arrows are a bit small. (OTOH their position and function is fixed so they do not contain interesting information.)
I put it on my list.

They are still a bit small.

Q: could the scope of the "ToolbarZoom"-tweak be extended to the Breadcrumb Bar?

I'm not even sure anymore. Would it really look better if they were bigger? Is it worth the lost space?

Filehero wrote:Q: could the scope of the "ToolbarZoom"-tweak be extended to the Breadcrumb Bar?

You can enlarge the Breadcrumb font by Ctrl+MouseWheel on the bar.

admin wrote:I'm not even sure anymore. Would it really look better if they were bigger? Is it worth the lost space?
You can enlarge the Breadcrumb font by Ctrl+MouseWheel on the bar.

"Root cause" of my issue are hampered touch/pen (*) operations with the BC navigation elements.

By default/standard they're too small on my high dpi devices (200% scaling). Sure, as you've pointed I can (an do so currently) enlarge the BC fonts which also scales up the arrows/hamburger.
However, since the relative size of button- and text-based BC navigation components (visually) remains during scaling, the BC path texts end up with godzillian ( ) size soon.


The following shots were taken on the Surface Pro but resampled to 50% of their original size to compensate for the 200% device scaling. You see, there's not much relative size gained.

Default, BC fonts not enlarged BC fonts enlarged
Of course, the question remains: is it it worth it for you?
Beside me there're not much public complaints here, indeed. But since I expect the number of (touch) high DPI devices to grow massively in the near future adapting for it isn't the worst idea, isn't it?

Just get yourself a Surface Pro.

How about the other XY users? Any opinion?

Cheers,
Filehero


*: pen operations still suffer from a small but noticeable pointing jitter.

OK, the next beta should work better. Let me know if it's still not big enough...

admin wrote:OK, the next beta should work better. Let me know if it's still not big enough...

Hmm, I don't see any changes in size. After more playing and comparing with the desktop machine where the scaling behaves nearly perfect my issue still exists. Initially the bc nav buttons are still too small in relation to the bc text (in comparison to my lower resolution desktop machine). Have you changed any button size under high DPI conditions?

I can continue to live with it. Since there are still some graphic elements awaiting resizing (Drag cursors etc), maybe his task could be better done in one rush on a rainy or winter day.

Hm?? Can you send another screenshot in 100% scaling.

How many pixels wide and high should be a button you can work with?

Here are the shots from both machines with the actual font settings (I need to use size 98 on the Surface otherwise it's too small).
Note the height of the hamburger as compared to the drive letter.


Desktop pc, scaling default 100% (as "recommended" by Win 10) Surface Pro, scaling default 200% (as "recommended" by Win 10) Confusion: in MDBU, as expected this image is double the size as the others. I don't know why this image isn't displayed doubled size here in the forum preview/view (all shots are 96 dpi)

Surface Pro, scaling default 200%, but resized to match desktop PC's 100% (PhotoLine 18, Lanczos
Do you see what I mean?

Something is strange here. Some "smartness" seems to be going on...

The largest arrow I currently draw is 13x13 pixels. Here is a screenshot (400% enlarged) where the breadcrumb font is set to Segoe size 15. Note that there should be no anti-aliasing at all with the arrows. It's all crystal clear hard pixels.

Surface Pro, fresh, no resizing Is any interference with some other config/tweak excluded with Fresh?

Yep, evil smartness at work there... but I have a plan... (hard to do though... )

admin wrote:Yep, evil smartness at work there... but I have a plan... (hard to do though... )

Which layer is to blame? Graphic setup (dpi), Windows scaling, XY adaption to Windows scaling or something else?

Hopefully this is something more generic, so the effort assumed will have some additional reward in the future.

Before I start the work, did you already play with the settings on the compatibility tab (right-click EXE, Properties)?

Yes, I've tried the options "Anwendung", "System" and "System (erweitert)" both for the current and all users. Each time I restarted XY, but couldn't notice any visual difference.

Note: since I don't know what these options really do it is just playing.

What outcome do you expect if the fix works?