> mahdi71, you been around long enough and build more then enough to know various limitations.
> Why has it suddenly become an issue to rant about ?
> > so yes c2 is not so fast after all . and its really not good for big projects.
> That construct 2 is not so fast is more a matter of personal opinion here I think.
> To me it is one of the quickest development tools around.
> And handling large projects is just another skill set you need to acquire.
hi, its not an issue .
people here think i said it can't be done, but i said its just take alot of work for a thing wich can be done by a drag and drop !
just read what i write then tell me if i wrong.
people here answer me with a "lol" becuase they really dont have an answer, i said this things can be done but with much work. just that so i dont need an capx example
Haha, some of the replies were rather short sighted; users glancing your trophies, post count and member status.... and go 'meh must be n00b'.
However, if they took a moment to look at your posting history ^_^
The things you mention, yes, some are tedious, and can be overcome in various matter.
A short sum up:
UI requires a similar approach in all projects to be easy portable.
I would recommend a creation approach; event and actions building and placing ALL the UI elements from an objects-container-layout. (1 layout holding all the objects initial objects)
This way you could easily copy paste an object for UI objects to another project's objects-layout, and copy paste all the events associated with that.
Remember that with families, you can still create the object using the original object name, and in the same action refer to them as the family object in order to manipulate the family values.
Reusable code, well, methods above mentioned show it certainly is possible, its all in the approach.
To retain an objects instance variable, remember you can set objects as global too, just make sure you correctly manipulate its position and visibility appropriately across layouts.
I tend to use 1 invisible sprite somewhere in the top left with a load of instance variables, and the object set as global.
The new local storage ... it just depends on how you use it ...
You could set 1 local storage variable with a global object's instance variables by means of an ASJSON. (mentioned above) And also restore it.
Thus you could save or load unlimited instance variables with a single local storage command.