Jump to content

Kevin Allen

Member
  • Posts

    2,004
  • Joined

Posts posted by Kevin Allen

  1. 11 minutes ago, spettitt said:

    So, a schematic view would be a symbolic representation (somewhat like a hoist symbol in TP) rather than a true orientation of the device?

     

    In my mind, the schematic view of a vertical boom pipe would show what we think of as the top/plan. In your example of some units facing 'front' and some facing 'back,' the schematic plan would show similarly, but with the forward or back orientation indicated. Much like the kind of 2D representation I've always created for booms.

  2. 8 minutes ago, markdd said:

    2d components is there for lighting devices, just about, but it doesn’t work with accessories yet. I filed a bug a while back about that so let’s hope there is a little more development soon.

     

    Mark, I think I saw your post and thought it quite a workaround. Accessories must be included. Of course, I think VWX defines things that aren't actually accessories as accessories. The 2D components need Loci. I need to be able to yoke back, out, or up. The 2D body needs to move with focus.

    I think VWX has long thought SVs are 'done,' while the users have never been satisfied.

    With all due respect to your ability to make them work. I always ask how can I explain this 'feature' to a new user. If I imagine the new user's eye rolling backwards in their head, there is a problem. With SVs, I see eyes rolling, no spinning, like in a bugs bunny cartoon.

  3. Very well presented, but I disagree with you about bonus features and ANY workarounds. No one should have to think about how to get a schematic View, and to be clean, I my opinion, the SV should generally use the top/plan 2D component. Your valid point about the top view above noted. 

    Maybe the concept of 2d components needs to be brought to lighting devices.

  4. 31 minutes ago, DianaK said:

    Why don't lenses in all lighting objects have a “-lense” class assigned yet, so they can render when facing the camera?  

    also, why can't uses control and map the classes provided by VWX.

     

    This is a problem that has been searching for a solution for years. @markdd has one, @C. Andrew Dunning has another. In neither case, the symbol libraries aren't set up to do this.

    • Like 2
  5. 18 minutes ago, _James said:

    I also don't get why they are so convoluted an have wondered if there is any point in having a hyperlink tool over just making the functionality part of the text tool instead - 

     

    the only reason would be the QR code. I also wonder if the text tools need updated code? I would like to se the MacOS spell checking integrated. I have not idea if there is any similar windows functionality 

  6. 16 minutes ago, trevorgooch said:

    Maybe with some clever scripting, we can get an array of hyperlinks automatically pasted on top of a worksheet ToC.   I may play with this a bit.  I seems super clumsy, but maybe with a few laps, a workflow will reveal itself. 

     

     

    Sorry. I do not want to have to work that hard. I also do not want a new feature, odds are that willet gummed up along the way.

    The tech seems to exist in VWX already. The key is getting the tech into the worksheet WITHOUT having to create a new tool that only creates a ToC.

    The reference marker, I might have the name wrong, does this. Place an arrow, point to something, link in the OIP to a viewport, move along. Move the viewport, change the sheet number, etc, the link updates. 

    • Like 1
  7. 1 hour ago, trevorgooch said:

    Struggling to get the back link to behave properly in the pdf,

     

    Maybe a 'back' button, returning to the ToC, where ever it is placed could be in the title block? As long as that does not further slow the title block objects. 

    • Like 2
  8. 14 minutes ago, Mark Aceto said:

    We did not. We ran into some logical challenges, and got stuck within the current constraints. However, I think we got the message across in the NYC user group meeting. @Kevin Allen would you agree?

     

     

    I think so. QR codes have come a long way, but they are not a substitute for an interactive table of contents (ToC) aka Index of Drawings. In my mind, a QR code someplace is an opportunity for a client, a tradesperson, or a colleague to DL a set of drawings. An interactive ToC is a way for people to navigate within the set of drawings, whether that's in a PDF Viewer, VWX proper, or using VCS.

    Two different things. Also the idea of generating QR codes for that kind of navigation is beyond maddening. 

    • Like 1
  9. 2 minutes ago, MrTemplate said:

    each chord has it's own position name, and each chord starts with a unit #1 [except for On and Off Top, which started with a mover, labeled as zero.]

    'liked' only so far as that is an excellent workaround. It will get the show hung, but It won't help you with Vision or other means or pre-program/pre-viz.

    • Like 1
×
×
  • Create New...