Jump to content

maarten.

Member
  • Posts

    387
  • Joined

  • Last visited

Everything posted by maarten.

  1. 1? there are 3 selection/adjust options. Be sure that the 3th one is selected No idea about the symbols though.
  2. I think i've found my faulth, GetPrefString(158) should have been GetPrefString(178).... My poor knowledge of techincal English has caused me trouble ones again :mad: [font:Times New Roman]PROCEDURE GetUnits ( VAR fraction :LONGINT; VAR display :LONGINT; VAR format :INTEGER; VAR upi :REAL; VAR name :STRING; VAR squareName :STRING ) ;[/font] I still have no idea where this [font:Times New Roman]squareName[/font] stands for in this function... Where does VS get this information cause i think it's wrong... Same with GetPrefString(158), where does VS get this info, for i can't find where i can change this setting.
  3. When i use GetUnits in combination with ObjArea, i get the wrong units. GetUnits give me the wrong units. They give me the curent unit mark and puts a "2" after it. for example: units are in mm square units are in m2 I draw a pio that's 1m2 big, the PIO will give me this information: 1mm2 The same thing happens when i use GetPrefString(158). Anybody an idea what i do wrong? If it isn't clear what i'm talking about: Here's the code:
  4. you're welcome. And to make my answer complete: This only works when your hatch has "Scale dependend units" (or whatever it's called in English) cause hatches with real units will always keep their preview.
  5. It has nothing to do with the zoomfactor but with the layerscale... So if you open your hatch in the editor when you're on a layer with scale 1/500 the preview will almost be invisible, but when you edit it on a layer with scale 1/50 it will be better... It's just a matter of choosing the right scale. Hope that helped.
  6. Could it be that your group contains rotated rectangles, symbols and pio's? If so, those objects don't scale in group.
  7. Be sure that you have it in your workspace (Happend with me too after I installed the program for te first time. For some reason it wasn't in my standard workspace)
  8. Can't you do that with "lock" (in the "edit" menu if i'm not mistaken) ?
  9. Wow, thanks, i didn't knew this!
  10. Thanks for the reply Kevin, I appreciate that a lot! I've changed that line into PioPoly:=CreateDuplicateObject(pioPad,pioHandle); as you suggested. But it still didn't worked. So I stripped down the script to it's minimum. I made a duplicate of PioPoly. To make sure the poly got duplicated, i moved that duplicate a little bit to the right and gave that duplicate a blue fill. Then i extruded that duplicate. So, the poly gets duplicated, it gets moved and it gets it's fill... But it still wouldn't extrude :crazy: When i convert that pio to a group, it shows 2 polys (the one i've drawn and the duplicate (with blue fill)), so i think that that part is correct, no. Here's the code again: PROCEDURE Test; VAR pioNaam : STRING; pioHandle : HANDLE; pioRecord : HANDLE; pioMuur : HANDLE; PioPad : HANDLE; PioPoly : HANDLE; DupliHand : HANDLE; ExtruHand : HANDLE; BEGIN IF GetCustomObjectInfo(pioNaam,pioHandle,pioRecord,pioMuur) THEN BEGIN pioPad:=GetCustomObjectPath(pioHandle); PioPoly:=CreateDuplicateObject(pioPad,pioHandle); DupliHand:=HDuplicate(PioPoly,200mm,0); SetFPat(DupliHand,1); SetFillBack(DupliHand,0,43690,65535); ExtruHand:=HExtrude(DupliHand,0,50mm); END; END; RUN(Test);
  11. I would like to be able to use more then 2 indexes in ARRAYs or DYNARRAYs. We can now only use 2 indexes and that's quite limiting imo.
  12. A good day to you all I have a Path-Pio. I let the pio make the path smaller and if there's a certain Line-Pio that "cuts" trough the pio, the poly will be parted in two (so that way there can be more then one polys in that PIO. (this was just some background information, it has nothing to do with the problem i'm having) Now i want to extrude those polys, but it doesn't work for some reason. I don't think there's something wrong with that part the code 'cause when i do it in a document based script, it works fine. Here's the code for the document based script: PROCEDURE Test; CONST AfwOn = 12.5mm; VAR PioPad : HANDLE; PioPoly : HANDLE; polyHand : HANDLE; afwOnH : HANDLE; PROCEDURE AwerkingBovenOnder(Hand : HANDLE); BEGIN afwOnH:=HExtrude(Hand,0,AfwOn); END; BEGIN poly(0,0,0,200,150,200,150,0,0,0); pioPad:=LNewObj; PioPoly:=CreateDuplicateObject(pioPad,polyHand); AwerkingBovenOnder(PioPoly); END; RUN(Test); This works. The poly get extruded. But if i do the same principle in the Path-Pio, it doesn't work... Here's The code of the Path-Pio: PROCEDURE Test; CONST AfwOn = 12.5mm; VAR {pio} pioNaam : STRING; pioHandle : HANDLE; pioRecord : HANDLE; pioMuur : HANDLE; PioPad : HANDLE; PioPoly : HANDLE; polyHand : HANDLE; afwOnH : HANDLE; PROCEDURE AwerkingBovenOnder(Hand : HANDLE); BEGIN afwOnH:=HExtrude(Hand,0,AfwOn); END; BEGIN {$debug} IF GetCustomObjectInfo(pioNaam,pioHandle,pioRecord,pioMuur) THEN BEGIN pioPad:=GetCustomObjectPath(pioHandle); PioPoly:=CreateDuplicateObject(pioPad,polyHand); BEGIN AwerkingBovenOnder(PioPoly); END; END; END; RUN(Test); And in attachment is the Path-Pio file. As you can see in the Debugger, the Handle afwOnH remains empty. The Handle Hand isn't empty though... Anybody an idea what i do wrong?
  13. If you have Photoshop (or any other program of that kind), you can just draw your drawing in VW like you always do (white background, black lines) and set it to "negative" in PS. An other option: when you're on windows, you can create a new layer on top of your drawing, set its layer transparenty to "Photo-Negative" and draw a black rectangle on that layer... Should be the same effect normally. I'm not completly sure about that last methode, for i haven't used it for many years (last mac version where that was in was VW11, so.... )
  14. click on the image from the finder and hold the mousebutton down. press F12 (to enter Dashboard) and drag (with mousebutton still hold down) the image into the widget. The image starts uploading. You'll get a sound when the uploading is done. From then on, it's copied into the computer's memory and you can paste it where you want.
  15. If i get it right, the symbols only have 3D objects in the 3D part of the symbol and no objects in the 2D part. If so, you should be able to rotate them in every view (even in perspective). So you don't need to use Pat's workaround in this case (but it's a very good workaround if you would have hybrid symbols). So, the only logic explaination i can think of is that you have "stack layers" on. It's this option: (i excuse upfront if misunderstood your question, in that case, don't mind me )
  16. Could it be that you have the option "stack layers" on? if so, turn it of and try again, it should work then...
  17. When you have the dialog to save the pdf, there's a button at the bottom "security options" (or something like that, i don't have the Englisch version). Make sure you uncheck all those options. If that doesn't do the trick, i'm afraid i've no idea.. sorry.
  18. Printing to PDF is standard build into mac OSX. Choose "print" and at the botom of the print dialog there's a button "PDF". Those PDF's aren't locked, so you can put annotations on them.
  19. I've requested it here. Let's hope it will be included quickly! I have a plug in that updates some information in the drawing when the user chooses to print, but i can't make it to do the same when the user wants to export to PDF cause it's not included in VS...
  20. 1 second that! That would also be handy while cropping a viewport. So everything outside the crop should be greyed and it would be even cooler to also be able to snap to those object outside the crop.
  21. I would like to agree here, but i'm not going to. The Dutch version has a command that does what you're asking. It works for some hatches, but for others it's very complicated to find the repetition. Also, you'll end up with a lot of layers and that makes your drawing a lot slower. And because you have so much layers, it's really hard to edit the hatch afterwards. So i rarely use that command. I requested this some time ago and i would rather see this actually: Kick out that Create Hatch Dialog And i want to ad to that: Highlight the repetition too when a line is selected. That way it is very clear what you're doing, especially when you're dealing with complex hatches. The options "rotate in wall/symbol" and "by scale" or "scale independend" should be editable by right clicking on the hatch (in the resource browser) and choose the option in the little menu that apears. An extra option to let the line repeats itself "in line" (like it is now) or not. With that option unchecked, we would be able to let lines with an angle repeat theirselves in a horizontal or vertical way. To make myself a little bit more clear, see the image below (the checkbox is not included in the image, i forgot to put it in, but it should be in the OIP): If you would want to make this Roman Tile hatch now, that line would be something like 1000cm long and it would only show 0,01 of it. You would need to do a lot of calculations before you would know the correct vallues. If we could uncheck that option, we could just draw the line the lenght and angle we want it to be, give it it's vertical and horizontal repeating factor and everything is set. This could also be the same workaround for when we would have other objects then lines to use in hatches. And use other terms for the repeating factors, it's way to criptic and hard to remember. So i would rather have colors or so, that's imediatly visible and the change that you'll make mistakes is much smaller. I also want to give the lines and objects a class, that way you can make a very complex Hatch, turn on all the classes in the viewport when you want high detail or turn most of them of when you want low detail hatches. That way you can also use other colors in your viewports for presentation of building plans.
  22. You probable accidentally hit a short key to the toolbar. You can change/turn them off in the Workspace editor (last tab page).
  23. You can give the variables (almost) every name that you like. Best is to give it a logic name ofcourse. The list of words that you can not use you can find in the VS Language Guide->Lexical Structures of VectorScrip->Reserved Words
×
×
  • Create New...