[L2Ork-dev] call for mentorship: version bump

Jonathan Wilkes jon.w.wilkes at gmail.com
Fri Jul 10 17:40:54 EDT 2020


Hi all,

I'm porting the "#ffffff" color syntax from Vanilla.

The thing is-- this won't be forward compatible because new patches
will save iemgui color args as symbols. Previous versions will refuse
to read in the new args correctly because they check for floatargs in
those color slots of the arguments. This can give surprising behavior
to users one or two versions behind-- they'll see breakage in colors,
label display, and possibly other problems with patches created in the
newer version of Purr Data. Worse, there's no way to force an error to
be reported in the old versions, as the iemgui arg-loading code simply
fails silently if it gets wrong arg number and/or types.

Vanilla's solution was to put a big "FIXME" comment while turning off
the ability to save the new symbolic color args for the time being.
This creates an insidious bug where users are already inputting the
precise "#123456" colors but continue getting the lossy behavior of
the weirdo integers.

Is this a case for a major version bump? Anything less and I'm afraid
users on older versions won't realize the subtle change in file
format.

Honestly, I'd rather add a line to the file format that crashes the
old versions than have subtle wrong behavior like this.

Suggestions?

-Jonathan


More information about the L2Ork-dev mailing list