New AVS (and APE sdk) build

Originally posted by UnConeD
Justin: I meant, a preset that uses the new trans / movement, crashes the old AVS. Not sure if this is an issue, though other components do degrade more gracefully as 'unknown render objects'.

Ah doh, yeah that's a bug in the old AVS, since mig added new presets. I will update it so it doesn't happen again if we add more,
but old versions are old versions I'm afraid 🙁

Or I suppose I could make it encode it differently so the old version
ignores it, hmm...

-Justin

Originally posted by justin
Also, you can use 'sw' and 'sh' in Trans / Movement.
Try: d=d*0.93 + (((x*sw/2)&(y*sh/2)&1)*-0.3);

Great, I always wanted this. Now I can do a movement that moves the pixel with an even y to the left, and those with an uneven y to the left. Thank you, Justin 😁 .

Originally posted by justin
Ah doh, yeah that's a bug in the old AVS, since mig added new presets. I will update it so it doesn't happen again if we add more,
but old versions are old versions I'm afraid 🙁

Or I suppose I could make it encode it differently so the old version
ignores it, hmm...

-Justin

I don't think this is a problem. Why would someone use an old version of AVS? It's not like anyone now still uses an AVS version without the SSC and Dynmov. 😉

Because they don't have the latest version. Some people still use AVS without dynamove becasue they don't have MMX and have to use 2.47.

really nice, specially subdirs 🙂 thanks justin.

I also notice that pi has been made a standard variable. 👍

The main problem I get with scope editing is the wiping of all variables when you change code... when editing, you lose all your init-variables. This is definitely bad in my book and should be removed again.

1337ness abound 😁

A couple requests off the top of my head:
-Switch the new bitwise operators (| and &) to something different (e.g. the C++ versions, || and &&) so that old presets that used them don't go fuxery. (And update the expression help to show this.)
-Add a bitwise XOR operator
-Add the ability to save code presets, fruityloops style - have a save button at the bottom of a code construct that puts the code into a seperate folder, under a new extention (.acp or something). Making them universal would be cool, so you could quickly bring up a SSC preset into a DM.
-Add a button at the bottom of the AVS config for docking/undocking (small and inconspicuous and under the config dialogue somewhere). It's kind of cumbersome to have to have to go to the AVS window and click "Dock in config" every time...I miss the double-click shortcut 😉
-Kill the var resetting, like UCD said. It really sucks to be editing your code and have to watch it initialize every time you type something (sometimes upwards of 10 seconds, and I'm on a fast comp...). In place of it, put a "Reset vars (local)" button at the bottom of the dialogue, and a "Reset vars (global)" at the top of the AVS config.
-In movement, calculate the user defined movement when it's selected...and put that "Load as user defined" button at the top somewhere so it doesn't go erasing my movements ._.
-GET RID OF THE FUCKING WINDOW SNAPPING. I have no fucking idea why in the hell you decided to put this in but it's really fucking annoying.
-Add the ability to make your own global vars; something like, to make the variable "bleem" global, put bleem* in init. The regs are useful, but I like being able to remember what variables do from their names 😉

Originally posted by Atero
-GET RID OF THE FUCKING WINDOW SNAPPING. I have no fucking idea why in the hell you decided to put this in but it's really fucking annoying.

I thought this was done by Winamp, not AVS.

Nope, it's AVS. 2.6+ does it, 2.5.1- doesn't.

Originally posted by justin
Or I suppose I could make it encode it differently so the old version
ignores it, hmm...
-Justin

Justin, just embed it. If I'm not mistaken, each object in the AVS file has a header ID of 4 bytes, followed by the size in bytes (LongInt). Couldn't you just increase the size value? Or does AVS actually care more about the Null termination rather than the specified size?

And Atero, it's actually AVS 2.6 using Winamp's window system. So it's kind of both involved, as to remove it requires hacking winamp.exe, which is more dangerous than vis_avs.dll. Unless you just put the old code back in, heh good luck!

That's what I meant. Instead of fucking with WA, just get rid of the use of WA's windows. It's useless and stupid and there's no reason it should be there in the first place.