Neil Barman

@MarkvlWhat Operating system are you using this mouse with? How has your experience with the mouse been during the last couple of months?

I like all three of these proposed changes! #1 does make the posts subtly but very nicely easier to read in sequence. #2 will be great at making it even more clear that Vectorworks Inc team members are active on the Forum, which I think is a very important aspect of this Community. #3 I'm especially keen to see this. There is some really great information here and and being to "compliment" it and its author will help to highlight it for others. (Similarly, being able to tag non-helpful information will also help improve content. If a post gets enough "down-votes" will it be hidden from the thread by default, unless clicked?)

Thanks some big news from this year @JimW! Congratulations! As I know many of the people of whom you speak, I agree that you are very fortunate to have them as part of your community and family. (I feel the same – I just wish you all were a tad closer.) The Vectorworks team (you included!) are a pretty amazing, versatile, friendly and brilliant bunch. I can honestly say that the people at Vectorworks are a major part of the software and they make it a pleasure to use, support and teach the software. Thank you once again for guiding this forum to its new incarnation and making it truly unique and valuable resource for all of us. All the best of the holidays and the coming new year, -Neil

@ThreeDotInteresting suggestion. How do you picture each line item of View history list being presented? That is to say, would each line list each action that was done, or...?

Good idea @Bertf! I have actually seen a number of new users expect this to occur when doing the reshapes you mentioned... It's an intuitive expectation.

Hi Andy, I understand that your colleagues have advised you to stay clear of referencing in the situation you describe, however I have done this a number of times with success. In fact, for one office I worked with recently, I have actually taken an entire project that was (before i arrived) "broken" because it was made with unit plans as symbols (as you are trying to do) and I made the file work properly, as the office had wanted it to work, using referencing. (This particular example was done within one file, however the other example I mentioned in our previous, direct emails had 4 files involved - 1 individual file for each of the 3 unit plans and then one Master file that brought everything and the sloped site together. This was in the days prior to Project Sharing and the units were in separate files so that different people could work on them at the same time.) Your colleagues may have had a negative experience at some point, but I would imagine that something may have been done incorrectly in the referencing process. When done correctly, which isn't difficult, referencing works very well for what you are wanting to do. About #1 - I do understand what you were doing, however the objects that you were putting into the unit plan symbols do not like being in symbols. The referencing technique I explained works great. Using Symbols to do what you are trying to achieve will likely cause you issues. About #2 - As I had requested via our tech support conversation, please do send me (or post here) the actual Vectorworks file you are using. I would like to investigate, but I can't actually examine the use of those objects adequately via the video alone. It appears to be something of a non-standard use of the tool, but having the Vectorworks file in hand will help tremendously. Thanks, -Neil

Just to clarify @AndySmithArch, is your symbol in question actually a typical unit plan symbol that you are wanting to repeat within a multi-unit floor plan, and does your unit symbol contain walls objects as well? From my experience, putting walls and space objects into symbols is not advisable. I have achieved a similar result by creating a layer for each unit type and then referencing each unit's layer into an overall floor plan. @JimWWhat are your thoughts on doing unit plans as Symbols vs repeated, Referenced viewports? And might the text scaling be due to putting a Space object into a symbol, then onto a Design Layer, then into a viewport... Is that simply too much scaling "gymnastics" for text to do?

LOL! I think you might be right about something being blocked/altered by/in/to Safari. The formatting of what is actually remaining in the Safari version also looks wonky ( < official technical term)

It's my turn @Jim Smith! I see what you mean... This is what I am getting in Safari right now... It was working earlier today, but now it's not. In Chrome however, I get this right now... I'm not sure why, but perhaps @JimWknows? Whatever the case, try an alternate browser and see what the result is for you.

It's working for me @Jim Smith

@Wesley BurrowsWhat happens when you import (rather than copying & pasting) the Title Block Border from the source file into your destination file via the Resource Manager?

Mac question: Would/Should the "Uninstall" application do it's job properly and fully if the Vectorworks application folder had been brought over to a new computer vis Time Machine?

Wow. Impressive. And great timing too as I am designing a restaurant right now where I will be using bulbs like this.

Excellent! Thank you Jim for making these available and to all the speakers for their presentations! This year's Design Summit was once again fantastic. I learned so much and it was great to connect with other users from all over the globe. What a great community we've got.

I'm wondering if someone here might be able to shed some light on this... What is the Window (and Door) Schedule's of "Front" and "Back" in terms of the images it displays in a Worksheet? Do "Front" and "Back" correlate to the model views of the same name? Thanks in advance!

@Marc Powell I'm not suggesting the automated Migration process is behind this floating data bar oddity per se. I was just curious since migration does "interact" with the interface to an extent, so I was looking for a possible connection. Migration doesn't seem to be at play so that's not a concern. It does sound like the team at Vectorworks Inc is on top of this one so I'm sure a fix will come in the near future.

Now that High Sierra is “out in the wild” here’s the official word so far...

Here’s the official word thus far...

Hi Spotlight users, I have a workflow question for you... I have a Spotlight user who has pointed out that the previous (v2017 and prior) "Replace with Active Symbol" button in the OIP for a Lighting Device has been changed to "Replace Lighting Device" in v2018. In previous versions, the button simply swapped the active lighting device in the Resource Manager for the currently selected Lighting Device. This meant that you had to select your new Lighting Device in the RM first, then select the placed Lighting Device you wanted to swap out, then click the "Replace with Active Symbol" button. Now, in v2018, the "Replace Lighting Device" button in the OIP brings up the Resource selector... No more need to pre-choose the new Lighting Device in the RM before you press the button to swap it out. However, this change or operation obviously requires a slight change (or perhaps a reversal) of workflow, so it's taking the user some getting used to. Q: Is there still a way to replace Lighting Devices as it was previously done, by pre-choosing them in the RM and "pushing" them to the already-placed Lighting Devices? Thanks in advance! -Neil

Patrick, when you say you migrated your workspace, did you do so by responding Yes to the actual migration question, or did you "migrate" it by another method?

Out of curiosity, for any of you who are experiencing this, when you first ran 2018 what did you answer when you were asked about migrating from a previous version?

Might you still have these available @Christiaan? Thanks, -Neil

This would be a very handy feature! Great idea @David Poiron!

I've been getting more and more requests for this from clients. it would be a very welcome feature.

This would be GREAT... Thanks Jim!