Jump to content

Ian Lane

Vectorworks, Inc Employee
  • Posts

  • Joined

  • Last visited

Everything posted by Ian Lane

  1. Hello, Thanks for the message. We are aware of this issue and I am happy to report that this will be fixed in Vectorworks 2022 service pack 2. This should be released in the next few weeks. Please update to the latest when you can and sorry for the problem that you have been seeing. Best Regards, Ian
  2. Good morning, This problem has been fixed in the SP1.1 build that was released on 10/22/21, build 619242. Please make sure that you are using the latest SP1 release. This was a problem with the initial SP1 release that was released a few days prior. Please let me know if you are continuing to see any problems after updating. Best Regards, Ian
  3. Hi Christiaan, Can you provide some more information on this? We are not seeing this crash anymore. What version of VW are you using and what build? Do you get a crash log? What is the behavior that you see on quit? Thanks!
  4. Kaare, Sorry to hear that you've been having trouble with the feature. Early on we made some changes to make it harder to accidentally detach the tabs but some users reported that they were still having problems, while many other didn't have an issue at all. As Andy shared (thanks!), we added a new Lock tabs option in the utility menu of the palettes. When this is turned on you won't be able to detach or rearrange the tabs. Turning this on won't set things back to the way that they were, so you can move tabs around or detach them and then lock them how you want them to avoid accidental changes in the future. Hopefully this helps you out and thanks for your continuing feedback. -Ian
  5. Hi Ryan, Our general policy is that we never recommend users to upgrade their machine to any beta operating system versions, especially not the first beta that is released. There are almost always bugs in the beta releases that need to be fixed, and keep in mind that things like printer drivers are normally not available immediately. We do not get early access to macOS betas, so our testing just started for Monterey when it became available to us yesterday. We will update our with our findings over the coming weeks as we do more testing with Vectorworks.
  6. Hello, The M1 Macbook Air that we have is the 8GB version. I'm not sure if the 16GB was even available when we purchased this since we got it when they first came out, but I would say that this machine is pretty entry level. Thanks, Ian
  7. Please follow the official thread for the latest updates to our testing efforts on M1. There was an update posted yesterday in fact. Enjoy!
  8. Hi everyone, Thanks for all of your feedback so far. We have been listening and trying to reproduce some of the issues that you have described. The "Dock Tabs Here" option should be available all the time, if you aren't seeing this it could be a bug on our end, but we haven't been able to reproduce this issue yet. If you have any additional info please let me know. We have made a change that will go into VW 2021 SP2 that will make it a little harder to detach the tabs. You will need to click drag a little farther away, so hopefully this will help some of the people who have been accidentally detaching the tabs when they don't intend to. For your future info: Palette positioning is stored in both the workspace and the saved settings files in your user folder. When you open VW and move some palettes around, that info is stored in the saved settings, which takes priority. That way we don't need to create a custom workspace just to save the palette positions. But if you open the workspace editor or run the "Save Palette Positions" menu command, then the positions are written into the workspace also. If you want to reset your palette positions for some reason you can use the Reset Saved Settings button in the VW Preferences dialog box, but you will also have to go back to a stock workspace if the positions have been saved there also. Hopefully this provides some more insight into how these systems work together. Best Regards, Ian
  9. Unfortunately I doubt that Apple Silicon will have any affect on Apple's tools regarding support for older versions of the OS, etc. Apple is very aggressive about pushing the latest updates, and their hardware, software and tools seem to follow this policy as well. As for the universal binary, I would expect that universal binary support will be baked into all releases for a while. It is hard for us to have an official policy on this because we don't know how long Apple will continue to release Intel based machines and how long they will continue to support those machines. A given version of Vectorworks tends to have official support for 5 or 6 versions of MacOS. So for VW 2021, it will run and be supported on 10.12, 10.13, 10.14, 10.15, 11.0 and eventually 11.1 when that is released next year. I do not expect that to change moving forward. Here is a list VW versions and official OS support that we have maintained through the years.
  10. Hi Mau, You are correct that at this time we do not recommend upgrading to Big Sur if you are using Vectorworks 2019. We always like to be proactive and make users aware of the issues that they might face if they decide to upgrade their OS. We want to be transparent and make sure users can make the most informed decision. As Zoomer mentioned, VW 2019 does not run well on Big Sur. And thank you to Christiaan for his detailed post, he explained the situation almost perfectly. We have historically avoided supporting versions two years back and older because of the inordinate amount of effort that it can take and the risk of creating an unstable version of VW that might be worse on the OS versions that it was designed for. Here are some more technical details also if you are interested: The main difficulty with supporting older versions of VW in the newest MacOS versions is difficulties working with Apple’s tools. VW 2019 was built with an older version of Apple's development tools (Xcode) that does not run on Big Sur. It is not safe to try and create a new version of VW 2019 using a new version of these tools because this can introduce bugs and make 2019 unstable. This forces us to work with an older development environment running on an older OS, which makes any fixes difficult because you can’t test and work in the OS that you are trying to fix things for. We will continue to keep our users informed as we investigate these issues and Big Sur is officially released. Best Regards, Ian
  11. Hi Larry, Jeremy may be correct above about your workspace files being corrupted somehow. I haven't seen this particular problem before but it definitely looks incorrect. I have sent you a private message requesting your workspace files so that we can investigate the problem. Palette data is stored in two different places in your user folder, the saved settings file and the workspace itself. If there is saved settings information for a workspace then that is used first, and then it falls back to the workspace if there is no palette info available in the saved settings. This allows for palette positions to be saved without having to modify the workspace file. You can reset the palette positions in your saved settings by using the Reset Saved Settings button on the Session tab of the Vectorworks Preferences dialog, but note that resetting that will also clear out other data. But this is a way to reset those palette positions if that is causing the problem. Another option is to just create a new workspace based on one of our shipping 2021 workspaces. That may be the best solution if you are still having issues. Best Regards, Ian
  12. I will also add that if you don't want to detach the tabs you don't have to, you can just ignore the feature and use the palettes exactly the same way that you used to. The main menu items for the Object Info, Navigation, and Visualization tab families will close all of the tabs together, resulting in the same behavior from previous versions.
  13. Hi Larry, For 2021 we have allowed users to choose what they want to do. There are menu items that will close ALL of the tabs that are associated with a tab family. These are assigned shortcuts in our shipping workspaces and they will function like they used to in previous versions. The CTRL+L shortcut will close all of the tabs that go with the Object Info Palette. That is the Shape tab, Data tab and Render tab. We also added new menus that will allow you to toggle the visibility of each indiviual tab if you want to do that instead. If you want to use these new menus with a shortcut you will have to assign shortcuts to them in the workspace editor, they do not have shortcuts by default. As you can see in this attached screenshot, this is the new palette menu in one of our shipping workspaces. You can toggle the visibility of each tab through this menu. Best Regards, Ian
  14. Hi all, If you are running VW 2019 I would highly recommend NOT to upgrade at this time, as zoomer noted above there are issues with Big Sur in 2019. If you are running VW 2020 make sure that you have SP5, this has some critical crash fixes for Big Sur. The initial release of VW 2021 will be fine to use based on our testing. But as Juan mentioned, Apple is still releasing new betas, so you never know if something will break...proceed with caution! Thanks again for continued testing and feedback, Ian
  15. Please tag me somewhere in this new thread so that I am aware of it.
  16. Yes this is correct, at this time quick search only finds menus and tool that are in your active workspace. So make sure the center line marker is added to the Braceworks workspace first and then you'll be able to find it. We investigated being able to search all other inactive workspaces also but there are many technical challenges related to this.
  17. This is something for a future release. In our opinion, adding more functionality to the nav palette is always a good idea, as long as it can be customized so that unwanted info doesn't get in the users' way.
  18. Sorry for all the multiple comments, just trying to keep the various conversations organized with my quotes. There was certainly a lot of useful info shared over the weekend! Last thing I'll add is that a context aware quadrant for SOD is another one that we have discussed during task planning, so this is a definite possibility for the future.
  19. This is the intent of the detachable tab palettes task and the ability to direct edit in the nav palette. We wanted to give users the ability to keep these lists open all the time and edit the info so maybe they don't have to use the org dialog as often. Our plan is also to support more columns on the nav palette and make them editable in the future. What functionality do you need in the org dialog that you can't get from the nav palette? This will be helpful information for us to have.
  20. Yes I would agree that the workspace editor has been a long standing feature that hasn't evolved much over the years. It really could use a complete overhaul to improve a lot of aspects in my opinion. But even some small features like the ability to drag multiple items from the left side would be a good start. I would recommend that you create a new thread where you outline your requested workspace editor fixes, that will make it easier to keep these together and not get lost with the other SOD or QS comversation. There are two flavors to this, workspace editor improvements and also suggestions for how we should modify our shipping workspaces. Obviously with our shipping workspaces it is impossible for us to create something that everyone will be happy with, but suggestions for changes are always useful. Thanks again!
  21. Hi Mark, Thanks for the feedback. Can you elaborate a bit on why you need 9 different workspaces? I'm a little unclear on that part. It seems to me that what you are requesting is an "everything" workspace that has ALL of our tools and menus already added in. With the new Quick Search tool this kind of workspace could be useful because you can still easily find everything.
  22. There is not currently any setting for this in the preferences. We debated adding this but ultimately decided against it. We worried it could be preference overload. But perhaps in the future if others think this would be useful!
  23. I can confirm that this issue will be fixed in 2021 SP1. Thanks for your help finding the problem!
  24. Because of the integration with the spacebar for SOD and the pan tool, the interaction is a little tricky. As the spacebar is pressed we are waiting on user input to try and determine if the user intends to pan or launch SOD. If the mouse is moved while the spacebar is down it will invoke the pan tool. It is tricky for us to get the SOD to appear easily while also supporting the normal workflows of spacebar to pan that so many people are used to. We will experiment some more and perhaps we can add a little dead zone around the cursor before the pan tool is invoked. But at least setting a different hot key is working well for you, and that will definitely be the best option in the meantime, especially if you are using the stylus.
  • Create New...