Jump to content

Conrad Preen

Vectorworks, Inc Employee
  • Content Count

  • Joined

  • Last visited

Community Reputation

115 Spectacular


About Conrad Preen

  • Rank

Personal Information

  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Eliot Hartzler You have a bright future as a technical author !!! Really appreciate the contribution Conrad
  2. As you know the ConnectCAD team listen very carefully. And we are moving forwards with all these matters. The input you give here is very very much appreciated. And the time you take to create pictures illustrating these points is well worth it. It's the enthusiasm of this community that keeps me and my team working to make ConnectCAD the best. Thank you all! Conrad
  3. @hihosilvey First of all, constructive comment like yours never causes offence. On the contrary these kind of explorations are what help us keep ConnectCAD out there in front of the rest. And that's why I don't like to force people into a particular workflow. That feels like the tail wagging the dog. In my view the software should support the process you find most natural. We already have plans well advanced to facilitate greater customization of arrow labels. Moving whole chunks of schematic including arrow connections between layers is a technical challenge. We will definitely look into it. But I come back to the fact that the main driver for this need is the labeling of arrows on paper printouts. The old naming paradigm of <layer> <device> <socket> is in any case somewhat dated because now an arrow can appear in a viewport on any sheet layer. That's what needs to be improved. Even a simple reference code like 'A', 'B', 'C' would do fine for navigating no paper. "Customise length and direction of arrows on both sides." Basically the problem is the lack of a control handle at the destination end. It would have to be visible and active when the destination layer is visible and active. And we don't have that facility yet. I'm aware of the issue and if we can fix it we will. Conrad
  4. That is the Vectorworks object name. You can use this as part of Criteria for selections and reports. ConnectCAD doesn't make any use of this any more. Conrad
  5. Hi @hihosilvey I've had a play with your workflow moving selected devices and circuits between layers. You were leveraging the older implementation of arrow circuits to the full. Back in the day the destination arrow was a separate object. The horribly-named Reverse Arrow. Keeping these in sync with their Circuits was a veritable nightmare with a zillion ways to go wrong. But one thing it was better at was being moved to another layer. We re-implemented the arrow Circuit to do it all in one object that can display on more one layer. This is better in so may other respects that I lose count. But changing the layer will need arrow circuits to be re-drawn and polyline circuits to be nudged so they reset after the devices have arrived on the new layer. The actual reason for your working this way in fact has to do with the labels. So here's my question: if you had more flexibility in labeling the arrow ends would you still need to move stuff between design layers? So in your dream CAD system how would your arrow labels be? Conrad
  6. Ok, we'll have a look at it . Thanks for letting me know. Conrad
  7. Yes it's the labels - I thought so. Nice drawing! In pdf the arrows are clickable links so that makes navigation very easy. For paper publishing, I think what you are doing is the best that can be done and it's actually good enough. Did the nudge thing work? Conrad
  8. @hihosilvey yes we are aware of this, and we already have a fix that we are testing right now. Thanks for reaching out! Conrad
  9. Hey @hihosilvey That's an interesting way of doing things. Moving a load of circuits and devices to another layer would need the circuits to reset AFTER the devices. So for this workflow (if it's what you really need) I would suggest adding Select Similar to your workspace (see VW help for how to), select all the circuits and nudge them up and down (shift-arrow keys). That will make them re-detect their end points. Of course I'll add this to my notes for us to look at. Do you know about Sheet Layers and viewports? It seems strange to me to move stuff to another Design Layer for printing. Maybe you have your reasons and I'd definitely like to know them. If it's just for printing though you can have multiple sheet layers with viewports showing different parts of the same Design Layer - perhaps that would suit you better? Conrad
  10. Hi @hihosilvey Sorry if this sounds a bit facetious, but... what about using All Layers Cable Report? There's nothing special about ConnectCAD Cable report commands. They do exactly the same thing as the Create Report command but with only one click. Just to get a better understanding of layer-to-layer connections. The convention we use is that the layer of the source end of a circuit is the Circuit's layer. That way we don't get duplicate entries in an all layer report. You can see this in the Object Info Palette if you select the destination end of an arrow circuit coming from another layer. Hope I've been able to clear that up and do reach out if you need any help. Conrad
  11. Well what Niko suggested was just a workaround ... It seems to me that there's a more fundamental point here. The reason for using ConnectCAD is to save designers time. That's what your boss is paying for - productivity. Yes we like you to be able to customise the look of our software, but it is also vital that ConnectCAD "just works" out of the box without a ton of fiddly clicks. The experience for the new user is very important. It's so easy to get hung up on the details and forget the big picture. Giving you the ability to disappear this text is on my list, please be patient. We need to do this the right way. Conrad
  12. Hi Jan, Funny, I thought I had replied to you about this. You are running up against a limitation of the Vectorworks database itself. And yes, one of my projects is to improve this but the right way is not to work around but to address the fundamental issue. Our Circuit object in effect does the database JOIN that you are looking for. From what you say All that information is in the Circuit object already so you extract it as a report or use our Make Cable Labels command to create a worksheet that you can export to Excel for example. You could probably parse the JOINed table which is a Circuit report and factor it back into Devices, Sockets and Circuits in an external relational database for yet mare flexible reports. That's all I can suggest for the current version. Conrad
  13. @aruk I'm not able to reproduce that gray square here (Mac OS 10.15.7 Vectorworks 2021 SP2) by the way. If you want me to investigate further please PM me the file and show me exactly where to look. Conrad
  14. Is the gray square part of the problem or did you draw it? Conrad


7150 Riverwood Drive, Columbia, Maryland 21046, USA   |   Contact Us:   410-290-5114


© 2018 Vectorworks, Inc. All Rights Reserved. Vectorworks, Inc. is part of the Nemetschek Group.

  • Create New...