Erik van Blokland
Erik van Blokland
Not sure how to proceed?
I welcome the discussion, but the consequences of these changes are not clear. So I will close the issue for now. You';re welcome to open it again with more motivation.
@frankrolf do you already have a preference for these names?
Maybe DSE should show a dialog "Save the sources first"
With a standardised place for stem values I can take them along in designspace calculations.
This scheme would facilitate many different names, right? I'd be very happy if we can have at least one thing named stem.
Stems though. Rather than say that we can store anything, which in many ways is already the case, this calls for the the specific. Can we agree on a set...
If we always require a horizontal and vertical value, would it make sense to just store a tuple `(10, 23)`? Also: I'd be in favor of assuming all values in...
More compact, same goal: ```python from pathlib import Path import glob from mojo.extensions import ExtensionBundle DSEBundle = ExtensionBundle("DesignspaceEditor2") dsePath = Path(DSEBundle.path) pattern = dsePath.parents[0].joinpath("DesignspaceEditor*") editors = glob.glob(pattern.as_posix()) if len(editors) >...
But it doesn't reliably work because we have a question in Discord where the old DesignspaceEditor was also installed, but no warnings were presented. If I install an old DesignspaceEditor...