Opened 5 years ago

Closed 5 years ago

Last modified 5 years ago

#159 closed enhancement (invalid)

Oversized windows for screen resolution

Reported by: Mikhail Malyshev Owned by:
Priority: undecided Milestone:
Component: undefined Version: 4.0-2014R5
Severity: minor Keywords:
Cc: OS Platform: All
Blocked By: Blocking:
Release Notes:

Description

Problem

Currently, when a window does not fit the screen, it tries to reopen with a topaz 8 font (which is usually not smaller then a proportional font like commonly used XHelevetica 11 or similar.)

Analysis

The current fall-back layout mechanism needs changing to something more useful and less destructive to the GUI.

Enhancement recommendation

When ever MUI requires to open a window that is bigger then the screen resolution, MUI should enforce a virtual group on the windows contents. This will allow to display the window and keep the user defined settings for the GUI even in extreme cases.

eg. test case: Current MUI 4.0 prefs editor → frames/backgrounds settings window has no chance of fitting 640x wide screen.

Change History (2)

comment:1 Changed 5 years ago by Thore Böckelmann

Resolution: invalid
Status: newclosed

Adding arbitrary objects without the application's knowledge will cause major issues, as this modifies the object tree in an unexpected way from the application's point of view. A simple virtual group wouldn't even be enough as there is no way to reach the objects which don't fit in the maximum visible area. An additional scrollgroup would be required, which doesn't make the situation any better nor easier.

topaz/8 is the final fallback font as this one always exists and is considered to be "small", even if other fonts might be smaller in either horizontal or vertical direction. But there is no guarantee that these fonts are available.

I know that MUI applications should be able to open their GUI on a 640x480 screen, but this is a statement from times when such resolutions where considered "standard". It is 2015 by now and typical resolutions are 1024x768 and bigger. Personally I consider 800x600 as absolute minimum by now. I told you several times by now that MUI4 is targeted at powerful machines and not at unextended "bare minimum" machines. If MUI4 works on these "low end" machines this is ok. If it doesn't then I do not care. Accept this. I will not discuss this topic any further.

comment:2 Changed 5 years ago by Mikhail Malyshev

That is really a shame since even Win apps fallback to 640 and we have a few apps that run in 640 screens making it impossible to change the MUI settings, since at lest the main prefs program has to cope with such situations (currently only the frames settings window is oversized).

It's a pity we can't do anything for standard apps that can end up in such situations. Basically it should work like layers lib and be transparent to the app, so the virtual group sliders in the window are not real mui vgroups.

On the other side, there is another potential and clean solution that has already been used by OS classact prefs!

If we can't fit on screen, we can open a new screen with larger dimension (larger then visual size) and then virtual scroll around the screen.

And finally, maybe ask a user for a small fall back font?
Rendering the GUI with topaz/8 is not better in many cases and it will not work if we came to this problem in the first place.

Note: See TracTickets for help on using tickets.