TheSwamp
CAD Forums => CAD General => Topic started by: Mark on December 18, 2006, 11:22:13 AM
-
Command line for the most part, a few toolbars and pull-downs.
-
I like the most amount of drawing realestate, so all I have at most is two rows of toolbars across the top. No toolpallets. I type most of my commands in, or pick from my special middle mouse button menu, or from the pull downs.
-
Command line for most everything. Which includes 2 key shortcuts I program for everything that is not a fast input
-
Command line for the most part, a few toolbars and pull-downs.
Same here. 1 custom tool bar & 1 custom pull down. I really heavily on the right click menu, properties palette, pgp file and lisp.
-
I use dynamic input practically all of the time.
-
Dynamic input and the Toolpalettes (of course I use ADT more which has a lot of custom walls/doors/windows which are only convenient on the palettes).
-
command line FTW, + my own custom *.pgp file for even quicker commands. also right-click mouse button is disabled as Enter. fa shizzle.
also, Tool Palettes FTW. i use the crap outta my Tool Palettes when drawing my HVAC plans.
-
Command line for the majority of it. I also have a few toolbars where I have macros and lisp routine access.
-
I use the command line the most, I have a Gateway programmable keyboard , an X-Keys key pad and I use AutoHotKey. :-)
Dan
-
Command line and accelarator keys
-
command line here mostly.
One toolbar across the top.
Never used properties palette, or tool palettes much till I got dual monitors. Now I use them more and more....but still a command line junkie. Most stuff one or two key aliases.
-
I use the command line almost exclusively, although I do have a few toolbars ... ok so I have ALOT of toolbars ... but most of them are customized for executing multiple commands in succession ... for example I have one that renames a specific dimension style, creates a new dimension style, purges all dimension overrides, zooms to extents, purges all unused layers, removes non graphical blocks, cleans all null text, then finally wblocks the drawing to itself to remove any stragling crap I missed. It takes all of 2 seconds to do .. of course I could simply create a lisp or VBA to do all of those things .. but hey I am lazy before I am a programmer.
-
Autocad please don't mess with the command line, I know it's looked the same for ever and it works but that doesn't mean you have to mess with it.
-
Command line for the most part, a few toolbars and pull-downs . . .
How are you managing that in Civil 3D? I had to leave many of my command line tools behind when I jumped to Civil 3D . . . I only use a select few anymore and only when I am doing strictly AutoCAD functions. I have to hold my nose and use the pulldowns and toolbars more than I care to, but I am growing quite fond of the right click and double click context menus. I guess most of the work now happens in a tool palette if that is where you classify Toolspace.
-
Currently I use the command line the most, but with each new tool I hack together, I'm finding I use the toolbars, pull-downs and increasingly tool-palettes more and more.
-
I use all the following equally:
command line, pull-downs, toolbars, tool palettes & object properties.
-
Command line for the most part, a few toolbars and pull-downs . . .
How are you managing that in Civil 3D? I had to leave many of my command line tools behind when I jumped to Civil 3D . . . I only use a select few anymore and only when I am doing strictly AutoCAD functions. I have to hold my nose and use the pulldowns and toolbars more than I care to, but I am growing quite fond of the right click and double click context menus. I guess most of the work now happens in a tool palette if that is where you classify Toolspace.
I used to use quite a few toolbars, but I've been using a lot more pull-downs since the switch to C3D. I still use a lot of command-line stuff, including accelerator keys and temporary keyboard overrides. I actually LIKED some of the DI stuff (not all of it, but some of it), and was using it a lot in Land Desktop, but it causes havok in C3D, so now DI stays off at all times. C3D even has problems with running OSNAPS, so those are usually disabled now, too.
And actually, in C3D, an awful lot of what I do involves going to Prospector... So I guess it's now become a mix of command-line, Prospector window, and pull-downs for almost everything...
We still use Tool Palettes for a few things. I had really started getting used to the incredibly-convenient Hatch Tools, and am sorely disappointed that they don't work (at least in any usable way) in C3D... Autodesk giveth, and Autodesk taketh away...
-
I've gone to Dynamic input, but being that 2007 improved the ability to dock and collapse palettes, including the command line, I use DI more than CLI, thought they are essentially the same. If I need to see something from the CL, I just move the mouse over the CLI and out flys a very large CL, similar to hitting F-2. IOW, F-2 is a thing of the past. Of course, a picture is worth...
(http://www.theswamp.org/screens/daron/1000words.png)
I like real estate too. :-D
-
I've gone to Dynamic input, but being that 2007 improved the ability to dock and collapse palettes, including the command line, I use DI more than CLI, thought they are essentially the same. If I need to see something from the CL, I just move the mouse over the CLI and out flys a very large CL, similar to hitting F-2. IOW, F-2 is a thing of the past. Of course, a picture is worth...
The biggest issue I have with DI is that it causes a bunch of little bugs in various commands. For example, the ARC command will not always work if you have DI on. There are various other issues. Some of them can be gotten around by turning off only the Dimension Input part of DI. But some bugs also occur when DI is enabled and you have a floating or hidden command window, even if Dimension Input is turned off (the command will work OK if the command window is docked). These commands will usually work OK if you turn DI completely off, though, so I used to leave DI on unless something funky happened when I tried to run a command. Then, if the command wouldn't work right, I'd turn off DI and try the command again - a lot of times, it would work.
But that's all in the past. Civil-3D uses the same basic tooltip-like functionality as DI, and if DI is on, you can't see your Civil-3D tooltips. The C3D tooltips are FAR more useful, so DI is one of those Autocad features that are dead to C3D users.