Jump to content

SamIWas

Member
  • Posts

    305
  • Joined

  • Last visited

Everything posted by SamIWas

  1. If you're in a sheet layer, then you need to select the render option in the Object Info Palette. As for the original topic, I've never understood why hidden line takes so freakin' long. Read above about it doing full calculations, but find it crazy that there hasn't been a simple line render before.
  2. I've been trying for more than a decade to get Vectorworks and Filemaker to talk using ODBC. Not with Vectorscript, but just through their built-in options. I was successful like one time many years ago for a brief trial on one file. It amazes me how difficult it is to get that working. As for the OP, exporting all of your info should be a pretty simple script. I have a large number of scripts which import information out in tab-separated files for import into Filemaker. They all use the calls Sam Jones specified above: Open(filename) PutFile; Write; WriteLn; Tab(1); A quick example of just the write lines: Write(GetRField(h,'LED Ribbon','ID'));Tab(1); IF GetRField(h,'LED Ribbon','Location')='' THEN WRITE ('-') ELSE Write(GetRField(h,'LED Ribbon','Location'));Tab(1); IF GetRField(h,'LED Ribbon','Position')='' THEN WRITE ('-') ELSE Write(GetRField(h,'LED Ribbon','Position'));Tab(1); These are all using the same record format, but you could use any number and mixture of them.
  3. Sure. Then that goes back to designing my VW plot layer or class structure around the grandMA patch: Having to build classes solely for patch. Then I have to make sure all those classes are turned on or off in whatever viewports and saved views. That is a LOT more work then just being able to specify a patch layer in a user field.
  4. Thanks Raymond. SetFPat did work to put white behind he text. It just means adding those lines for every piece of text in the PIO, which is a little annoying. But, the important thing is that it works!
  5. Not sure I follow. The plugin gives you four options for exporting layers from Vectorworks to MA: Design Layers, Classes, Fixture Type, or Position. Now, I don't know how you draft your plots, or how you do your layers on MA. But I know that my plots have layers for scenic, rigging, fixtures, cable, racks, etc. And I have classes for lots of things, but I do not class fixtures based on layer. In no way would I design my Design Layer and Class structure around exporting to MA, so those two are out. Fixture Type and Position remain. On MA, I have layers separated by "genre"...so "Conventional", "Movers", "LED", "Worklights", "FixtureMart". Since those don't jive with anything I would do in Vectorworks, those are out. I'm not sure how having a user field for layer is entering data twice. Where am I entering the layer info in the patch and a user field?
  6. Did you go into the data tab of the Object Info Palette? If you don't see the fields there, then you definitely have an issue. If you want the data fields on the shape tab, then you have to create a custom plug in object, which is a whole different animal.
  7. I have a PIO that I've created which has some text elements and those text elements must have a background fill to be readable. My VW preferences are always set to create text without background fill, and unfortunately, this appears to affect PIOs regardless of PIO code. This is a snippet of the code: FillPat(1); FillFore(65535,65535,65535); FillBack(65535,65535,65535); PenPat(2); PenFore(objcolor); PenBack(objcolor); TextJust(2); TextVerticalAlign(3); TextFont(GetFontID('Avenir Next Bold')); TextSize(18); TextOrigin(0,0); CreateText(concat(distbase,CHR(39))); No matter what I set FillPat two, it doesn't seem to make the text have a fill color. I'm not finding something to set the fill color attribute to "solid" without using FillPat. Am I missing something?
  8. This could be done as a plugin object, which would give you more control, or as a simple symbol with a record attached, which would be easy and could be made in minutes with no scripting involved. For the simple symbol, do the following steps (not detailed with every step): Draw your symbol as it will be needed, with the text formatted in place Select all objects involved, and create the symbol, being careful to select the right insertion point Create a record format with the fields you need to change in the symbol such as height and depth (in this case, it will only change the visible text labels). Add fields to the record format of the number type, and format them as a dimension. Edit the symbol Make sure nothing is selected in the edit symbol window and attach your new record format in the OIP. Select each text field then use the "Link Text To Record" command to assign a record field to a text object. The attached file has an example. Data Symbol.vwx
  9. This is absolutely possible and something I do daily. If you're trying to copy and paste a large number of items I've had it fail on more than one occasion.
  10. I feel your pain. If you were scripting it, you wouldn't have to even go as far as adding the locus and whatnot. The script would simply get a handle to the object, get the coordinates of the object (which would be the insertion point), then use HRotate(90) to rotate the object 90˚ counter-clockwise about that point. PROCEDURE RotateObject; h : HANDLE; sx,sy : REAL; BEGIN; h:= FSActLayer; GetSymLoc(h,sx,sy); HRotate(h,sx,sy,90); END; Run(RotateObject); At one point, when keyboard commands actually worked reliably, i had mapped a version of this script with 5˚ increments to my scroll wheel, so I could select a fixture and rotate it using the scroll wheel.
  11. Thanks guys. I think I got it worked out. I delved into what I assumed was the offending symbol, and did some work on it. Turns out that the guy who built it modeled everything down to each pin on each fluorescent tube in the fixture. And those pins were mesh rounded cylinders. Two pins each end of each tube, times 8 tubes per fixture, times 120 fixtures = 3840 high-poly little pins that aren't even visible, but still being processed. Also found some geometry which was rounded but could get away with a low-angle chamfer instead. Once i did that, I went from several minute per setup to maybe 8-10 seconds each time. I'm working in someone else's template on this production, so I'm working with what I'm given.
  12. I fixed it automatically going into OpenGL, which has helped somewhat. I guess that was my main issue. Still...it shouldn't take over and not let you stop it. But even when starting a render on a viewport on a sheet layer...sweet jesus...can't do anything else. Which is odd, as I thought that worked in the background. I'm definitely going to go through this symbol library I was given and clean it up. There's no reason it should take almost 10 minutes to process the geometry for about 100 Image 80s. The MacBook is the highest-level one made, so it does have a real graphics card.
  13. I'm working on a file using symbols from someone else. It's his template for him, so I'm not looking to change all his symbols....yet. But seriously....every time I click into a 3D view, a process bar at the bottom-right corner of the green pops up labeled "geometry". It takes literally 5-10 minutes on a high-spec MacBook Pro each and every time. And there does not appear to be a way to stop it. Once it starts, Vectorworks is useless for that period of time. Is there some way to kill this process? I'm sure i can search the forum of a while, but I'm trying to complete these plans.
  14. Currently, yes. That is how the plugin works. That's one feature I do not like, and one reason I don't use it. The VW drawing should not have to be designed specifically around export. The layers should be able to be derived from a user field.
  15. Yeah, multi patched fixtures on the same layer shouldn't create an error.
  16. I really wish the official version would allow patch layers by a user field or something. I really don't like having to design my VW document's classes or layers around the patch.
  17. Thanks guys, Apparently, it was a current-launch bug. Today, the problem is no longer happening. What's also weird is that all of my other PIOs use the same text-scaling procedure, but it didn't work in this one. So I corrected it without the scaling. Today, when I opened up the work file, the text was massive. I changed it to match my other PIOs and now it works correctly. So, it looks like all of that was related to the same thing. It's all working now. Alas...I didn't think to turn it off and back on again.
  18. I have a tool I created for placing exhibit graphics. It's just a simple box and two pieces of text, controlled in the OIP. All of them react to a "Top" or "Bottom" setting in the OIP as well. When I select "Bottom", everything lines up as expected. When I select "Top", the text flies off into space, even though the correct dimension is being calculated. Here is a sample of the script: --------------------------------------------------------------------- {---------------CREATE RECTANGLE-------------} rectwidth := PWIDTH; rectheight := PDEPTH; IF PDIRECTION='Bottom' THEN BEGIN TextOrigin(0,(-.5-RectHeight)); TextVerticalAlign(1); END; IF PDIRECTION='Top' THEN BEGIN TextOrigin(0,(.5+RectHeight)); TextVerticalAlign(5); END; TextJust(2); BeginText; concat(PNAME) EndText; IF PDIRECTION='Bottom' THEN BEGIN TextOrigin(0,(-5-RectHeight)); TextVerticalAlign(1); END; IF PDIRECTION='Top' THEN BEGIN TextOrigin(0,(5+RectHeight)); TextVerticalAlign(5); END; TextJust(2); BeginText; dimtext EndText; --------------------------------------------------------------------- If RectHight is set to 1.5", as is default, and I select "Bottom", the PNAME text is at -2" and the dimtext text is at -6.5", as expected by the calculations. If I select "Top", PNAME should be at 2", but the text ends up at 21' 6.56". dim text should be at 6.5", but it ends up at 14' 9.54". Am I missing something, or have I encountered a bug? I don't recall having this issue previously on other scripts. Could it have anything to do with the source number being a dimension instead of a number? Oddly enough, if I put the calculation for one of the top locations in one of the text fields, it shows the correct number, while putting the text off in some weird location. If I need to include the entire script, I will. EDIT: I forgot to mention...if I change the TextVerticalAlign to 1 from 5, the text jumps to the correct coordinates, but is below instead of above that coordinate.
  19. Yep. Most likely the internals of the symbol are in the "None" class. This is very normal. "None" is the default class in every document (along with "dimension"). Your lighting symbol might be in the "Lighting" class, but the lines and polygons that make up that symbol are probably in "None".
  20. Yeah, that's a bummer. When I have some time, I guess I'll have to learn python scripting. I also can't use comma-delimited. Almost all of my data has commas in it. " Edison 12/3, 50' ". And I'd rather deal with working around it than changing all of the data to something uglier.
  21. Okay. Thanks all. I was hoping for something simple I was missing! Seems like that would be a bug, and one that could be fixed fairly easily.
  22. When importing a tab-delimited .txt data file from Filemaker, some fields may be empty. I've noticed that when a field is left black, Vectorworks ignores it and imports the next field in its place. So I have this test data: R1 1ABC 1DEF 1GHI R2 2DEF 2GHI R3 3ABC 3GHI R4 3ABC 4DEF R5 5DEF 5GHI And this simple script to test it: PROCEDURE ImportInfo; VAR filename,recnum,field1, field2, field3: STRING; BEGIN; Getfile(filename); Open(filename); WHILE NOT EOF(filename) DO BEGIN Read(recnum,field1, field2, field3); AlrtDialog(concat('Record: ',recnum,'. Field1: ',field1,'. Field2: ',field2,'. Field3: ',field3,'.')); END; {while} END; Run(ImportInfo); So, when I run that script, the first dialog says: Record: R1. Field1: 1ABC. Field 2: 1DEF. Field3: 1GHI as expected. But, the second run of it says: Record: R2. Field1: 2DEF. Field 2: 2GHI. Field3: R3 So, it has skipped the blank area in the first field of the second record. I have been dealing with this for ten years by putting a dash in empty fields. But, I really want to move past that, as that is error-prone. Since it seems to ignore the field, I don't know how to check for the field being empty. I can't move to comma delimited, and would really rather not move to colon-delimited. You guys are geniuses, so I'll throw this one at you!
  23. Yep...the way mine is currently set up is that is uses IsNewCustomObject() to generate an ID upon creation, looking at existing IDs and adding 1. Then when duplicated, it checks the ID against the object name, which changes no matter what. If those two are different, it changes the ID number. But, this will only happen upon regeneration, which requires changing a field. SO, for now, that's what I do. I'll have to look up how to deal with kObjectCreated/13.
  24. I am not, but that's precisely the item I am trying to disable. When I drop a fixture in, it often assumes basic mode, when my symbol is in extended mode.
  25. When I drop some of my symbols into a drawing, they appear to automatically assume a mode from the drop-down menu. I do not want this, as I have my symbols drawn with the correct information, and Spotlight appears to always put the other mode. For instance, when I drop in a Viper Performance, it assumes standard mode, while I am using extended. My symbol's Light Info Record uses the extended number of channels. This explains why my paperwork was all messed up last show! At some point, I did a replace of the symbols on the drawing, and the number of channels changed to the wrong mode. I do not want Spotlight to assume a mode. Yet I cannot find whatever setting may control this. It does not appear to be in the LIR. Any way to turn this off, or just something I need to change in my workflow? Is it something I set when I made the symbol?
×
×
  • Create New...