Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Enhancement] Horizontal text scrolling in settings #8136

Closed
SukharevAndrey opened this issue Nov 1, 2015 · 10 comments · Fixed by #8913
Closed

[Enhancement] Horizontal text scrolling in settings #8136

SukharevAndrey opened this issue Nov 1, 2015 · 10 comments · Fixed by #8913

Comments

@SukharevAndrey
Copy link

Please make all the text in settings menu automatically scrollable if it exceeds some predefined length (in my opinion text should scroll left and when it reaches the end of phrase - reset and do that again infinitely). Users with low resolution screens (mobile devices for example) have overlapping text everywhere in settings, especially in Russian language where correct translation requires much more space than in English.
image
This is a simulation of how it looks on that screens.
Also it would be great to see detailed explanation of every setting in application (like in Dolphin). For example it could be showed like Android toast on long press. It will eliminate a lot of comments in brackets.
proposal
I thought I could do it myself but then realized that you are using your own custom UI framework done from scratch. I'm not so skilled programmer yet to customize such things :(

@VIRGINKLM
Copy link
Contributor

I really like this idea.

@hrydgard
Copy link
Owner

hrydgard commented Nov 2, 2015

Yes, adding explanations makes sense. I plan to redesign the UI a bit in the future to make space for them.

@zminhquanz
Copy link
Contributor

good idea

@zminhquanz
Copy link
Contributor

@hrydgard please redesign UI nearly XMB by Sony

@MarcoEstevez
Copy link

+1 zminhquanz suggestion

retroarch uses it and its great on PC with game controllers, not sure will fit well on phones, tablets touching fashion.

said that, ppsspp UI is also great, is one of the best original UI out there by far :-D

@SukharevAndrey
Copy link
Author

I think complete redesign is not needed, especially like XMB. RetroArch UI is not as suitable for touch control. Let the developers better focus on emulation.

@hrydgard
Copy link
Owner

hrydgard commented Nov 2, 2015

XMB is not great for touch and there are patents around it, so that won't happen. More like changing the look of the existing interface a bit, maybe add an action bar, stuff like that.

@GamerzHell9137
Copy link

Ohhh~ UI change? Can't wait for that. find the PPSSPP UI pretty meh right now.

@unknownbrackets
Copy link
Collaborator

@hrydgard speaking of UI changes, what do you think of views having e.g. std::vector<UI::Tween> tweens_? Could apply a matrix to bounds or maybe verts, as well as opacity, etc. based on a timer. Trickiest part would want to make them cancel without fully reverting (e.g. to reverse or change a tween mid-swing.)

For explanation UI, getting touch right may take some thought. I think the simplest thing is to show an explanation once they change the option, but how about dropdowns? Of course, long-press could highlight without changing and that might not be too hard to discover. It could even initially show the space (attached at bottom) with that CTA.

I'm not a huge fan of the horizontal scroll. Personally, I'd rather we allow a certain % shrink in the text before we do that - it looks uneven when it shrinks, but less bad than when it moves. Moving text is distracting.

Personally, I'd prefer it to wrap in the settings dialog, if the checkbox text is too long. Still at maybe a certain % smaller font size and not too generous a line height.

-[Unknown]

@hrydgard
Copy link
Owner

Yes, some sort of animation system would be nice.

To fit long strings, shrink to say 60% then wordwrap is probably the better idea, yes...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants