Cloning issues ( mega-topic ) ( partially unfixed )
-
@vectoradmin
For some reason it seems that I did not get the report.
Do you mean that you didn't get a crash report from me? If so, that's because I didn't send one. I always resort to post issues here.
And I cannot replicate error (1).
Strange. Did you try replicating on both OSs?
EDIT:
To be precise, you have to peform the exact same sequence of steps as I did to replicate.
At the very least, what I could observe was that the clone needs to stem from a source object that was created on the reference canvas. And you have to cut and paste from the reference canvas, not any other canvas.
I couldn't replicate under any other conditions.
For example:
Cloning from an object on the artwork canvas, then cutting and pasting that clone to the reference canvas and then cutting and pasting from there does not replicate this.
-
@Nils Yes I tried all these combinations and both on Windows and Mac.
I watched the recording, repeated step by step and still no crash. I'm sure I'm doing something different, just don't know what
-
@vectoradmin I'll see if I can find what makes the difference.
For the future: Would it help you if I semantically augmented sub-topics in either bug or feature mega-topics with subjective priorities?
For example, I'd give this less priority as other bugs in this mega-topic, since it can be easily avoided, while some of the others significantly cripple the creative process.
I can see how this might not be objectively apparent, though, which is why I'm asking this.
EDIT:
Did you perform the cloning via alt + drag aswell? If so, did you ensure the correct duplication mode is set?
-
@Nils said in Cloning issues ( mega-topic ) ( partially unfixed ):
Did you perform the cloning via alt + drag aswell? If so, did you ensure the correct duplication mode is set?
Yes, I set the duplication mode to cloning and then used Alt+drag.
I think it is sufficient to mention a priority (Low/Medium/High) in the bug report. But it is optional, as I will try to fix any issue that can be identified or replicated as soon as possible.
-
@vectoradmin
I see.
But it is optional, as I will try to fix any issue that can be identified or replicated as soon as possible.
Yes, which is awesome. But some bugs are obviously very hard to replicate, while having relatively little impact on the usability of VS. So this could lead to a kind of violation of the well-known "pareto principle".
-
@vectoradmin
Another possible difference:
Are you replicating on a dev build or on the actual release builds as they're downloaded from the website? I replicated on 1.1.026.
-
@Nils said in Cloning issues ( mega-topic ) ( partially unfixed ):
Are you replicating on a dev build or on the actual release builds as they're downloaded from the website? I replicated on 1.1.026.
I tried on the actual 1.1.026 build (in release mode) as installed from the website.
-
@vectoradmin
in release mode
This sounds like there could still be a very tiny difference from what's actually downloaded from the website. I say this, because sometimes bugs creep in in the most subtle ways imaginable.
Did you try to actually download the release, install it and then replicate? Maybe there's something wrong with the upload.
-
@vectoradmin
Found the culprit. Something was wrong with my user data. I deleted it and the bug disappeared.
It could be the actual configuration of settings, though. I will now gradually restore ( by adjusting settings, not restoring files ) my original settings and see if the bug creeps back in at some point.
-
@Nils said in Cloning issues ( mega-topic ) ( partially unfixed ):
@vectoradmin
Found the culprit. Something was wrong with my user data. I deleted it and the bug disappeared.
It could be the actual configuration of settings, though. I will now gradually restore ( by adjusting settings, not restoring files ) my original settings and see if the bug creeps back in at some point.
Actually it these cases it is worth backing up the settings.xml and workspace.xml files from the c:\Users<user name>\NumericPath\VectorStyler1.0\vector\data\resources\ folder.
-
@vectoradmin
I see.
So I have been able to pin this down to the workspace.xml file. After deleting the NumericPath user data folder I tried restoring..
- both ( settings.xml, too )
- only settings.xml
- only workspace.xml
..from the bak.
Only in the case of workspace.xml did the bug reappear.
Any idea what causes this in the file? Might it be the file itself rather than the content? Some suspicion for a specific workspace setting?
I'll try to copy the contents of the file in a new file.
EDIT:
Just copying the contents didn't make any difference ( as expected.. ).
-
@Nils Send me the settings.xml and workspace.xml files by email, and I can try to use those to replicate the issue. (these files contain no personal info, only what has been changed in preferences, and panel states, options, etc).
-
@vectoradmin
Sent you both files as an archive.
Further observations:
I deleted the user data and then restored my workspace manually. The bug then reappeared. I'll see if I can pin this down to a specific aspect of it.
-
@vectoradmin
Was able to definitively pin this down to the Shape Effects panel being open anywhere in the GUI while performing the actions.
The bug occurs when the Shape Effects panel is either..
- visible in its own modal view separately
- in the modal view with the stack of open panels
- visible ( active selection )
- selectable via the hamburger menu
Let me know if you can replicate this.
Current workaround ( admittedly cumbersome ) : Close the Shape Effects panel after any interaction with it or before doing any cloning.
-
@Nils replicated the crash of (1), only on Windows, using the settings and workspace files as they are.
I will try to fix this for the next build. -
@vectoradmin
Hey, please check out my last comment on this mega-topic.
It isn't the files. I've replicated this with the default files. It's the shape effects panel being active as I described above. This is 100% the cause.
