lbuttery

You only need to delete them when layout is ready or place on a layer(in layout) to turn off when not needed then if you use the "save as method" as advocated by Scott they will be there ready for the next project Lew

Rod: the annoset "rabbit hole" is much deeper than anticipated I thought I would take some time to study the annoset dbx and the default's being chosen via that dbx I was surprised that there it is like a maze - perhaps never-ending open one dbx and there are more nested within and then within again not sure how anyone can "master" all these settings and how they inter-relate certainly way more than I would ever need to use for the remodeling projects that we used to do and even the few new homes we did like hunting mice with an elephant gun Lew

working views on a special working views layer in the Layout. That way I can use Layer Sets in the Layout to control multiple settings with one click from the drop down Rod: neat, more study required thanks, and I understand about the settings there are a multitude of them and I will probably stay with OOB for now I've never needed the multi-disciplines that some of the power users need Lew

any number of these working Layout Views that can be preset in your template plan. Each can be set to fit a particular tasks requirement Rod: interesting, I will have to scope this out can you post a sample of these ??? since we mainly did remodels we never felt the need to have a template plan or get that organized from day one we just cloned the last plan and went from there with making it work for the next project a crude SAM method Lew

Anno sets are now associated with individual Layout Views. Layer Sets were already associated with Layout Views Rod: I just learned that a view will remember the anno-set/layerset info so even if the layerset and annoset dropdowns are used to select the framing layerset and the 1/4" framing annoset if a saved view is accessed that had been setup for plot plan layerset and annoset it would use the plot plan info the plan would continue to use the framing info CA stated that this makes VIEW king where some where advocating for layesets to be king or annosets to be king I like Joe Carricks suggestion that layersets and annosets are JACKS and have equal weight in relation to each other Lew

IMO it is a losing game to try and remove something that others are using to advantage Rod: I agree except in this case the "active defaults" dbx does the same thing AND offers access to the other defaults while the "current cad layer" dbx is limited to the one setting only so if they are using the "active defaults" dbx then there is no need to use "current cad layer" anymore if they are not using "active defaults" dbx then the question is - why not ??? Lew

Rod: I know much about layers and layersets and a decent amount about layouts concerning layout we had to do "permit sets" - never complete CD's just never had a need to get into anno-sets since I retired about the time they were introduced I'm studying them now with "newbie" eyes Lew

Anybody have a solution? Yes, use the "active defaults" dbx only the "current CAD layer" dbx is redundant - and no longer needed Lew

You do realize that if CA updates or changes the '3 dozen dbx's' it can make your macros useless? Bill: useless ??? - no needing tweaks ??? maybe - depends on the change(s) even so, they are easily editable via notepad as I stated before there are a zillion VBA macros for Excel, Word, Powerpoint etc there are a zillion Ruby macros for Sketchup there are a zillion macros for other software some how they manage to stay current just bringing a plan from ver 5 into ver 6 can "break" things never assume a migration is 100% successful thus, I plan to also present (when time allows) how to use recordable macros for "regression testing" to help verify if the newest release has caused changes in a plan this is especially useful for new home builders with production lines if they create a set of macros to build a production house when the new release comes they run those macros and they should get the same house if the new versions has moved or eliminated settings then the macros will issue a warning/crash then once the macros can recreate the same house the user can add any new features and that becomes the baseline for the next upgrade Lew

Perry: I'm not complaining about these annoset topics trying to understand how the pieces and parts work and in doing so I found a few inconsistencies etc that CA may want to consider addressing I will probably never use annosets etc but my friend/partner is interested and I'm doing the research for him once I understand it, I'll show him the ropes also, once I understand annosets and the 3 dozen dbx's that are involved in the process I'm planning to post a recorded macro example for Glenn's challenge that he issued last week last week I was prepping for an open house for my new museum now I have a little time to kill I'm sorry that questions about Chief irritate you Lew

I CREATE MY OWN TOOLBARS Perry: OK, so do I what's that have to do with which icon to use ??? anyways, you prefer "current cad layer" - I get that it's up to CA to decide if it is redundant Lew

Perry: the "active defaults" dbx also has a toolbar icon Lew

Perry: got it Lew

CA does not allow you to attach DWG Keith: most file types need to be zipped first Lew

David: I agree that we can create whatever we need just curious why Chief's OOB would be different for arrows ??? Lew

Studying annosets and wondering why the "Saved Arrow Defaults" are different from Rich Text, Text, Callouts, Markers ??? see attached dbx's (only Callouts - since the others are the same) these are all Chief's OOB just curious why Arrows are "missing" most of them and why 1/20" scale and NKBA were added ??? I'm suspect there is a drafting difference just not sure what it is trying to learn Lew

achieve an outcome via different methods and paths Jon: agreed this would encompass having the same feature/tool available via menu or icon or hotkey etc but having two dbx's by different names doing the same thing ? especially when the one dbx can only do task A while the other can do a multitude of tasks I don't understand where the benefit is in having the "current cad layer" dbx anymore it's a leftover from versions prior to the "active defaults" dbx being introduced now it just adds confusion Lew

his method is quicker Scott: how is it quicker ??? it does the same thing .... Lew

I use current cad layer for framing plan a lot Perry: ok, so why can't you use the "active defaults" dbx for that ??? Lew

I just created a new thread in the suggestions forum No "delete" ??? yet this posting here has one ??? Lew

I'm also wondering why Chief has a menu choice under CAD for "current CAD layer" and a toolbar icon for "current CAD layer" when the "current cad layer" can be found on the "active defaults" dbx since the "active defaults" dbx has all the other defaults also why have a dbx that is solely for the "current cad layer" ??? Is this a leftover feature from versions prior to the introduction of the "active defaults" feature ??? Lew

ok, I was just looking at the "active defaults" dbx I would think to be consistent there would be an edit icon (pencil) on dbx like there is for dims, rich text, text, callouts, markers, arrows ??? Lew

nope, just not available I'll send it to CA Lew

I'm surprised that from the Annoset dbx or the Layerset display options dbx that there is no way to get to the CAD defaults setup dbx Am I missing something yes, I can get to CAD default setup by clicking the Defaults icon on the toolbar or the CAD defaults icon on the toolbar I would think to be consistent there would be an edit icon (pencil) on the annoset dbx like there is for dims, rich text, text, callouts, markers, arrows ??? If I'm not missing anything - I'll post this in suggestions Lew

Dennis, I understand what you are saying seems to me that there is plenty of room at the table for everyone we are all competitors to each other with the internet I could be doing projects on your street/town Lew