Cloning issues ( mega-topic ) ( partially unfixed )
-
@vectoradmin I see. Tbh, I couldn't even get html to render here. If I include any tags here, they are rendered raw. Any idea what's wrong?
-
@vectoradmin FYI: In this new procedure, CEDIT refers to the child-topic, PEDIT to the parent.
-
@Nils said in Cloning issues:
@vectoradmin I see. Tbh, I couldn't even get html to render here. If I include any tags here, they are rendered raw. Any idea what's wrong?
I think that is handled by NodeBB and it converts HTML to code display.
-
@vectoradmin Google led me to this issue in their forum. Quote:
Alternatively you could allow HTML in the markdown settings, but I would highly advise you also install sanitizehtml plugin, otherwise anyone can post anything including malicious scripts as a post in your forum!
-
This post is deleted!
-
This post is deleted!
-
This post is deleted!
-
@Nils Regarding the "Cutting and pasting clone from reference canvas crashes VS"
Did you get a crash report for this?
-
@vectoradmin If you mean a modal view for formulating and sending a crash report popping up when starting VS again, then yes.
-
@Nils said in Cloning issues ( mega-topic ) ( partially unfixed ):
@vectoradmin If you mean a modal view for formulating and sending a crash report popping up when starting VS again, then yes.
For some reason it seems that I did not get the report. And I cannot replicate error (1).
-
@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.
