Sorry for the slow response… been quite busy @work.
Anyhow, I checked and there is no issue with the Seamly2D installation in regards to folder structure. The paths… that is the folders for the pattern, measurements, layouts, and label files are created when you set them in the application preferences. It should be noted that you can either set the path to where Valentina files are stored, duplicate them in a users/seamly2d folder… or create any named path you want. What I posted previously still holds… you will not be able to open files created in Valentina (shortly) after the fork in Seamly2d, but you can the other way around.
It should be noted that there will be a major conflict though once any new feature is added to Seamly2d requiring a new schema version… currently the pattern schema ver is 6.0… if a new feature is added to Seamly2d requiring a 6.1 schema file, it will conflict with Valentina’s 6.1 schema. The way the programs validate the XML files there would be no way to tell the two apart… the program simply looks at the pattern, label or measurement ver and if it’s later than the program can read it won’t open it. That’s a problem though if the programs have different features for a given readable file. It’s why I brought up the fact the file ext should be changed. Either that, or a new element could be added to the Seamly2D schema so that could be used when opening a file to identify it as a Seamly val or vit.
