PocketMatrix

Variables are easier to spot this way for the users. Since PPL doesn't declare variables, it's also easier for the compiler to analyze the code this way.

Also,

1) would you use this with say, SetSpriteCollide. Seems like that would be hard.

2) how would you retrieve these properties?

Kornalius,

On the subject of the new operators, will the old text version of XOR still work? Could you please update the precidense page in the .CHM file also?

Brad

The more I am playing around with spriteoptions() the more cumbersome I am finding it. Before I could simply type:

If (SpriteVisible(b$))
blah blah blah;
End;

Now I cannot see an easy way of doing this.

Also, I added a few options to Mario$ in your example. Each time I did a ShowMessage(Spriteoptions(mario$)) all I get back are numbers. How do I effectively use this? I can't use

if (SpriteOptions(b$) == SO_VISIBLE)

can I?

next I was looking over the help file at SetSpriteOptions() and had a questions. What if I want the sprite's shape to be rectangle. I used to be able to simply use SpriteShape(). The only flag I see is SO_OVAL. A user may find themself contantly checking the help file because they can't remember what flags to use. The only other solution I see is to use SetSpritePhysics() and set everything, even though I just wanted to set the shape.

I really thought the old way was more intuitive. Just my lowly opinion

I had a feeling I would get a response like that .
I just think new users would find it SOO much easier the way it was. Very intuitive.

Not to mention I have to change all my code around for the game I was working on

Maybe there are some hidden advantages to having it the new way that I am not aware of.