Project Sharing - References

[jgulbrandsen]

Hello,

 

I do Viewport references in the project file. 

If the reference file settings is not "correctly" set up before creating the project file, it seems impossible to update the reference settings itself inside a project file. 

Example if the reference path is set to absoulte not relative, and i want to change this. 

In my working file i edit reference, and this popup "Edit Reference" appears, here i change the settings for Absolute -> Relative patch and locates the file. 
If i also change settings for "Save references cache to disk" , "Automatically update out of date reference during file open" and "Update class definitions". 
Then i hit OK, and then "Save & Commit" my changes. Everything now looks okay. 

I can close my working file, reopen the working file and this settings is saved. 
If I instead (or another user) opens the project file the settings for the referenced file is not changed, and have resetted back to previous settings - the same setting as when the project file was created. 

Other settings for the viewport like classes and layer visibilities do changes if i edit these. 

Same happens if i want to change the reference to another file, lets say it was referenced with a file called "drawing v1" and now "Drawing v2" have been made, i want to swap the file inside the reference, not make a new reference. This is also impossible inside the project file. 

 

Is this expected behaviour or is this a bug? 

If this expected, is this the way it should work, or can this be edited to be possible to change? 

[dpicolo]

Hi @jgulbrandsen

Thanks for reporting this.  This is a known bug and it should be resolved in the upcoming VW2024 Update 7 release.

[jgulbrandsen]

@dpicolo
Thanks. Is there a place to search for known but not fixed bugs? 

This would be great feature, for both customers and Vectorworks I guess. Less work for customers not needing reporting a known bug, and less work for Vectorworks to reply to the same known bugs many times. 

[Pat Stanford]

Users are usually not the best ones to determine if their issue is known or not. You would be surprised by the number of people who post a comment on a 2 or 6 or 15 year old thread with a comment like: "I have the same problem, why hasn't this been fixed" when the entire code underneath has been re-written since the original post and there is no way it is the same bug.

 

Also, while an issue may have been reported, that does not mean that a reproducible case that can easily be used to fix the problem has been submitted. VW would rather have multiple bugs with different samples submitted so they have a better chance of truly understanding and fixing the entire problem.

 

And finally, from a marketing point of view a posted list of bugs would likely be used by competitors. "Don't buy VW, it has 17 known bugs!!!!!"

 

$0.02

 

Personal opinions only. Not related to my work as a volunteer moderator on the forum.

[jgulbrandsen]

Thanks @Pat Stanford
I definitely see your arguments, and i do agree. 

 

This time i posted the bug here, and also used the Vectorworks Bug report site/form.

I normally only use the form to send in bugs, and i think i have gotten a reply only once. So i will never know if it was a bug, or user fault / other reasons. 

Many times i also noticed that this bug report is not on the list for new releases bugfixes, so thats extra frustrating. No feedback, and no fix. 

 

So if i can come up with a different request, i would appreciate better feedback when sending bugs into the form. If this is the preferred method, or i can post them here in forum.  

[Pat Stanford]

I understand. Here is my understanding of how it works

 

Posting to the Bug Submit form formally gets the process started and generates a file in the bug tracking system [Jira]. Unfortunately, there is no automatic response from Jira to the submitter of the bug. This has been asked for before.

 

Entering a bug here works also, but getting it from here into Jira is then a manual operation and the quality of the Jira submittal then depends on someone else understanding exactly what you are seeing/saying and translating it into a form the programmers can understand.

 

If you have a repeatable case in a small sample file I recommend submitting via the form and maybe posting here also to see if another user can help with a work around.

 

It if it more of a general frustration type thing that can't be easily replicated or that you need a work around for, then definitely post here. Or contact Technical Support directly.

 

HTH