legacy editor toggle

[EvenMasait]

From my knowledge, more experienced mappers don't covert to lazer because the changes in the editor were too drastic to their liking, making their hours that they put into muscle memory to perfect the editor worth nothing when mapping on lazer.
I suggest making a toggleable option to enable the legacy editor (aka whats currently used for stable) into the lazer options (disabled by default) so mappers will have an easier time mapping while still being able to use whats more to come with later editor changes.

[cihe13375]

I don't think it's technically possible to add the whole stable editor into lazer code. However, if the goal is to edit the same map with both stable and lazer editor, I think the following workflow is easier to implement:

1. create the map in lazer and edit in lazer
2. convert the map into legacy format (currently not possible, but I think the required logic is already in the code, i.e. compatibility export)
3. edit externally and specify the stable song folder as mounting folder (the second part is currently not possible but should be easy to implement)
4. refresh map database in stable and the map should appear
5. edit in stable
6. end "edit externally" from lazer side after editing

Or maybe reversely, create the map in stable and let lazer support loading maps from an arbitrary folder.

[bdach]

I suggest making a toggleable option to enable the legacy editor (aka whats currently used for stable) into the lazer options (disabled by default) so mappers will have an easier time mapping while still being able to use whats more to come with later editor changes.

This is not how anything works, and also we're not doing it. Please stay tuned for improvements to the current lazer editor such that stable users can migrate to it easier.