Do you think you could also add this option to move group object when you’ve actually selected it? A lot of times its hard for me to fish out the correct node/line from the big long list
If this is not possible, perhaps you could suggest a better way I can conduct my workflow?
Basically the reason I need it:
I draft my base block, copy and paste the file, and then start making my adaptations like close dart, add ease, change side seam, pockets, etc.
So the issue is that in my base block I add my front to a group and my back to a group.
Now I am working on the front and some things have changed such as the side seam, hemline, and waistband, but others such as the inseam and crotch, etc have not been adapted.
So I’ve added my changes to a new group ‘Front New’ and then want to move my unchanged parts to it too and leave the others behind… if that makes sense?
What I figured out to do in the meantime was I just delete my group before I start working, I still have the opposite group existing and hidden (as in Back when I’m working on front so its out the way) then I add everything to the needed group as I go.
Well I spoke too soon… of course it’s never easy, and probably why I didnt add the move group option the point context menu. When you’re in the Group Manager and select an object you know what source group it’s in. When you select a point, the point can be in any number of groups… so we can’t just say move it to Group “x”.
Lets say there are 3 groups - Group1, Group2, and Group3, and Point A1 is currently in Group1. Well the context menu move items have to be:
Move from Group1 to Group2
Move from Group1 to Group3
Lets then say A1 is in Group1 and Group2… now the options have to be:
Move from Group1 to Group3
Move from Group2 to to Group1
Move from Group2 to to Group3.
As you can see the more groups, the more complex the context menu gets.
This one took a little bit of thought… had to reconfigure the context menu to provide the source and the destination group id’s, unlike in the group Manager Object list where it just needed the destination group id’s.
Thanks @Douglas ! Just curious, why was the option for adding an object to multiple groups created? I’ve never seen it in any other software and so far haven’t found a use for it so I guess now that the topic of discussion is there I’d love to come to understand its use case
It was created before @Douglas became our programmer and I found it extremely useful and still do. I’m be crying very big crocodile tears if it gets removed.
I really wasn’t trying to make it sound like thats what I was suggesting
Basically was just saying I’ve never used it yet, there’s so much stuff on Seamly that I’m like I wonder what that could be used for??
Here, you can see that I have my Basic sleeve in a group. This sleeve fits into the armhole of my bodice. If I want to print a pattern with this basic sleeve, all I have to do is to open the Eye on the group and I can select all the points without any distractions from other construction points. I can see the outlines very easily.
This is something that it will look like if I didn’t have things in different groups:
So that’s all in one pattern and sometimes, the objects get shared but for neatness sake, it’s easier to see when things that you don’t need to see aren’t visible while other things that you do need to see may be in another group with a whole bunch of other stuff that you don’t need to see. So those things go into a 2nd group, even while drafting, to keep things clearly visible and not lost in a whole bunch of other “stuff”.
I didn’t program the initial groups, so I’m not sure why it was created that way. It goes against the way you would normally program a nested parent-child behavior. To me it’s like Schrodinger’s cat, where the cat is in 2 places at the same time. Except in the case it could be in 3, 4, 5 or more places atthe same time. To me it then becomes a nightmare keeping track of which combination will show or hide an object. If a object is in 1 group things are simple - it’s like a light on a switch - it’s either on or off. If there’s a parent, it’s like a breaker… turn a breaker off, all the light on the circuit go off. The main breaker is like the parent to the all the breakers… turn it off, everything goes off. Imagine if your house was wired so that every light could be on more than 1 switch, and you had to know which switches to flip to turn a light on.
I think that the bottom line is, whatever I’m given to work with, I’ll find a way to make it work for me. If it takes the software forward by changing the group behaviour, I’ll always be happy to change the way I work.
The “Download Latest” link at the top of the forums should give you links to latest release. If you want to stay on top of any new release - which happens every monday (late sunday night for me) - you can go directly to the Gihub page:
Scroll down and off to the right sidebar you will find the links to the latest release and any “pre-releases” - i.e. builds made during the week when a PR is merged.
Actually I wouldn’t mind it if more users downloaded pre-releases as they can act as beta testers where we might be able to catch bugs before the release comes out.
If you really want to be on the cutting edge you can check out builds in progress before they are merged as an artifact. Click the “Actions” tab on the toolbar:
Which brings up a list of all the workflow runs… That is everytime a PR (Pull Request) is made, Github will run a job and build all the os versions of the apps.
and still do. I’m be crying very big crocodile tears if it gets removed.
Basically was just saying I’ve never used it yet, there’s so much stuff on Seamly that I’m like I wonder what that could be used for??
