michaelk

Hmm. I didn't even know that was there. Is this what you are seeing? If you are printing from the design layer: 1. File > Page Setup... 2. Printer Setup... 3. In the Printer Setup dialog box Setting pulldown to Vectorworks 4. Change Scaling to 100% If you are printing from a sheet layer: 1. In the Navigation Palette, Sheet Layer tab, right click on a sheet layer and choose edit OR 1A. Go to the Sheet Layer. File > Page Setup... 2. Printer Setup... 3. In the Printer Setup dialog box Setting pulldown to Vectorworks 4. Change Scaling to 100% I'm not sure why you can't change the scaling factor. I'd try changing the design layer to 100% and then the sheet layers. This screen is optionally presented when you create the sheet layer. hth mk

Command-Shift-4 will turn your cursor into a target-with-a-camera-looking thing. Click, hold, and drag over the area you want to shoot. When you release you will hear a shutter release sound and a screen shot of the area you just dragged over will be on your desktop as a .png file. mk

Where are you seeing a setting for 50% size? Can you post a screen shot?

I never import a dwg directly into my drawing for exactly that reason. You might find this workflow useful: 1. create a blank document. Import the dwg. Make sure the scale is correct. Save and close. 2. In your real drawing create a design layer viewport - external source and navigate to the first drawing. Now that viewport's OIP will have access to all the classes of the original dwg, but those classes will not be in your drawing's navigation palette. The link between the two vwx drawings stays live. So if you go into the source vwx drawing and delete something, the target vwx drawing will update the next time it is opened or whenever you manually tell it to update. hth mk

I didn't look at every SubZero symbol, but all of them that I did look at have 2D geometry with no fill. So when you select it you have to make sure to click on a line - not in the middle of the symbol. And those symbols are set to auto-insert in the class Equipment-Main (that class gets imported with the symbol). So when you switch to your saved view, that class is off. Edit the saved view to make Equipment-Main visible or move the symbol to another class. hth mk

I've also seen that. (It seems to depend on the orientation of the rectangle used to create the extrude??) I usually just rotate the texture after applying it with either the OIP or Attribute Mapping Tool.

