D678: Appending ML version name to firmware version does not work about magiclantern_simplified HOT 3 OPEN

One-shot task with a delay seems an obvious approach (unless Canon repeatedly overwrites it?).

from magiclantern_simplified.

Yep, that's one of the possible answers. In early days, when you accidentally left the huge msleep in startup code - existing solution was working properly.

The only issue with that approach is when you boot with "set" button pressed (with the promise we don't load ML, but really we still do a thing or two) we still would need to run that task to update the string.

from magiclantern_simplified.

I'd have thought it was more intuitive to not update the string if "set" has minimised ML functionality. Does it matter that much which happens?

from magiclantern_simplified.