James Teh

That's true, though I believe you can save project settings as default for a project. The question is whether we can include custom settings in that.

@ScottChesworth , do you have any thoughts as to whether this should be per-project or global? I think both gets too confusing.

I think some really solid thought needs to be put into the actual user experience with all of these ideas. Regarding saving to an ini file, there aren't that many...

The fact that we're even saying "I guess a fundamental part of this might need to be configurable from the ini file" is a huge UX red flag. It almost...

Yeah, doing global first seems like a sensible starting point. Hold off on hastling Cockos about this one. I'm fairly sure they'll rightly point out that there is already a...

I'm really not a fan of version detection, especially for a project like OSARA where we don't have official versioned releases; users just use snapshots. That makes version numbers even...

I think depending on functionality you can't directly control is fragile. OSARA might support reporting of a marker type, but you don't necessarily know what actions or other behaviour will...

Ultimately, official releases only make sense if there's some quality bar that differentiates them from snapshots. Just choosing some point in time and saying "this is a release" is arbitrary...

The build number really does need to be included for differentiation between failed builds if nothing else. We could probably drop the 2022.1pre though. That's in there because it allows...

I'm not sure modifying the names of the items in the list for this purpose will be popular with sighted users. It's also very difficult to hack names of list...