irneb Posted June 6, 2012 Posted June 6, 2012 As I said it's just due to an old addon which made me used to those settings (same type of thing with a break @ int - called split). It used a select point with intersection. To see the difference change your PickBox (temporarily) to 3, then issue some command (say fillet), before picking anything type Int and see how the cursor looks now. Quote
nestly Posted June 6, 2012 Posted June 6, 2012 I wasn't referring to your reply specifically, I'm just saying I don't understand the default settings of PICKBOX=3 and APERTURE=10. Why do you have to be 3x closer to an object to pick it, than to snap to it? Quote
irneb Posted June 6, 2012 Posted June 6, 2012 I wasn't referring to your reply specifically, I'm just saying I don't understand the default settings of PICKBOX=3 and APERTURE=10. Why do you have to be 3x closer to an object to pick it, than to snap to it?Oh! Yes, that is strange isn't it? Probably due to things like this ... it was there since I can remember (R9 ~ 1988 ). It's probably just left and no-one thought of combining the 2 settings. It does make it "strange" especially for new users, seeing as those 2 settings are on different tabs of the Options dialog (Selection & Drafting). Quote
Blackfish Posted June 6, 2012 Author Posted June 6, 2012 5% vs 100% - neck to neck Quite interesting... Does it matter which release of AutoCAD one started? 5% - ACAD2000+, 100% - older releases... --- PS. What colour of crosshair? I have 254, because it's 'screaming' form the screen if pure white. Quote
irneb Posted June 6, 2012 Posted June 6, 2012 5% vs 100% - neck to neck Quite interesting... Does it matter which release of AutoCAD one started? 5% - ACAD2000+, 100% - older releases... --- PS. What colour of crosshair? I have 254, because it's 'screaming' form the screen if pure white. I think (at least from what I've seen), most of those starting with As for colour, I tend to not worry too much about that ... though I'm with you on the screaming front. But I've seen guys going totally opposide and making the cross-hairs blue of something like 251. IMO that's silly since you start having to squint ... That brings up another point: One guy in our office actually works on Revit much more than ACad, so he's used to a white background. That's also why he sets his crosshairs to a dark colour as well. And I prefer having the plot-style displayed on paper space (i.e. everything is black on white with line weights), nearly everyone else here hates when I do that (can't imagine why though since I can't actually read yellow on white, most of the text on the title block is yellow, should probably have that changed but hate to come close to the "standards" debate). Quote
Tyke Posted June 6, 2012 Posted June 6, 2012 I use a red crosshair, because we have one client who uses a white background and a very dark blue font and you can't see the dark blue text on a black background. But normally we would use white crosshairs on a black background. Quote
rkent Posted June 6, 2012 Posted June 6, 2012 5% vs 100% - neck to neck Quite interesting... Does it matter which release of AutoCAD one started? 5% - ACAD2000+, 100% - older releases... --- PS. What colour of crosshair? I have 254, because it's 'screaming' form the screen if pure white. I use 5% cursor size and I started on AutoCAD in 1988, V8 (r2.6). I use yellow crosshairs in model space and magenta in PS, black background in both. Quote
irneb Posted June 6, 2012 Posted June 6, 2012 I am pre 2000 AutoCAD and prefer 5%. I use 5% cursor size and I started on AutoCAD in 1988, V8 (r2.6). Well, that starts to prove me wrong Quote
BlackBox Posted June 13, 2012 Posted June 13, 2012 (edited) I also recently implemented a Command Reactor that automagically changes my CursorSize from 5% to 100% only for specific commands, without having to even use the command posted above... I'll post here if others are interested. Saw that someone zombified a similar, much older thread than this, and thought I post this here too: (vl-load-com) ;;;--------------------------------------------------------------------; [color=seagreen];;; List of commands to react to: ;;; Note - This string will be used in a wcmatch statement.[/color] [color=seagreen];;;[/color] (setq *CursorSize_Commands* "[color=red]COPY,GRIP_STRETCH,MOVE,SCALE,STRETCH[/color]") [color=seagreen];;; ;;; Specify the cursor size, which can be any number between 1 and 100:[/color] [color=seagreen];;;[/color] (setq *CursorSize_Size* [color=red]99[/color]) ;;;--------------------------------------------------------------------; ;;; Start reactor function: (defun c:CursorSizeOn () (CursorSize:StartReactor)) ;;;--------------------------------------------------------------------; ;;; Stop reactor function: (defun c:CursorSizeOff () (vlr-remove *CursorSize_CommandReactor*) (terpri) (prompt "\n** CursorSize reactor has been stopped ** ") (princ)) ;;;--------------------------------------------------------------------; ;;; Start reactor function: (defun CursorSize:StartReactor () ;; Command reactors (or *CursorSize_CommandReactor* (setq *CursorSize_CommandReactor* (vlr-command-reactor nil '((:vlr-commandCancelled . CursorSize:CommandEnded) (:vlr-commandEnded . CursorSize:CommandEnded) (:vlr-commandFailed . CursorSize:CommandEnded) (:vlr-commandWillStart . CursorSize:CommandWillStart))))) ;; <- Other reactors (prompt "\n \n >> CursorSize reactor loaded ") (princ)) ;;;--------------------------------------------------------------------; ;;; CursorSize:CommandWillStart callback function: (defun CursorSize:CommandWillStart (rea cmd / cmdName) (cond ((and (/= "" *CursorSize_Commands*) (wcmatch (setq cmdName (car cmd)) *CursorSize_Commands*)) (setq *CursorSize* (getvar 'cursorsize)) (setvar 'cursorsize *CursorSize_Size*)) ;; <- Other conditions ) ) ;;;--------------------------------------------------------------------; ;;; CursorSize:CommandEnded callback function: (defun CursorSize:CommandEnded (rea cmd / cmdName) (cond ((and (/= "" *CursorSize_Commands*) (wcmatch (setq cmdName (car cmd)) *CursorSize_Commands*)) (setvar 'cursorsize *CursorSize*) (setq *CursorSize* nil)) ;; <- Other conditions ) ) ;;;--------------------------------------------------------------------; (c:CursorSizeOn) (princ) Edited June 13, 2012 by BlackBox Quote
rkent Posted June 13, 2012 Posted June 13, 2012 Renderman, Thanks for that one, very nice. I added PLOT to the list as I often window areas from MS for printing. Quote
BlackBox Posted June 13, 2012 Posted June 13, 2012 Renderman, Thanks for that one, very nice. I added PLOT to the list as I often window areas from MS for printing. That is kind of you to say; Always happy to help! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.