We are having an issue with the BusySpinner and Progress Dialog within our applications on certain devices.
The spinners are displaying some strange scaling/translating behaviour. This applies to both the BusySpinner and the default ProgressDialog.
The problem occurs on the new Roku Express, but not on the Roku 4, Roku 3 or older Roku Streaming Stick (not 2016 version). All running on 7.5 Firmware.
We have developed several apps on the “fhd” setting and we never had any problems until we tested it on the new Roku Express.
This appears to be a bug within Roku itself and we would like the Roku Team to take a look at this.
Below you will find some example gifs.
Here we are using the BusySpinner
[upload|kk04JvZFBFQC8XQoJL8xog==]
Here we are using the ProgressDialog without a background
[upload|QNHiXcyMaSK0lPhTIYT+Ow==]
Here we are using the ProgressDialog with the default settings
I’ve seen this behavior on the non-OpenGL devices as well. Our workaround was to turn off most animations on non-OpenGL devices.
One of the Roku sample channels show filtering on Roku models by those whose first digit is 3 or less (2310X, 3500X) but I currently have a whitelist of the supported low-spec devices to apply the shortcut to.
More recently there was a flag ‘optional’ added to Animations which may be used.
I would like to see this bug fixed in the software rendering rotations, though.
“24i” wrote:
We took this example: https://sdkdocs.roku.com/display/sdkdoc/BusySpinner?preview=/4260877/4261069/SimpleBusySpinner.zip
and compared the differences. It turns out that this bug is caused by the “ui_resolutions” setting on the manifest when it’s set to “fhd”.
On “hd” it works fine.
Well this is odd. How can you run example with ui_resolutions=fhd on Express, if FHD UI is only supported on 4k devices?
The issue is not specifically with the BusySpinner, but rather with rotations in general when using the automatic scaling from FHD to HD. Any use of rotation using the “fhd” UI resolution gets mangled when scaled down to HD. The only workaround I’ve found is to either explicitly define an “hd” layout as well, or to use a custom sprite/frame-based animation.
“EnTerr” wrote:
Well this is odd. How can you run example with ui_resolutions=fhd on Express, if FHD UI is only supported on 4k devices?
fhd layouts automatically get scaled to hd on devices that don’t support fhd, so you don’t have to define multiple layouts.
