Posts: 7,806
Joined: Feb 2013
Reputation:
1,486
2018-03-01, 14:19
(This post was last modified: 2018-03-01, 14:20 by jurialmunkey.)
I used diffuses for rounded corners pretty much everywhere in Arctic:Zephyr and it's probably one of the fastest skins out there. There is a slight cost, but not that much. Focus more on reducing the number of textures, texture resolution, number of controls, amount of animations, complexity of animations, and number of visibility conditions. Anything that auto-scrolls makes the screen re-draw and will cost CPU. Try to avoid String or Integer checks (e.g. String.Contains or Integer.IsGreater) where possible if another boolean can be used instead - e.g. ListItem.IsParentFolder is probably going to be faster than String.Contains(ListItem.Label,..) because the former is just a true/false flag, whilst the latter has to constantly check the string to see if it contains the label.
The big thing I've noticed is that visible conditions are quite costly, so you want to reduce them as much as you can through a combination of variables and conditional includes.
Don't use multiple label/image controls with visible conditions if a variable will work instead.
If a control (or group of controls) is only visible in certain windows, use a conditional include instead of a visible condition.
Try to minimise the total number of viewtypes available because each additional viewtype is another chunk of code which is loaded into memory and having its visible condition checked every frame. The resource cost really starts adding up surprisingly quickly. If a particular viewtype is only used in MyVideoNav, then make sure you aren't also including it in MyMusicNav. I just did a clean-up of viewtypes in Aura, and moving each view into its own individual include made a massive difference in resource cost (previously I had all the views in one big include).
