Time to add a sixth digit <img src="smileys/smiley20.gif" border="0" align="middle" />

I already did mention and link it here, and it kept being uncommented, so that I feared there is no sense for it.

I'm glad it gets attention at least when posted as a new thread, as it is much to important to not get attention.

Here is a link about arrays and hashtables, incl caps demonstrating them:

http://69.24.73.172/scirra/forum/viewtopic.php?f=8&t=8400

--------------------------------------------------------------

Arima, I wonder why you do it so complicated? Without any further info it seems to be unneccessary (you can just save any hash table to file with the same ease as saving an array).

If the events posted above are complete, then there's an event/condition/trigger missing, that sets the global 'Boss002' to anything other than less or equal 0. Which means, as soon as that condition is met, it keeps being true on every tick.

One solution could be indeed using 'trigger once' with this event:

+ System: Is global variable 'Boss002' Less or equal 0

I'd say, time does not play a role in this scenario. Of all three, ini is the slowest, because it needs to convert strings, but that's a matter of milliseconds per line. As long as the amount of data stays that small you're free to use whatever pleases you the most.

It does detect it and it gives it a "picked" status. That is, it is put on the selected objects list ("SOL"). And you acess picked objects using SOL.objectname:

SOL.spr

http://www.scirra.com/forum/python-refer-to-instance-from-event_topic44898_post281166.html

Another way would be using "getattr", getattr(SOL, objectname):

getattr(SOL, spr).width = self.nW

http://www.scirra.com/forum/function-created-with-python-needs-check_topic45101_post283709.html

I would ask ROJOhound directly as the creator of texture setter, because from what I read about that plugin, it really only uses a texture of another object, not any information of how that texture is used by the original object. A tiled background for example just uses one texture and repeats it, but texture setter will not use this repeating information, I'd say.

First of all, It's totally up to you to ignore the information. That doesn't change anything, CC keeps being one-based, you will just run into more issues with your projects growing. But that's totally your decision.

Secondly, noone said it wouldn't. I just pointed out that event 15 uses a redundant condition. "Animation frame not equal to 0" is always true.

Have a look at this thread for an example. use url as a tag.

http://www.scirra.com/forum/signature-image_topic48203_post302614.html#302614

johnstiles76

I'm confused. Nothing you say really makes sense, overall.

For example, here you say you are a C++ programmer and have "real" programming skills. Well, then it is no problem to work with the event system. I know that. I have "real" programming skills, too.

On the other hand, in this thread you say: "I'm fairly new at C++ but am still in college taking courses." So, you're not experienced?

And while you are fairly new at C++ in 2012, you claim to have done Candy Crisis in 2005. The read-me included there says: "Please, please don't judge my coding ability from this source! The original code was

largely written in my late-high-school/early-college years."

You didn't make any progress over the last 7 years (btw, I don't know much about colleges, it seems to be very hard, if one must study C++ for 8-10 years), and are unable to adapt your programming skills to something as simple as the event-system? You can't download some of the many example caps and start on your own?

I'm confused.

Why does everyone try to set an animation's frame to 0 although the first frame is 1 (CC is one-based)? I'd say, 0 is just undefined and wouldn't recommend using it.

It leads to aftereffects, e.g. in this example above the second condition of event 15 is meaningless, because the animation frame will never be 0 and the condition therefor always be true.

Interesting. I'm so used to do subeventing, that I wouldn't have recognized it. I'm not sure what causes it to behave differently, but it tells me to further keep the subeventing-thingy.