There are a couple ways: When editing the texture there is a size field in the bottom left corner. That size is the width of the texture. (Default is 1") If your source image is trimmed to 36", then just make this field 36". (turn off tiling) Or use Set by Image. In the top left corner of the image is a line with a handle at each end. Drag those handles to the ends of a known dimension and enter that dimension. Or adjust the scale in the OIP - Render Tab once the texture is applied. Or use the Attribute Mapping Tool to position and resize the texture once it is applied. hth mk

never mind... .found it!

Can VectorScript access the color picker? i.e., is there a function that asks the user to pick a color? mk

Pat Sometimes I want to change just one format, say make text bold. But if the range of cells has cells with plain text, italics, different font sizes etc., then all of those settings get unified if I make the whole selection bold. mk

This seems to work. Is there an easier way that I'm not seeing? Procedure DoAllCellsInRange; {Badly scripted by Michael Klaers} VAR WSHand : Handle; currentCellRow,currentCellColumn,topRangeRow,leftRangeColumn,topRangeSubrow,bottomRangeRow,rightRangeColumn,bottomRangeSubrow :INTEGER; LoopColumn,LoopRow :INTEGER; BEGIN WSHand:=GetTopVisibleWS; GetWSSelection(WSHand,currentCellRow,currentCellColumn,topRangeRow,leftRangeColumn,topRangeSubrow,bottomRangeRow,rightRangeColumn,bottomRangeSubrow); For LoopColumn := leftRangeColumn TO rightRangeColumn DO BEGIN FOR LoopRow := topRangeRow TO bottomRangeRow DO BEGIN Message(LoopColumn,' ',LoopRow); Wait(2); END; END; END; RUN(DoAllCellsInRange);

I suspect it may be a bug. At first I thought it might be a rotation problem. The objects have larger bounding boxes than it appears they should. In the first image there is a 2D locus inserted. The left extrude is aligned right/bottom. The middle extrude is aligned bottom. the right extrude is aligned left/bottom. They don't line up. If you double click the right extrude to edit, it shows up in rotated plan view. (It may have been drawn in rotated plan view?) Switch to top/plan view and you can see it's original orientation. When I create similar extrudes they add as expected. But not those shapes. The rotated orientation of the original polygon is the only difference I can find.... mk

There is a semi quick way to get rid of the line. Convert the final object to nurbs. The side with the unwanted line will convert to 2 nurbs surfaces. Delete one of them. Resize the the other one. Model > 3D Power Pack > Stitch and Trim Surfaces. Now you have a generic solid without the extra line. mk

I've been looking everywhere for this and I can't find it. What is the syntax for addressing every cell in a range of selected cells? I'm using GetWSSelection to get the selected cells. Is it something like FOR (toprangerow,leftrangecolumn...bottomrangerow,rightrangecolumn) DO something; If only one cell is selected will the FOR statement still work? Thanks mk ps. where should I have been looking for the correct syntax?

I had totally forgotten about that. If I remember, ungrouping just keeps the most current fillet and looses any earlier fillets.(?) I'll have to go back and check. In any case, it's been a long-standing wish list item to have fillet edge and chamfer edge objects keep their history. (and I would add loft objects). But, you're right - good news for ERK - ungrouping should work. mk

1. I'm seeing it, too. The artifact that is at the intersection of all the solids.... Not sure if it's a bug or if there is something about the geometry. When I created 3 shapes with a similar joint they added as expected. 3. No. The fillet and chamfer don't behave like solid additions, subtractions, etc. There is no history. 2. Your best bet is to push/pull the shape back to the original or add solids to get back. You can also use the push/pull to make fillets. (which will also have no history). mk

Ian I'm not familiar with that specific logitech mouse. I use the Magic Mouse all the time as my road mouse. It works fine, but there is a learning curve. You have to learn to avoid any stray touches in the top of the mouse. And I don't think it has an equivalent of pressing the scroll wheel. The road keyboard I use is the bluetooth Matais FK304 (Mac version) http://matias.ca/foldingkeyboard/pc-mac/. It has a weird concept for caps lock, but otherwise it's the perfect traveling keyboard. The desktop mode thing does work. If the laptop is closed with a monitor and keyboard plugged in, then hitting a key will wake up the computer and cause the external monitor to become the home monitor. I've found it useful to use both the laptop monitor and the external monitor in non mirror mode when in the office. Mac will let you choose which monitor has the menu bar. Or you can download a cool little program called MenusEverywhere to put the menu bar in multiple places. http://www.binarybakery.com/ You'll have to get an adaptor for the monitor. Apple loves proprietary monitor connectors. I haven't tried the newest OS yet. I expect VW will have an SP to fix any issues soon. mk

In the Viz palette, right click on a light and choose edit. OR Right click on the light in the drawing. Choose Edit Light... hth mk

That feature is now in the visualization palette. All the lighting devices (both spotlight instruments and generic lighting objects) are listed. hth

The lighting position uses the default text. Make sure nothing is selected (click on an empty space or double hit the X key) Text> .... set your font and font size. That will now be the default text font, size, etc until you repeat the process and change something. All future position objects, text blocks, etc will use these text settings. hth mk

Worksheets don't update until you tell them to. If the worksheet is on the page, right click on it and choose 'recalculate'. If the worksheet is open click the little triangle near the top left and choose 'recalculate'.

I'll have to go back to 2010 and try navigating from a SLVP to a design layer to create a section line to see if it works. For what it's worth, 49 MB isn't a big file for VW. Files sizes 3 to 6 times that size are not uncommon. Especially with 'save viewport cache' turned on. In my experience, VW crashes and slowdowns are almost always caused by a "bad" piece of geometry. Remove or replace the geometry and the performance immediately improves to normal. I still have and still use a laptop with far lower specs than your machine and it has no problems w/ VW. mk

Peter's right, of course. I usually Select a viewport in a sheet layer (usually top/plan) View>Create section viewport. Draw the section line - with or without jogs - double click to end the section line. That's it. What I enjoy about this method is -the section line instances and the drawing labels will automatically number/coordinate themselves with drawing numbers and sheel layers and -there are no section line instances in my design layers to muddy the waters and -both the section viewport and the parent viewport are on the same sheet layer so you can immediately see and (hopefully) understand the results. To edit the section line, you're right, that's just personal preference. Would you rather edit in the design layer or the annotation space of the VP. ---------------- I'm not sure what is causing portamigra's problems. I've never seen that before. He doesn't say where he is drawing the section line, but I'm not sure that it matters. Usually when VW misbehaves like that it's because some piece of geometry is corrupted. 2010 was the first year of the new solids engine. It could be that there is a symbol from 2009 with self-intersecting geometry (often a sweep). And it is possible in DTMs to accidentally include a point that is 2 miles from the rest of the DTM. (I've done both) Peter, wasn't there a bug in the early SPs of 2010 that caused DTMs built from contour lines to go bonkers? (I remember you helping me with a DTM around then...)

Rita Layer links is an outdated method. It is no longer included in most of the workspaces. (It is still in Fundamentals.) Design layer (or sheet layer) viewports are a much better method. However, you shouldn't need either to render. Make sure you have the layers you want to show up visible (not grey) and the layer options set to Show Others or Show/Snap Others. Make sure Unified View is on. Make sure your objects have a solid fill. Render away. hth mk

You can also switch the OIP move from Entire Object to Vertex Only. Use the little arrow buttons and the button between the arrows to show which vertex is active and change vertices. Then you can enter the moves in the X, Y, & Z fields of the OIP.