You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extra arrows at opposite sides have fallen out of favor due to the time that it takes to point and click them. A more productive approach is placing both extra arrows bellow the scrollbar, similar to how it’s done in various popular word processors, such as MS Word, WordPerfect, and WPS Office in this picture:
An advantage of following that approach is that the same buttons could be repurposed to move between text found in a search or markers if so desired. Nevertheless, having the buttons at the bottom would shrink and offset the side bar up, meaning it could fail to act as an accurate progress bar.
Hiding these buttons while prompting would liberate the space to be used by the scroll bar at the expense of loosing the button while prompting. Another option would be to leave the buttons at the button and make sure they have a border or background color that sets them apart from the rest of the scroll bar.
I couldn’t find anything relating to scroll bars on KDE’s Human Interface Guidelines. A change like this should be consulted with KDE’s Consistency Group to make sure that we don’t re-invent the wheel or divert too much from the design in other KDE software. We could also implement the feature first and change it later because, at present, QPrompt is not a KDE app. Nonetheless I’d like to leave that door open, hence why I follow the HIG for most things.
Also at the time of writing, I’m not clear on how to implement this feature without potentially crashing QPrompt. QML’s ScrollBar placement is very tricky and can crash the program if used incorrectly. This API also provides no means to add buttons. Though, I think, it shouldn’t be too difficult.
I just realized Ctrl+Home and Ctrl+End achieve this goal of allowing to jump to the start or to the end... This being the case, would you still want physical buttons for this @videosmith?
Feature request by @videosmith, taken from conversation on the forum: https://forum.cuperino.com/t/qprompt-system-message-animation-completed/46/4
@videosmith wrote
@Cuperino's reply
@videosmith's reply
Takeaways
The text was updated successfully, but these errors were encountered: