Bug 313116 - KTouch has a too large minimum window size (1000x700)
Summary: KTouch has a too large minimum window size (1000x700)
Status: CONFIRMED
Alias: None
Product: ktouch
Classification: Applications
Component: general (show other bugs)
Version: 2.0.0
Platform: Other Linux
: LO normal
Target Milestone: ---
Assignee: Sebastian Gottfried
URL:
Keywords:
: 322723 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-01-12 03:03 UTC by Christoph Feck
Modified: 2020-12-24 01:07 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Christoph Feck 2013-01-12 03:03:21 UTC
It could simply scale down the contents for smaller window sizes, seeing it is pure custom graphics.
Comment 1 Sebastian Gottfried 2013-01-12 09:44:52 UTC
Too small for what? Please clarify.

I know were was a policy for KDE software to fit on 800x600 screens, but I thought that was thing of the past. The minimum window size I use (1000x700) was chosen to fit on screens with a resolution of 1024x768 pixels, a resolution most devices bought roughly in the last ten years should have. One exception is obviously the first generation of the infamous netbook device class, but these luckily did fall out of favor pretty quickly.

There is one problem are the approach you are suggesting to resolve the issue: the top row in the training screen with the analog meters. This row is limiting factor here, all other UI elements are scalable and would fit in a smaller window.

The graphics to render those meters are scalable per-se, but even at the scale they are displayed now they contain a lot of features only a single pixel wide. Further down-scaling those elements would result in a blurry mess. 

The only way real way out I see is to provide a second set of meters with considerable less detail for low-res screens. This is a non-trivial amount of work so I would first discuss if its really necessary.
Comment 2 Sebastian Gottfried 2013-01-12 09:56:57 UTC
> Too small for what? Please clarify.
Oops. I've meant too large, of course.
Comment 3 Christoph Feck 2013-01-21 22:22:58 UTC
Thanks for the clarification. I started KTouch on a screen with a 768x1024 resolution (portrait mode), that's why I noticed the failure to adapt.

I would say we keep this entry open to see if someone else has the same issue, otherwise just close if too complicated to adapt.
Comment 4 Sebastian Gottfried 2013-01-22 14:25:51 UTC
I think I will eventually handle such cases as well. I have already received some feedback through my blog clearly indicating not every likes those big analog-meter-style indicators in general. It is quite possible that I implement for this user group a more subtle statistics readout. This one could then also be used for low-res screens as well. But this is definitely KDE SC >=4.11 material.
Comment 5 Sebastian Gottfried 2013-07-23 08:37:27 UTC
*** Bug 322723 has been marked as a duplicate of this bug. ***
Comment 6 Stefan 2019-05-13 14:13:44 UTC
This issue affects a Samsung Nc10 netbook with max resolution 1024x600 that I gave my daughter to learn typing. I understand that these kind of laptops are rare nowadays, but is it really so complicated to reduce the minimum vertical resolution from 768 to 600?

Thank you.

Stefan
Comment 7 Chris Lane 2020-06-01 11:35:53 UTC
I discovered this recently too. While it's not typically an issue if you're running the app as a floating window or fullscreen, it becomes a problem on tiling window managers when other things are also running.

e.g. https://i.imgur.com/KWwnxlo.jpg
See how ktouch extends way beyond the half-screen window I would expect it to have.
Comment 8 twinshadows404 2020-12-24 01:07:02 UTC
This also creates many issues if scaling is applied as the scrollbar and a part of the text become invisible when you try to snap a window to the right side.