![](https://seccdn.libravatar.org/avatar/4c72270298d8059442a8d6b6af432514.jpg?s=120&d=mm&r=g)
Hi, Josef & Ladislav: Thank you for your replies. On 10/11/18 12:05 AM, Josef Reidinger wrote:
Hi Fraser, we receive that message. I am just not sure what to respond as I never see that right side cut off. Also we use it on almost every place this alignment of navigation buttons. My opinion is that this right part of screen cutoff is bug and we should fix that and not workaround it, because that someone can complain that bottom part is cut off and in the end we use just few pixels in middle of screen, which will look a bit suspicions.
On 10/11/18 12:38 AM, Ladislav Slezak wrote:
Um, that would not help if the bottom of the screen is cut off as well...
...
IMHO the current layout is good, you can always continue by pressing the button in the right bottom corner. If we moved the buttons to the center then you would need to carefully read the labels to void clicking a wrong button. And users would press a wrong button more often anyway. From the usability POV it would be worse for all users and only helped a bit in few specific cases.
Sorry, I'd keep the current layout unchanged.
Yes, after thinking further on it last night, I was about to post a "never-mind" when instead I got these answers. I was beginning to think of another solution, for sometime in the future when I have enough experience I can contribute more, that would not only address this issue -- which I think is relatively rare, though it does happen to some -- but also the nomodeset thing that was recently discussed. That will be a ways down the road, though. And, since I think it would take some work -- and the Yast Team is already up to their necks in good but hard work -- I think it is something that I should be looking at doing for a major contribution.
I see your point but that is not a solution but a workaround. I'd suggest to report a bug so this issue is really fixed. Or is there any HW combination which always results in broken screen detection? Maybe then YaST could print some hints at the beginning in such case.
In my case, which is somewhat unique, it happens because I am using an older laptop with a shattered screen as my desktop machine. I have a large Acer external monitor attached to it with a Wide-Screen aspect that does not get detected properly in the case of the installer. Works just fine once installed, though. And, since I do not mind using the ncurses installer, it really is not an issue to me personally.
You can select the installer screen resolution using the F3 key in the boot menu. If you manually select the correct resolution then it should work. Or is the correct resolution missing in the list?
I have tried various methods in this regard, all fail. Hunted online, checked all linuxrc options, even tried some bizarre methods of trying to override it. In my case, something that gives the option of "Use External Monitor?" would probably work, but that does not address all the other Users' specific problems. Although, something like that would also solve some problems for those who are using dual monitor setups, ie: The problem of the login dialogue popping up off-screen or on the wrong monitor. On the Forums, I will continue to say "try the ncurses installer" as a solution until I can come up with a better method.
BTW you can still press Alt+N as a keyboard shortcut for the [Next] button. But obviously this depends on the selected language and some dialogs might use a different key.
The ncurses UI uses F-keys for the navigation (F8=Back, F9=Abort/Cancel, F10=Next/OK), maybe implementing also these keys in Qt UI would help. But the problem is that the users would need to know that or at least should be able to easily find out these shortcuts.
Ladislav
... yes, and I see the problem with this, as it would need to add yet another button or something, such as a popup, to the installer intro that would list all these shortcuts for the affected Users. Something that is probably not that desirable, since it is only addressing a fringe set of Users. Thanks again for your replies. I will contact you when I have some better ideas and can help out. Don't hold your breath, though, because you will turn an awful deep colour of purple waiting for me to get to that point. ;-) -- -Gerry Makaro openSUSE Member openSUSE Forum Moderator openSUSE Contributor aka Fraser_Bell on the Forums, OBS, IRC, and mail at openSUSE.org Fraser-Bell on Github -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org