shreyas_potnis

28th April 2003 11:25 UTC

APE version conflicts
i am facing this problem.
i released dynamic cls without the blend modes before.
and now i have completed replace, 50:50, additive and one blend mode which i accidently found out while playing around.

now the problem is:
should i release the new version as a completely new versio with a different id and name or overwrite the first one?

if i overwrite the first one and someone distributes the previous version of the APE in his packs there's a problem.
and if I make a new one, people will say why did he release a new APE just because he added blend modes ? :confused:

AVS Axer

28th April 2003 11:39 UTC

if you use the same name, people will have a tendancy not to instal it, thinking that they have it already.
if you use a different name, they can delete the old one if they want.

Magic.X

28th April 2003 11:48 UTC

just replace the download and add a big fat [updated!] banner ;-)

UnConeD

28th April 2003 15:46 UTC

Include a version resource in the APE... these can be read by installers to determine which version is the most recent one.

Though I don't know if NSIS automatically does a version check when it finds that a file already exists.

Yathosho

28th April 2003 17:32 UTC

Originally posted by UnConeD

Though I don't know if NSIS automatically does a version check when it finds that a file already exists.

jheriko

28th April 2003 19:00 UTC

On another point... try to make your apes backward compatible, i.e. you can still use an avs made with the old version with the new version.

Yathosho

28th April 2003 19:02 UTC

i think you should update all APEs, so they all have that version resource in!

dirkdeftly

28th April 2003 19:38 UTC

it's just "setoverwrite ifnewer" isn't it?

Yathosho

28th April 2003 20:03 UTC

i think "SetOverwrite ifnewer" only checks the date, not the version resource.

edit: i've been playing around with GetDLLVersion, and it works charmingly.

UnConeD

28th April 2003 23:03 UTC

killahbite: I only intend to include the version resource in my other APEs if/when I update them with actual fixes/features.

Simply updating them with the version info will only increase the number of versions floating out there. Until then, you could use filesize as a check... also, an APE with no version info should probably always be considered older than one with version info.

And while you're tinkering with NSIS, could you PLEASE update your script so it pops up a nice "AVS needs to be restarted for the new APE files to work" rather than rudely closing down Winamp (which isn't even necessary btw)? :rolleyes:

Yathosho

28th April 2003 23:43 UTC

the new packs* already have that feature. i'm planning to update all the packs with the next major release of the script (version 3), which will be available to the public then.

* db4, visbot, the y element

shreyas_potnis

29th April 2003 10:45 UTC

ahh, well i think this sovles the problem :)
another problem i had, (now with the APE) is that the combo box where a user can slecet the blend options doesnt drop down! :confused:
i think something similar was the problem with the first versions of multifilter by jherico, can anyone explain?

Magic.X

29th April 2003 12:12 UTC

yeah, i had a problem like that too when i played around with the picture II, but copying and replacing the box solved the prob, so it should only be a wrong attribute or something alike.

UnConeD

29th April 2003 12:45 UTC

shreyas: search the forums :P.
The answer's in the multifilter thread.