-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
[MainUI] Knob or Gauge widgets overriding the Close button #536
Comments
Obviously (or so I thought) you're not supposed to choose widget types
other than list items as the default list item widgets. Just noticed the
standard standalone widget library is presented though. I'll remove it.
Keeping the issue open to track.
…On Wed, Nov 18, 2020, 21:20 lolodomo ***@***.***> wrote:
[image: image]
<https://user-images.githubusercontent.com/10186704/99583473-d9017b00-29e3-11eb-81c5-100de15ad206.png>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#536 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAPJJMYYGFZTUBDTHMPT623SQQUA7ANCNFSM4T2OIAOQ>
.
|
ghys
added a commit
to ghys/openhab-webui
that referenced
this issue
Nov 19, 2020
Disallow standalone widgets to be selected for list items (close openhab#536). Allow slight alterations to the default widgets suggested by the system without reconfiguring it completely: if the metadata value is blank, assume the default system-suggested widget is to be used and merge the config found in the metadata. Closes openhab#534 (since now only the iconUseState option has to be set to enable dynamic icons for Number items and similar). Change the metadata namespace selection menu to only display the metadata which is set in the metadata menu, and use an action sheet to add more. This also paves the way for user-defined namespaces. Move the metadata order out of the item edition card in the Model page, into its own section. Add metadata editor for the expire namespace (openhab/openhab-core#1620). Reorder the sections of the item details page in a more logical manner (semantic classification below the tags that define it). Signed-off-by: Yannick Schaus <github@schaus.net>
ghys
added a commit
that referenced
this issue
Nov 19, 2020
Disallow standalone widgets to be selected for list items (close #536). Allow slight alterations to the default widgets suggested by the system without reconfiguring it completely: if the metadata value is blank, assume the default system-suggested widget is to be used and merge the config found in the metadata. Closes #534 (since now only the iconUseState option has to be set to enable dynamic icons for Number items and similar). Change the metadata namespace selection menu to only display the metadata which is set in the metadata menu, and use an action sheet to add more. This also paves the way for user-defined namespaces. Move the metadata order out of the item edition card in the Model page, into its own section. Add metadata editor for the expire namespace (openhab/openhab-core#1620). Reorder the sections of the item details page in a more logical manner (semantic classification below the tags that define it). Signed-off-by: Yannick Schaus <github@schaus.net>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The problem
After selecting a knob or a gauge for a number item, I can't click on the Close button at the bottom of the window.
For the Know, there is no visual overriding but when you click on the Close button, it just selects the "40" value.
For the Gauge, there is a clear visual overriding.
Expected behavior
Keep the necessary space for the selected widget and allow to push the button "Close".
Addtionaly, I am asking myself if the gauge or knob should not be more at the right rather than at the center.
Your environment
Firefox on Windows 10 or Google Chrome on Android smartphone.
Additional information
This looks promising to be able to choose these kinds of widgets.
The text was updated successfully, but these errors were encountered: