Markus Barrera-Kolb
-
Posts
343 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Markus Barrera-Kolb
-
-
I thought that this, along with some other things, was what OzCad's Worksheet On Drawing plug-in used to do, but it seems that Julian Carr is not planning on updating it for VW 2008 -- apparently because NNA incorporated some of it functionality into the native worksheet objects... Now if NNA would only incorporate the other capabilities of the plug-in!
-
inveresk -- if I understand you correctly, you're talking about actually using separate wall object to represent the individual components of the overall wall? I can imagine that this would indeed make window and door insertion a challenge, aside from negating any time-savings from using the wall PIO...
-
It seems that wall component joining, as VW currently stands, is a rather spotty thing. However, I'm not quite clear as to what I can realistically expect to achieve. Specifically, if I am joining two walls of different overall thicknesses, say at a 90? corner, that each have outer components of the same thickness, should I expect these to join correctly (because they're not). Is it something I'm doing wrong, or is VW simply not up to the task yet?
-
Is there any way to create linetypes in VW that include characters and/or symbols? In AutoCAD we'd use linetypes with letters to indicate footing drain lines, downspout tight-lines, electrical lines, etc. Representing all of these with just different dash patterns would get pretty confusing. Am I just out of luck?
-
I very much agree on the dash-between-feet-and-inches issue in worksheets, as well as the need for more control over the display of units in worksheets overall (e.g. the ability to override the document's unit preferences). We, like many others, use worksheets for architectural window and door schedules, and when contractors are using this information to place orders, adhering to common standards and ensuring maximum 'readability' is cruical!
-
Thanks Pat, thanks DWorks! Seems like a very useful script -- most of the time my drawing set only has sheets of the same size, but it's good to know that this might be an issue, just in case.
-
Is there a way to update the title block on all sheet layers at the same time if you make changes to the title block symbol? The only way I seem to be able to make the updated title block appear on the drawing border of any given sheet is to re-select it in the OIP for the drawing border, which is rather tedious, especially if you have to do it for the whole drawing set. Really, I don't understand why the changes to the symbol definition don't appear automatically in each drawing border...
-
Is there any way to show and be able to snap other objects while editing the 2D component of an extruded 3D object, such as a floor? When I go to resize a floor and double click it in order to edit its source polygon, everything else is hidden, even though "Show other objects while in groups" is selected. Then, of course, I can't snap to anything else in the drawing, which makes it quite a challenge to modify these things accurately...
-
I take it, then, that in theory you should be able to place keynote tags in a VP while having the notes reside on the sheet layer itself? In any event, bug report has been submitted, test file has been emailed...
-
What happened when I tried to place a keynote in the SLVP annotations while leaving the notes themselves on the sheet layer was that the the notes were automatically resized to match the keynote in the SLVP -- which means that in my case they were suddently 48 times bigger (VP scale was 1/4"=1'-0")! I could change them back to the size I wanted, but then as soon as I added another keynote in the VP, they went back to being huge...
-
I know it's possible to lock the position of a Design Layer Viewport (through a check box in the OIP), which is a great feature. I wish the same was available for SLVPs!
-
1
-
-
Right you are, thanks Pat! It's obvious once someone smarter points it out...
-
It looks like it's currently not possible to place keynote callouts (the tags with leaders) in a viewport annotation and have the actual notes reside on the sheet layer. Unless, of course, I'm missing something. However, this woud be the ideal way of using this tool, IMHO. After all, the keys are supposed to refer to the stuff inside the viewport, and I want them to move with it, but the notes are not and shouldn't. Am I missing something, or should I go straight to the wish-list? Also, what the hell happens when you accidentally delete the note list?
-
Thanks for the scripts! Coming from AutoCad I also find the construction line function useful. The posted scripts seem to be a bit more like the Ray function, in that the line only shoots off in one direction.
I made a humble attempt at a script that would extend it in both directions, by simply scaling the line drawn between the two points (in this case by a factor of 1000). I made the script into a tool, but it'll only let me draw one line. To draw a second one, I have to exit the tool and then re-select it. Any idea why or how to correct this? Thanks!
PROCEDURE DrawXline;
VAR
x1, x2, y1, y2 : REAL;
BEGIN
GetPt(x1,y1);
GetPtL(x1,y1,x2,y2);
MoveTo(x1,y1);
LineTo(x2,y2);
Scale(1000,1000);
END;
RUN(DrawXline);
-
Adding the shim gap to the jamb is a poor workaround for us, because then if we want to show the overall unit size we'll have to do extra math in the worksheet (to subtract the shim gap again) instead of just extracting the appropriate parameter from the PIO. Plus, if we want to generate larger-scale window elevations for the window order, the units will be shown too large.
In the U.S., windows are typically identified by the outside frame size, but we like to show the R.O. on the plans for the carpenters out on the site...
-
I just had a very interesting email exchange with Julian Carr of OzCad, and he sounded very amenable to the idea of adding Rough Opening functionality to WinDoor. This would include scheduling capability for R.O. width, height, & area, as well as the display of loci in plan view indicating the R.O. in the wall, according to the window/door width & specified shim gap. I'll cross my fingers that the next version of WinDoor will include these capabilities!
Come to think of it, if you think this would be a great idea drop him a line and let him know (contact info at OzCad)...
-
It seems that the Custom Modification Tool works spottily, at best. It sometimes crashes the app, and there are times when it modifies only one of the selected PIOs (just experienced this with General Notes objects).
Being able to modify multiple items at once is cruical to an efficient workflow, and really, it should be doable right through the OIP after selecting multiple objects of the same type; but if you're going to have a separate command to accomplish this, it had better work! Please, fix and improve multiple object modification!
-
DWorks has written a great script that updates the date & file name information in a title block. He provides the option of calling the Print command after the update is complete, but I was hoping to be able to call the Batch Print command -- so:
Is there a way to first call DWorks's script and then the Batch Print command? I've tried this script:
PROCEDURE PrintWithUpdate;
BEGIN
DoMenuTextByName('DUpdateTitleBlocks',0);
DoMenuTextByName('Batch Print',0);
END;
RUN (PrintWithUpdate);
but I get this error message:
Error: _1035 _119 - Array ALLOCATE end < start: _97
Any advice? Thanks!
-
DWorks -- looks like I got it to work (with a regular records field from our title block). Excellent script - thanks!
Would there be any way to have the script call the batch print function instead of the regular print function? That would make it absolutely perfect for us, since that's what we use to print almost everything. We'd simply assign P to your script, do all our printing that way, and never have to think about the time/filename stamp again!
p.s. my problems with the Data Stamp had to do with the fact that I'd customized my OS-X time/date format (seems that VW couldn't deal with that)
-
OK, my coworker helped me stumble on the answer for the first question: I'd changed the default date and time formats in the OS, and apparently VW isn't smart enough to handle that. Once I changed the date & time preferences back to a default setting in the OS-X System Preferences, the Data Stamp was able to display both the date and the time. Now it's just how to update the thing...
-
Does anyone know why the Data Stamp tool might refuse to display the date and time, no matter what settings I use? And I've seen various discussions as to how to make the thing update (automatically, in an ideal world) in a title block, but I'm still quite unclear on this.
-
DWorks, do the filename and date just need to be regular record fields attached to text in the title block, or do you have use the data stamp tool? For some reason neither the date nor the time show up in my data stamp, no matter what settings I choose.
-
I've found the stair PIO to be rather inadequate for building anything other than "traditional" stairs. Some of the frustrations I've had are:
? the thickness of floor framing for landing is determined by stringer parameters;
??if the stair runs are not full-width (i.e. the landing is wider and there's a horizontal gap between the runs), then the landing gets this weird 'appendage' that you can't get rid of;
??and as you've indicated, there's not much control over the stringers themselves, especially if you're trying to do something open/contemporary...
I haven't done enough 3D modeling yet, but my conclusion up until now has been that more specialized stairs probably need to be built from scratch.
-
Coming from an older version of AutoCad, I've been wishing for better text handling for a long time. VW is definitely a few steps above what I'd been dealing with, but I agree that linkable text boxes, along with other capabilities such as hanging indents, tables (no, I don't want to have to use worksheets for all of those), and numbered lists would make life considerably easier. Most architectural construction documents incorporate quite a bit of text, so this comprises a significant part of our CAD work.
Extra protection from accidentally deleting viewports
in Wishlist - Feature and Content Requests
Posted
Given that a lot of work can go into a viewport, both in terms of information that's added in its annotation space and in terms of attribute overrides, class and layer visibilities, etc, it would be really nice if there was a way to prevent the thing from being accidentally deleted other than locking the thing.
After all, if you lock it, you have to unlock it anytime you want to do anything to it, which isn't all that convenient. What if the viewport still existed in the Navigation Palette, even if you (accidentally) deleted it from your sheet, and deleting it from the Navigation Palette required you to click through one or two big, obnoxious "Are you sure you wish to delete this viewport" dialog boxes? That would allow you to keep working with the viewport without always having to lock/unlock it while knowing that you're not going to lose all that work through a dumb mistake. Not that I ever make dumb mistakes...