> "creating..." forum?
Yes. The "Main support"-forum is for "normal" users, the "Creating ..."-forum is for skin- and module developers. If possible, we're reading and answering posts in all forums, sometimes we're also part of the community
Best regards,
Your Silverjuke-Team
Statistics: Posted by Service-Team — 6. Nov 08, 13:55
]]>
> Skins, Scripts and Modules"-Forum
I wondered when I posted. But as this forum was labeled "support" and the "creating..." forum is labeled "community" I presumed it had to go in support, after all it's not the sort of question I'd likely get a community answer on.
As this was probably not my last question
: do you prefer all skin related support Q's in the "creating..." forum? Regards,
SilverEagle
Statistics: Posted by SilverEagle — 6. Nov 08, 13:40
]]>
> through the items it has once displayed, and not
> just the items parsed on the load off the skin? [...]
No, it always goes through all times in all layouts. This is because, there may be more than one item with the same id, esp. in different layouts.
Best regards,
Your Silverjuke-Team
PS: We've moved this thread to the "Creating Skins, Scripts and Modules"-Forum
Statistics: Posted by Service-Team — 6. Nov 08, 11:28
]]>
Thanks for the tips, unfortunately nothing new...
For your information and maybe some future improvements - although I can imagine it's not exactly everyday usage
:Service-Team wrote:
> ...currently Program.setSkinText()
> (currently the only function using the id markers)
> is not very fast and has to go through all items
> in all layouts on each call.
Am I correct in presuming that it only goes through the items it has once displayed, and not just the items parsed on the load off the skin? That would explain why I see the drop only after I use the layouts.
The weird thing is this: lets say we have layout A, B and C in the skin, all with lots of id-ed text items.
When I do...
program.layout = 'A';
...all is well...
program.layout = 'B';
...uses little bit more CPU, not notably slower...
program.layout = 'C';
...uses still little bit more CPU, not notably slower.
But now when I do again...
program.layout = 'A';
...CPU goes through the roof.
I expected the drop after 'C' was displayed, but it seems textitems on a layout not visible anymore demand more processing than those visible?
Regards,
SilverEagle.
Statistics: Posted by SilverEagle — 6. Nov 08, 10:57
]]>
In common, massive scripting usage may result in a bad performance under certain circumstances.
The number of id= markers should not be the problem, however, currently (currently the only function using the id markers) is not very fast and has to go through all items in all layouts on each call. So setSkinText() gets slower on a large number of items.
I think, theses performance issues will be improved sooner or later, however, as they are just fine for "normal sized" skins this is not the very top point on our TODO-list.
For now, you can try to optimize your scripts: re-use object as often as possible, use as less code as possible and avoid too many calls to setSkinText() in too few time.
These are only very common tips, however, maybe they can help you as well.
Best regards,
Your Silverjuke-Team
Statistics: Posted by Service-Team — 6. Nov 08, 10:36
]]>
]]>