Sort of addressed in pdxlocations/control#12 ?
The help text will now adjust to the window height. If your console is too small the text will get cut off and display '...' to let you know you're SOL.
Sort of addressed in pdxlocations/control#12 ?
The help text will now adjust to the window height. If your console is too small the text will get cut off and display '...' to let you know you're SOL.
<!-- github-comment-id:2771382955 -->
I feel like a set height to the helptext box is a good idea. Having helptext be cut off is a bad idea.
Or maybe have page-down scroll the helptext?
I feel like a set height to the helptext box is a good idea. Having helptext be cut off is a bad idea.
Or maybe have page-down scroll the helptext?
<!-- github-comment-id:2771382961 -->
I think adding an interactive element (scrolling) could be confusing? How would you navigate to the help box? Fixing the help text to 4 lines uses a lot of real estate. Add 2 rows for the border. I banged my head against this one for a while this week so I'm still open to suggestions. I landed with pdxlocations/control#12 to be as friendly to any screen size as possible.
I think adding an interactive element (scrolling) could be confusing? How would you navigate to the help box? Fixing the help text to 4 lines uses a lot of real estate. Add 2 rows for the border. I banged my head against this one for a while this week so I'm still open to suggestions. I landed with pdxlocations/control#12 to be as friendly to any screen size as possible.
<!-- github-comment-id:2771382964 -->
Just spit balling here, I'm a new to Contact so I certainly could be overlooking something
help window could auto scroll
help window could be the 4th window, left after channels and right after nodes
help could be a dialog instead of a window, freeing up real estate
Just spit balling here, I'm a new to Contact so I certainly could be overlooking something
- help window could auto scroll
- help window could be the 4th window, left after channels and right after nodes
- help could be a dialog instead of a window, freeing up real estate
<!-- github-comment-id:2913192162 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
I think we can get by with a max length but I'm not sure how to enforce it...
What'a our minimum screen size target?
24 x 80 chars
Sort of addressed in pdxlocations/control#12 ?
The help text will now adjust to the window height. If your console is too small the text will get cut off and display '...' to let you know you're SOL.
I feel like a set height to the helptext box is a good idea. Having helptext be cut off is a bad idea.
Or maybe have page-down scroll the helptext?
I think adding an interactive element (scrolling) could be confusing? How would you navigate to the help box? Fixing the help text to 4 lines uses a lot of real estate. Add 2 rows for the border. I banged my head against this one for a while this week so I'm still open to suggestions. I landed with pdxlocations/control#12 to be as friendly to any screen size as possible.
I just woke up, need coffee. I notice i did hard code the ui to leave space for at least 4 lines of help...
Just spit balling here, I'm a new to Contact so I certainly could be overlooking something
Help in the context of this issue is referring to the help text descriptions in the Settings dialogue.
Limiting the help text length is the simplest solution.