Jump to content


  • Posts

  • Joined

  • Last visited


1 Neutral

Personal Information

  • Occupation
    Design Director
  • Homepage
  • Hobbies
    Design, Music
  • Location
    United States

Recent Profile Visitors

601 profile views
  1. Thanks Larry... Yeah, I'm finding this easier said than done... I wish NNA had some examples to study.. I'm still trying to figure it out... 😵
  2. Ahh.. Okay... Thank you for the reply! I'll give that a try... good to know.. Dave
  3. Fuge


    Thanks Pat.... 👍
  4. Curious if someone can confirm what I'm seeing with the following script. Below.. I'm wanting to select an object and make it a child of a PIO. It appear from the testing I've done that the PIO has to already exist, or exist on the layer, before it can be made the parent. It appears the PIO can't created during the script, and isn't realized yet... for CreateDuplicateObject to work. If the PIO already exists on the layer and selected with the other object to be made the child, CreateDuplicate works fine.. Maybe I'm missing something... but I'm wondering how I can make this work if the PIO isn't already on the layer prior to running the script. What's a workaround or another approach? Should the PIO be made a symbol.. Would making it into a symbol, and inserting the symbol during run behave different since I wouldn't be "creating" it since it would already exist?! Thanks!! PROCEDURE SetParent; VAR h1, h2, hPIO, DupObjh: HANDLE; ObjName :STRING; BEGIN { Select an object, run, script adds the PIO, Does not work 😞 } ObjName:= 'TESTPIO'; h1 := FSActLayer; hPIO := CreateCustomObject( ObjName ,0,0,0) ; SetSelect( hPIO ); DupObjh := CreateDuplicateObject( hPIO, h1 ); { Sub this... On the active layer, select an object, then select the PIO, run, works } { h1 := FSActLayer; h2 := NextSObj(h1); DupObjh := CreateDuplicateObject(h2, h1); } END; RUN(SetParent);
  5. Fuge


    Thanks Josh... I did further Scooby-doo-ing around but didn't find anything about bitmap interface... It doesn't appear to be very well documented. Appreciate your time... Dave
  6. Fuge


    Curious if anyone knows anything about RunImageComp? I don't see anything online about it... An example would be nice! I'm looking to create a thumbnail of the active sheetlayer outputted at a predefined size saved at a predefined location... Of course I realize i can do something with Publish but would rather not for this solution. 🙃 Thanks! Dave
  7. Ahh... Yeah... Good Idea Pat.. Then the Worksheet can have =COUNT+('Part'.QTY) Thanks for chiming in again... Dave
  8. Hey Maarten, Thanks for your reply.... Due to what we do, the components in the end, probably won't be screws... that was just an example of what a component could be. When I mention PIO inside a PIO... I was thinking It would be nothing more than a dummy PIO.. My thought is it wouldn't have any geometry, it would just be there to be duplicated in a For loop and would have a record attached to it, as you mentioned, for the the Worksheet to count. Appreciate the ideas guys!! thanks for your time..
  9. Thanks for the suggestion Pat... Seems there's not really a clean simple way of doing it. I was thinking inserting a PIO inside a PIO, or even just a locus3D and multiplying it within the PIO. The PIO i'm creating could have 12 of this, 4 of that and so on... so it could get messy fast whichever way it's done... Another program I was using has a special function for doing something like this... One of the few things I like about the other program... Hence why we've moved back to VWs. It would be great to see a built-in function for this... something like QTY( LnewObj, 12 ); 12 of the last new object... super simple! Dave
  10. Hey Guys, Does anyone have a clever way of creating a PIO where you have a large quantity of a component without having to create geometry of each inobject instance? For example, If you had a BOM and it required 12 screws... I don't want to create 12 instances of the screw, Maybe only one... but have my worksheet count a quantity of 12, but insert only 1 instance of the PIO (with a variable = 12) into my document. Hope that makes sense... Thanks for any insight... Dave
  11. It would be great if we could select a bunch of objects on a layer and create a view of only those items. This would allow us to always only work from 1 model and not have to worry about creating a duplicate model or assembly with different classes etc as a work around.....
  12. Okay I've done some more digging and testing, and found that you can attach a texture(s) to a PIO. If you use SetTextureRefN the result is the same as selecting a texture on the Render tab, however the Render tab options for textures ends up getting changed bit for the PIO depending on the texPartID flags you use. Thought I'd share what I found to hopefully save someone else some time in the future! Thanks!
  13. Hi Everyone... Which VS call do you use to attach a texture to a Plugin Object? The effect I'm looking for is the same as when you manually choose a texture on the Render Tab of the Object Info palette as shown below. Thanks for the help! Dave
  14. Thanks Josh... Much appreciated.. I ended up using CreateDuplicateObject... It works great! Dave
  15. Hi Guys... Am I missing something? I don't see a procedure available to create a symbol from a selected object. MySoonToBeNewSymbol := LSActLayer; The only way to create a symbol from what I see is using BeginSym, EndSym... Seems like there should be a way.. but it appears not to be available... Looking to automate creating a symbol from imported geometry. I see the XT import can now create a symbol, but it creates a symbol from the import for each geometry group within the file. I want 1 symbol. Any insight is appreciated... Thanks! Dave
  • Create New...