You don’t know the struggle of creating a custom Dialog until you try.
You don’t know the struggle of creating a custom Dialog until you try.
BTW: this is the current alpha state of the animations setup.
The Version is going to contain random switching between several animations
]]>« Pierre Hébert I know this is not an easy thing, but: (Previous Post)
D5 Creation
< ![CDATA[
This is looking extremely promising. Amazing work so far with the animation project
]]>
< ![CDATA[
Indeed, I am impressed that you took the plunge in custom dialogs.
Be careful however not to build something too complex, LLX is not designed for this and to be honest I don’t know how it will handle heavy stuff.
]]>
< ![CDATA[
I hope it all works out. Amazing work.
]]>
< ![CDATA[
Pierre Hébert if there are any borders for LLX, I won’t find it in this project…
]]>
< ![CDATA[
No, I think this is somewhere on the TODO list. The idea was to enable box settings for a desktop, same as folders and panels.
]]>
< ![CDATA[
Pierre Hébert I meant borders in the sense of limit, not borders as lines around the screen, lol
]]>
< ![CDATA[
oh, sorry, I misunderstood. Limits are bound by the range of 32bits integers (from -2,147,483,648 to 2,147,483,647)
]]>
< ![CDATA[
you got me wrong again XD
I am talking about limits in a sense of RAM, or heavy stuff, as you said
]]>
< ![CDATA[
RAM is bound by the android virtual machine configuration, heap size (at least on Dalvik). But in some situation LLX also uses memory outside of the heap.
by “heavy stuff” I mean “complexity” more than usage of resources. For instance, you could make use of threads but LLX is not designed to be thread safe in scripts.
]]>