Import and Anchor

How Do I...?
1

How can I import and anchor an existent pattrn with the same measure table. And acho rthe A to a existent point?

2 Likes
2

You can’t. Due the formulas and unique names for points it makes it a difficult a task to achieve. Importing one pattern into another is likely to cause collison between the point names, which would have to be changed and resolved in the tools & formulas.

The only way this would ever work is if we devise a point naming scheme for specific darft blocks where all the points would have a unique name. For example… all collars might be designated with points begining with “C”, all sleeves with “S”, pockets with “P”… etc.

2 Likes
3

Use case Import:

  1. User triggers the Import function in the file> Import menu.
  2. Application displays file browser from the operating system.
  3. User selects the file.
  4. Application reads the file and lists the labels that have conflict with the file in memory.
  5. Application Displays a list of label in conflict and the anchor option at which point showing the list of existing points in Combobox.
  6. User fills alternative label for each conflict and selects the anchor point.
  7. Application removes conflict verification again.
  8. While there is still conflict. 9. Application re -xes the list of conflicts signaling in red the labels that are in conflict.
  9. Refact Application The import and adds the entire model from the point of origin of the imported model to the selected point of the model on screen or memory.
4

Or it’s only a fraction more geeky to just combine the patterns in XML, assigning them apt new IDs. It’s definitely not something handy enough to put in the File menu –maybe in an Advanced menu, with History. Considering how ill-advised is merely changing the name of a point with dependents, I think this is an issue best left to Seamly2D v. 2.*.*

:unicorn:

1 Like
5

If it were that easy to import another pattern we probably would have figured it out in the last 12 years. There’s more to it than simply changing point names. Every tool also has a unique tool id, and some have a unique object id associated with a tool id… all the dependencies of which also have to be resolved in the XML’s.

Another issue that I’m sure you - as well as others - have not considered is that point names and formulas are translatable… which means there could be another level of complexity if you’re trying to import and resolves conflicts say with a pattern made in German with one made in Portugese.

Also you have to take into account each pattern could be made with different measurement files where both have to be validated AND then resolved between the 2 patterns. One measurement file could be using all known measurements while the other could be all custom measurement names. So in one file you could have @bust_circ_f while the other could custom name the same measurement @BCF.

Then there’s another Gorilla in the room… the units. One pattem could be inches… the other could be in cm.

Minor issue to deal with is pen attributes used could be different between patterns.

I’m sure there’s probably other issues I’m not thinking of. :thinking:

Again… In my educated opinion… they only way importing one pattern into another will work is if patterns can be exported in a standard format, with standard point names, standard range of id’s, standard language, standard measurements, and standard untis.

2 Likes