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
Not sure whether this falls under the "feature request" or "bug report" category:
For regular widgets the width gets displayed in "dp" (see also issue #1176). When coming close to the border of the screen, this value changes to "100 %" and the widget cannot be drawn broader anymore. That makes sense and is fine, clever approach.
Unfortunately this does not apply to the clock widget which is the first widget and always display on the screen.
For it the unit displayed stays in "dp" no matter the actual width. The value even increases further after the widget already fills the full width of the screen. While the widget itself is not scaled anymore and keeps its maximum extent, the virtual width is apparently not limited.
I'd suggest to use the same logic here as for every other widget: switch to "100 %" near the border and then prevent further increases of width value.
The text was updated successfully, but these errors were encountered:
Not sure whether this falls under the "feature request" or "bug report" category:
For regular widgets the width gets displayed in "dp" (see also issue #1176). When coming close to the border of the screen, this value changes to "100 %" and the widget cannot be drawn broader anymore. That makes sense and is fine, clever approach.
Unfortunately this does not apply to the clock widget which is the first widget and always display on the screen.
For it the unit displayed stays in "dp" no matter the actual width. The value even increases further after the widget already fills the full width of the screen. While the widget itself is not scaled anymore and keeps its maximum extent, the virtual width is apparently not limited.
I'd suggest to use the same logic here as for every other widget: switch to "100 %" near the border and then prevent further increases of width value.
The text was updated successfully, but these errors were encountered: