08-14-2018 21:57 - edited 08-14-2018 21:58
08-14-2018 21:57 - edited 08-14-2018 21:58
I am running into issues where SVG elements have limited values for some reason. for example. A nested SVG tag with an X or Y of > 300 will not render to screen. Even though it contains elements that are located with negative values and should display on screen. An x of 299 displays, an x of 300 does not display.
Another: the gradient rectangle seems to have a max of 300 for gradient-x2 and gradient-y2.
These limits seem like a naive way to optimize graphics and put a limit on more sophisticated techniques.
Are there any ways around this? Or any documentation for these limits?
Jason
Best Answer09-01-2018 09:37
Fitbit Developers oversee the SDK and API forums. We're here to answer questions about Fitbit developer tools, assist with projects, and make sure your voice is heard by the development team.
09-01-2018 09:37
There may well be some optimisations happening which prevent these from rendering.
If you can provide a simple example project I can get confirmation from the firmware team, and see if there are alternative solutions.
Best Answer09-01-2018 14:06
Gold Fitbit Product Experts share support knowledge on the forums and advocate for the betterment of Fitbit products and services. Learn more
09-01-2018 14:06
I've noticed this too. I found it necessary to crop some elements in my code, converting the original into one or more elements that completely fit on the screen. It's a lot of work (and maths!), and rather slow to run when many elements are involved.
Best Answer