Jump to content

A.D.K.

Member
  • Posts

    145
  • Joined

  • Last visited

Everything posted by A.D.K.

  1. If I rotate a viewport say 90 degrees, the label legends that read right to left in the design layer are now rotated 90 degrees as well. Surely there is a way to have the text stay upright and/or rotate contrary to the viewport rotation. The "right-reading" and "non-rotating" options in the Label Legend "Edit Fields" pane do not achieve this. Ideally it would be by fixture, but knowing Spotlight you'd have to make a whole new legend to do it. I just can't figure it out. EDIT: Screenshots attached
  2. Will poke around a little more and submit, thank you.
  3. How do you make 2D label legends rotate with viewports? Thanks.
  4. When you duplicate a Label Legend, it duplicates only fields, not layouts. Can we get it to actually duplicate the label legend instead of just the fields pane? Thanks!
  5. @ASagatovVW Here's a new one, with different behaviour. I was making another file to submit with another bug report, and made a special callout class with big text to leave notes for them. The ones I created in class "none", then switched class, took the graphic and text attributes as intended. The ones I created with the intended class active first did not take the text attributes. This is different than what we were experiencing before, so I thought I'd ping you this file in case you want to update the bug reports. There are two classes of callouts in the file attached here: one from the original file for the other bug report (purple), and one for this issue (white). BadCalloutv2_17July.vwx
  6. Latest service pack yes@klinzey . Where do I "send to tech support", please? Edit: never mind, found it.
  7. Can we please get the ability to save build lists in the spotlight fixture summary feature? Thank you.
  8. @ASagatovVW I didn't have that blue applied to anything as an attribute, but attached is a screenshot of my Interactive Appearance Settings. It looks suspiciously like the blue associated with "Object Highlighting - Action".
  9. @Boh Possibly. If we start going down that road, it might actually relate to the separate problem I outlined here. I was able to recreate the ghosting pretty consistently by scaling the layer in that file.
  10. I just tried this, forgetting I had my user and internal origins on the same point. It seems the layer scales around the internal origin. If you Tools > Origin > Locate Internal Origin, and centre your drawing around that, does it scale the way you want it to? Edit: By "centre your drawing" I mean move your drawing so that what you want as a "reference point" is on that internal origin.
  11. @ASagatovVW It happened again! I took a screenshot before restarting. Restart did fix, though interestingly, stripping the file of everything but the text style in question did not. "Console 5" is the original, and has ghosts. "Console 5 Copy" was a copy/paste of the original, and has ghosts. "Console 5 New" was created after, with the target class already active, and does not have ghosts. The ghosts on the original are from a layer scale operation, and those on "copy" are from just moving it. The one visible above "new" is from "copy", but before I renamed it "copy" (in case you're wondering about the size difference). EDIT: I seem to be able to reliably replicate this by scaling the layer. The file is attached, but I imagine you'll get the same no ghost situation as me when you load it fresh. BadCalloutNoDonut.vwx
  12. Thank you for this @ASagatovVW . Those two notes do make sense based on my last hour as well. I've now been making sure the correct class is active when creating the callout, and I haven't had the attributes problem since. I'll try to keep you posted on recurring ghosty problems as they arise. Very much appreciate your help!
  13. @Boh No, all templates were made in 2019. Unfortunately of the 5 or so files I've got running, I can't remember which were made from which versions of which templates, it's been rather evolving with my learning curve. I may very well have bugged out a template somewhere. I'll try tomorrow to clean you up a file that doesn't violate my NDA. Thanks for offering!
  14. @ASagatovVW I'll read up on the Very Great Movements improvement, but it seems like to get stuff done I need to leave it in performance mode. You're correct, when I changed that setting things slowed down (expected behaviour) and the graphic ghosts did not go away (unexpected behaviour). They also persist through visibility, layer, and flyover navigation changes. The ghosting issue, as with the other mysterious graphical issues (like not taking settings) are all resolved on restart. I can't pin down when/how each issue occurs, unfortunately. Sometimes it's one, sometimes another. They do all seem to resolve on restart, but as stated that's not really a reasonable fix; I can't be reopening a file every time I touch a callout. Thanks!
  15. So I can't figure out how to change where the leader comes out of the callout; when I click on the little blue handle where the leader starts and try to move it, it appears to adjust text rotation. That cannot be expected behaviour. You rotate with the rotate tool, and move stuff with the little moving handles. Also "Vertical Position" does not manipulate the vertical position. It kind of bumps the leader up the thing if there's more than one line of text, but "bottom" does not put the leader on the bottom. "Horizontal Position" works just fine. Is this a navigation thing I've gotten myself into? I can't believe I can't manage to make a box with a thing coming out of it that points at another thing. It cannot be this difficult. Thanks, -Frustrated CAD Monkey
  16. Can we please get a way to change the prefix on a load of classes at once? Even better would be a proper parent-child class structure, such that children can (please please make this optional) take attributes from their parents. It's also a little silly that objects can't be in what is ostensibly a "parent" class, resulting in things like [SetName]-Rigging-Truss-Truss. Thanks!
  17. Files were created in vwx 2019. Tried a new file, and this time I'm not getting the ghosting. This instance is refusing to take the graphics attributes (see: screenshot). And just guessing is great, thanks for your help!
  18. Hi @ASagatovVW , Thanks for the suggestion. I had it set to "Best Performance", but when I changed it to "Good Performance and Compatibility" (the middle of the 3 options), I immediately got an awful performance hit (so not a workable compromise, even if it had fixed it). And the blue boxes are still there, despite much zooming and flying over. Also tried turning on and off the class and design layer visibility, and switching to a sheet layer and back.
  19. Hi, Would be very nice to be able to publish to multiple folders at once. Is this possible? Also would be great if the window would show files (not just folders) in the destination folder, instead of just offering that ominous "you might overwrite everything and destroy the world" dialogue. Just a little idiot-proofing that would save some busy neurons. Thanks!
  20. Screenshot of latest ridiculousness is attached. Every single time I insert, edit, or delete a callout I seem to get some sort of graphic ghost or other bug. The attached pic is the three most recent positions for the callout in question, and they won't go away. Sometimes it's these. Sometimes it's disappearing text (despite graphic and text attributes, and class/layer assignments/visibilities/stacking being identical to another, well-behaved instance). Most often they refuse to accept graphic attribute changes. I don't have this problem with any other properties or resources. Yes, they almost always resolve with a restart. But restarting the software every time I want to touch a callout is unreasonable. I don't think I'm doing anything unreasonable to them. I make them one at a time, and so far they're all plain old text, no database link. The second screenshot is my default preferences for new callouts. Have I done something silly that's hard on the program in some way? Thanks!
  21. When I run lighting fixture maintenance, it appears to overwrite fields that have been manually added to the Lighting Device Parameters, or custom records. It does not appear to matter whether the field is text or a number, and/or whether it has a default value. Is this expected behaviour? It kind of smells like it's resetting anything that isn't in some invisible lighting device record.
  22. Can we get the cycle selection and associated highlight features mappable to keyboard commands? There is way too much mouse movement required to bounce around in a group doing stuff to things. It takes longer than manual selection. Thanks!
×
×
  • Create New...