my.size

It is a particle flag used to define the size of a particle. I have used it many a time. But now it causes a huge error that crashes SED. I believe this is because it has been double defined in A6 as the screen size as well. I don't know why this problem has just randomly appeared but I would love some amazing code wiz to find a good way around it. Thanks.

I guess no one actually knows how to solve this problem.

no variable has ever been double defined, that's not possible at all. i don't really get what you want. the property of a struct depends on the struct you're using it on. particle.size is as valid as foo.size, for the compiler there's no way for a misunderstanding.

Thats exactly wht I thought but when I type 'my.size' in my particle function two worrying things happen. Firstly when the game runs it crashes with no error message and secondly in the help bar at the bottom it reads the flag as size x y for the screen not my.size refering to particles. The pointer is irelivent its the flag that causes the problem.

effect(efektim1,.....)


function efektim1(PARTICLE* mypart){
mypart.size.....
...
...
...
}

?????

edit: ah sorry, this is lite-c.

Quoting Joey.

Only last week or so, a past slice of this (self) used a compiler, which complained about a double definition.

While user Joey may exist in another universe where unforgivable generalities run rampant, and chaos reins with confusion at its side, perhaps a reference to a specific term like 'scope', 'field', 'member', should be assumed there somewhere.
Ah, locales, languages and translations, but if the source is human, nothing is lost in the transfer.

@sydan
This (self) does not assume that the help bar, it's contents, and SED are directly linked to the engine in such a critical way.

Although the engine may be riddled with a number of nuisances, many may be somewhat out of sight, so for the time being, maybe you could just ignore the help bar, until the source of the crash is found, a better engine is selected, or some more worthwhile task preempts.

Quoting sydan.

Is that really 'your' best guess?
If the solution involves modifying the code there, and other parties have limited access to relevant information, maybe, in that case, replacing the term 'no one' with 'sydan', yields sense (or an approximation thereof for this senseless realm).


After so many occurrences, we're going to have to assume Quadraxas is doing 'that' on purpose.
this.reputation = -255;
this.that[n].reputation -= 55;