Reply to Re: sprites-editor\sprites-script
If you don't have an account, just leave the password field blank.
I agree that future updates to source code should be easy to implement, such as using a baseref for a website, rather than hardcoding paths.
In this case though, OP will be deleting the editor created sprites and rercreating these exact same sprites, with a script.
I'm suggesting his alternate script should only be called once the global condition was correct, and would only change necessary attributes to the existing objects rather than replacing them with identical ones.
e.g. If we have sprites 4,5 and 6; we can refer to them as sp(4),sp(5),sp(6) or &man1,&man2,&man3.
Our script then deletes &man1,&man3.
Creates &man3, then deletes &man2, and finally recreates &man1, &man3. This may be different also from OP's needs, but entirely possible.
If the script references at some point by sp(4) then the editor sprite would be &man1, where as the scripted sprite could be &man3, providing no other sprites had been created or disposed of in the interim.
Just the same, I am learning more than I am offering and I appreciate this chance to exchange your knowledge with my ideas. Even a bad idea can be a good thing.
They say the weakest link in a network, is between the keyboard and the chair. With workshare programs, we have increased the number of weak links. The upside is that we will eventually replace the occurence new user glitches with recurring themes.
mm
In this case though, OP will be deleting the editor created sprites and rercreating these exact same sprites, with a script.
I'm suggesting his alternate script should only be called once the global condition was correct, and would only change necessary attributes to the existing objects rather than replacing them with identical ones.
e.g. If we have sprites 4,5 and 6; we can refer to them as sp(4),sp(5),sp(6) or &man1,&man2,&man3.
Our script then deletes &man1,&man3.
Creates &man3, then deletes &man2, and finally recreates &man1, &man3. This may be different also from OP's needs, but entirely possible.
If the script references at some point by sp(4) then the editor sprite would be &man1, where as the scripted sprite could be &man3, providing no other sprites had been created or disposed of in the interim.
Just the same, I am learning more than I am offering and I appreciate this chance to exchange your knowledge with my ideas. Even a bad idea can be a good thing.
They say the weakest link in a network, is between the keyboard and the chair. With workshare programs, we have increased the number of weak links. The upside is that we will eventually replace the occurence new user glitches with recurring themes.
mm
