Ken
-
Posts
655 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Articles
Marionette
Store
Posts posted by Ken
-
-
I second this request.
It's one of the reasons why my fingers catch on fire from pressing those keyboard shortcuts so rapidly. I forget if Shift-C is stock or my own customization, but I use it a lot, along with Shift-V.
On the other hand, boomerang pan has caused me a lot of headache...
http://techboard.nemetschek.net/ubbthrea...64662#Post64880
...so I hope it doesn't create errors and glitches elsewhere.
-
While I agree that your proposal would make life easier for us if it could be implemented faultlessly, the "faultlessly" part of that requirement makes me nervous. NNA still hasn't been able to fix another tool that requires interaction between two coincident objects - the Trim tool.
Though I share your sentiment, Pete, I'm jumping on this bandwagon anyways.
Furthermore, I wish the break line could be used to trim other objects (trim command) such as lines and walls AT THE BREAK LINE instead of at the extent of the squiggly "break height," which is silly.
-
Pitch at blue roof is not the same as at orange roof. Therefore, the valley is not at 45? in top/plan view. Currently I have to do some trigonometry in my handheld calculator to draw the valley angle. And the green arch-top dormer will have to be approximated in the 2D roof plan.
I wish for roof intersections to render as lines in Hidden Line Rendering. In other words, I want to take advantage of the computing power of a CAD software so that things that model easily can be converted quickly into equally accurate line drawings.
-
Sounds like you want Unconstrained Chain Dimension that can turn corners?
-
I would be curious how plainly imported symbols (from file to file) can maintain their original folder structure, not to mention WGR's!
If there is logic in organising symbols into folders in the master, how is that logic invalid in the client? If the alias of a folder in the Finder was not actually a folder but just the files it contained, I would not be happy...
Joel, I didn't mean to imply that there's any flaw in any human brain's logic when used to organize symbols into folders in the Resource Browser of the CAD software application called Vectorworks! [ Laughing Out Loud ]
... When I use the RB to import symbols that reside neatly in their nested folders in a Favorite File, they don't automatically drop into their respective nested folder of the same name in my current drawing. I hope that's clearer.I'm glad you're experimenting with WGR's though.
-
Here are some odd findings...
I've installed the shareware KeystrokeRecorder X, and I open the log every time I catch the mode button going off.
Reading the log:
- mouse clicks and mouse movements are not recorded
- LOPTION is when the option key is first pressed
- [Option] is when the option key is held down as modifier with the next key as logged
- COMMAND is when the command key is first pressed
- [Command] is when the command key is held down as modifier with the next key
- the shift key is only revealed by the next key being in caps (e.g., nudging is not recorded)
- boomerang pan is revealed by a space (which may appear as carriage return in your browser)
- the return or enter key is revealed only by a new paragraph in the log
- v is my legacy shortcut for zoom in
Three different pieces of the log this morning:
xCOMMAND[Command]xCOMMAND[Command]s uLOPTION
There's a peculiar "u" that appears before the option key is depressed -- it did not occur physically.
COMMAND[Command]3c xCOMMAND[Command]su COMMAND[Command]sLOPTION
The same peculiar "u" key appears after saving the file before two boomerang pans then saving the file again. The option-click to Finder is recorded only as an option press.
[Command]] xLOPTION[Option]e[Option]eLOPTIONLOPTIONLOPTIONuLOPTIONLOPTIONuCOMMAND[Command]]xLOPTION[Option]e[Option]eLOPTIONLOPTIONLOPTIONLOPTIONLOPTIONuLOPTIONCOMMANDCOMMAND[Command]]COMMAND[Command]3 c x
The peculiar "u" key appears again during toggling of the eyedrop tool from pick up to put down (while clicking on various objects). The fact that the command key also toggles it may contribute to the problem. The fact that sometimes the tool is NOT called upon first pressing [Option]e may also be part of the problem. The general feel of the eyedrop tool in VW12 is just not as crisp and distinct as it was in 11.
That's three occurrences of the first mode button going off without physically touching the "u" key. My keyboard is stock, standard, kept very clean and works perfectly fine in VW11.5.1, not to mention in every other OS X app and in the OS itself.
-
Perhaps the solution is a new "Symbol Folder Mapping" feature similar to Class and Layer Mapping?
-
It's a bug when you select multiple walls, even if some are hidden with classes. I've reported it as a bug. You should report it too. Sometimes it helps to select ONLY one wall at a time.
-
I would be curious how plainly imported symbols (from file to file) can maintain their original folder structure, not to mention WGR's! When I import symbols I assume they all drop into the top level only. I assume it's because symbol folder naming in each file can be, and is best left as, unlimited.
And this is 12. Unless there's some sophisticated strategy already in place that I'm not aware of?
-
...At least since VW10 the Export to DWG dialog says "Older DXF/DWG versions normally use colors to indicate line weights. Version 2000 files have True Line Weight support, so you may not want to choose this option."
I construed this warning to mean that, by not choosing the "colored line" option, my lineweight data would be automatically embedded in the DWG file by default...
FWIW, the "lowest common denominator" approach was a huge lesson for me in keeping my sanity. All the time I send DXF files to people who claim to be ACAD users. But, as you also mention, ACAD users comprise many different "levels of usage" not to mention many different sub-versions of the software. It's challenging enough to fine-tune WYSIWYG-ness between just two people, one using VW and the other ACAD. Toss in a third person and you get havoc or you start the trial-n-error process all over. You learn to pare down. That's just my opinion.
Having said that, I think you're right about lineweight data automatically embedded in the DWG file! It's been so long since ACAD 2000 that I may have to go through all my trial-n-error iterations again.
As for your re-importing the DWG back into VW12 and not seeing the lineweights, have you tried exporting layers as layers, then re-importing (DXF) layers as layers again (in the Graphic Attributes tab)?
-
You probably mean the Data (Display) Bar?
One way to get i and j instead of x and y is a rotated grid.
- double press the a-key to get the Set Grid dialogue box
- enter angle = 0
- click OK or press Enter key
- press a-key once to exit snap to grid
-
Michael... (sigh). I'm afraid not. I've been using keyboard shortcuts a long time. Nearly every key is taken up on my keyboard. 1, 2, 3, 4 are IMMENSELY useful for Text, Line, Arc, Rectangle. I cannot imagine any VW user not taking advantage of those! I cannot imagine giving up any other key for the lower-demand mode buttons. U, I, O, P and sometimes [ are fine.
The problem, again, has nothing to do with keyboard shortcuts. In fact, you can say that the problem here is that keys on the keyboard SHOULD NOT be affecting the on/off behavior of the first mode when they're NOT USED. Accidental hitting of the u-key that many times for me?! NO WAY!
To answer your question about "nonplot," classes are quickly toggled with the command-arrow-left/ arrow-right keys, so you may have hit command-arrow-right by accident since "nonplot" is directly above "none" -- unless you're talking about the "sills" class which starts invisible upon first inserting a door PIO.
Mark, thank you for confirming. I'm impressed that you're able to see it on a Powerbook! I cannot input data fast enough in my PB with the limited keyboard (awkward numerical keypad) and without my 4-button Kensington trackball.
Katie, thanks for acknowledging.
I vaguely recall a utility for the Mac that actually records keyboard strokes. Perhaps it was a security or spy software. It was in old classic OS. I'll have to search for it if it exists. That's what may be required to track down the cause of the problem. I don't suppose NNA techs use it.
The problem here really may be a quick-use situation, especially of space-x to get out of another tool. It may be related to the response lag of 12.
-
I've had this problem, too, and with many different hardware versions. Yes I think the power of the video card affects it, but to what degree in relation to the complexity of the VW drawing is upsetting. Screen still goes blank for me as described above, but at such a tight zoom that I don't care so much.
Just my 2?
-
Katie, I've been trying to narrow down the list of other tools that I use that may cause it. I think it involves several tools, but quick use of boomerang pan may be the primary culprit.
I'm disappointed that few others notice this glitch. More users have to use keyboard shortcuts and know about "releasing" of a tool/command with temporary press of the space bar. More users have to use the tab key to go into the Data Bar. More users have to take advantage of the Smart Cursor and Floating Datum. More users have to be aware of the "focus" of the app, whether it's on the drawing or in the RB or OIP, and how to control it.
There's nothing else different about my standard VW Designer. I've modified my Workspace by adding a bunch of shortcuts, added back a few legacy commands, eliminated some other default shortcuts -- nothing fancy. In fact, I've only replicated the my settings from 11.5.1.
The fact that I noticed it also in a client's iMac upon a standard install tells a lot.
-
I more than know about the U, I, O, P keys that toggle the mode buttons -- I'm actually wishing for a Vectorscript procedure to call them for my scripts.
You don't seem to get the point. It has NOTHING to do with pressing the U key. Those two modes (in those two tools) keeps dropping their mode selection randomly while I go about normal vectorworking like I've always done since Minicad 6 (and using the U, I, O, P keys as necessary).
The other possibility is that switching mode in one tool (like Mirror) affects the mode back in 2D Selection and Eyedrop, which is still a glitch, if you can imagine that.
This was the first annoying glitch I noticed upon upgrading to 12. I've posted it elsewhere as a side remark several times thinking it's such an obvious glitch, BUT nobody seems to take notice! I've submitted it as a bug, but, of course, they don't acknowledge. I realize few people (here) use the full features, shortcuts and scripts of VW to notice such things.
So yes, I know that the "u" key toggles BOTH of these. LOL.
-
Anybody else notice this bug?
Look again, the first button is sometimes on, sometimes off.
I've reported it, but not sure if they're acknowledging it. I'm not sure anymore if anybody else notices it, but it drives me nuts. I totally dread the next update NOT having it fixed. I've confirmed the odd behavior on a different computer (client's iMac with 12 freshly installed).
The problem is that the first mode button (Enable Interactive Scaling Mode) in the ubiquitous 2D Selection Tool randomly turns off while switching back from other tools in various combination/ sequence/ order. It seems to be related to keyboard shortcuts, especially boomerang Pan (space bar).
The other shortcuts I use (with various mode settings each) include:
- full screen
- normal view
- boomerang pan
- zoom in - marquee
- zoom out - interactive
- previous view
- move
- offset
- 2D reshape
- line
- wall
- join
- break wall
- connect
- insert symbol
- mirror
- eyedrop
Eyedrop also loses its mode setting, which I think is related:
-
... in recent years ACAD has been able to display lineweights on screen as well as in prints...
That's news to me. It's good to know.
I'm from the old school -- where lineweights are assumed NOT wysiwig in Autocad. In fact, I remember when lines thicker than the absolute thinnest in Minicad (0.03mm or 1 mil) exported as a polyline! It has long been corrected, but from those lessons I've stayed with the lowest common denominator, which is to map VW lineweights as colors. Autocad now reads my drawings with hardly any hint of my using VW to create them!
By "mapping lineweights to colors" you simply choose your colors. You should then provide a separate chart or a screen shot of your color choices. VW does NOT produce any special line thickness in the export. The purpose is for the old method (in Autocad) of using colors to differentiate line thickness when plotting.
That's why I've consistently used the same 7 lineweights -- they get assigned the RGB, the CMY and, of course, white/black. Now in 12 I have 3 more to choose from, which means I'll have to choose 3 more "basic" colors.
Now the next feature I'd expect is for the DXF/DWG team to enable direct lineweight mapping into Autocad! They're working on it... I know they are...
-
Glad to eliminate the unlikely possibility of just the dual-processor 2GHz Mac being the problem!
Actually, I'm one of those users who's so tidy... running diagnostics and backing up data regularly, that I notice any slowdown immediately just from feel. I would dread working on files off of a network server let alone not being aware of the performance hit. My comment about the hardware was just half-serious. I'm not connect to any server. My other apps blaze along in blinding speed to witness.
The VW12 sluggishness was noticeable immediately upon installing 12 and getting all my settings in place (way back when). I've since settled upon the trade-off of new features for the quirks and sluggishness (well, almost... still complaining about the quirks, still complaining now about the sluggishness).
In fact, a good reminder is when I go back and revisit my old settings in 11.5.1. The navigation in and out of views and sheets and panning and zooming are amazing sprite.
VW12 is definitely inferior in performance.
-
Yes. Slower for me, too. I use 12 every day. Before it was 11.5 every day. Before that it was 11, 10, 8.5, 8, 7, 6.
12 has the greatest "lag" between tools, screen redraws, boomerang pans, zooms, etc. -- despite my high-end machine, which is most disappointing. It's noticeable (and very annoying) only if you are a VERY heavy user AND use many scripts and keyboard shortcuts to navigate your models/drawings.
I suspect several things:
? some new middle-ground level of code writing for both platforms sacrificing Mac zippiness
? something to do with Quartz imaging
? the prefs for hardware-accelerated navigation and vectorcaching are suspicious in complicating things
P.S.
I notice we're running same machine? My Dual 2GHz is the first version that came out in summer of 2003. Hopefully that's not the reason...
-
Are you familiar with Set 3D View in a regular (design) layer, like perhaps for a layer-linked model? It's command-0 on the Mac. After clicking your two points on the drawing, the dialogue box asks you what those two points are, as in viewer height and look toward height. Insert some numbers, then chose "normal" perspective.
To do so in a viewport, do the same inside the crop edit. The trick is to draw a crop object such as a rectangle. The flyover and translate tools work just the same. Too bad you can't preview the rendering while rotating inside the crop.
-
I've looked at this situation, and Arch.Ken is trying to do something here that doesn't exist in construction, and that is a door with a zero jamb. The "true" KISS is to draw it like it's built...
In practice, the reality is that there are many situations where door trim and jamb should NOT be shown, either in plan view or elevation. One example is when the focus of the drawing needs to be in the area of renovation and everything else (existing) is shown only for context. The contrast should be clear. In elevation view, wall openings should stay equally simple and clean, while the "scope of work" part of the drawing, correspondingly, should be shown with all its necessary information. Michael_E mentioned some other situations. It takes some creativity to imagine yet other possibilities.
Now, there's already the problem of not being able to insert simple doors at its hinge or latch point. Showing trim forces you to insert existing doors at the edge of trim if you have only opening size and want to draft quickly! Or it's some arithmetic with insert at center. This is the reason I started using zero jamb to begin with.
Don't we all wish we had only new custom homes to design --- these "problems" would be irrelevant.
It seems with every new "improvement" and expansion of features, I must create drawings to suit the way that Vectorworks is supposed to be used.
-
Did you apply settings to all new documents?
If you have and it's still not working... or for the similar "general notes" database, I've discovered that if you duplicate the text file and put it where you want it, then DELETE the original one, every new or blank file will go to the new location by default -- assuming that the new location is always accessible.
Also perhaps it needs to be "established" in each computer -- a one-time thing for each computer.
-
Robert, is any separation supposed to be okay? Even if duplicate/triplicate lines occupy the same precise location it's still silly. I'm not splitting hairs. I think it's worse than silly. It potentially bloats file size, takes extra work when repetitively deleting, looks and feels sloppy, embarrassing when exported, etc.
In fact, I think any kind of miniscule extraneous entity in a digital drawing should be avoided. Otherwise, it's like sweeping dirt under a carpet -- if nobody notices, then it's clean??
-
I believe a Vectorscript can do it. It may require that the origin stays consistent (e.g., untouched) in all those incoming sheet layers. It's worth looking into if you need to do it regularly and often.
Roof intersection line rendering
in Wishlist - Feature and Content Requests
Posted
And click on what points for the line segment? Sometimes the situation is like this:
Again, if only we had the power of CAD...