Alaskan_Son

Angela, If you have a mnaually drawn dimension that already exists in the plan, Chief will use that instead of producing its own Temporary Dimensions. Those dimensions you're seeing could be dimensions that you have drawn and that are on a layer that is currently not displayed. Also, temporary dimensions are controlled in part by your currently Active Dimension Defaults. So if you have those set to Locate Centers, then your Temporary Dimensions will locate centers as well.

Thanks Lew. I have to say that this one indeed qualifies as a genuine workaround.

...and possibly never should be.

I think basement levels are always a little weird, both with regard to the Living Area label and with regard to the Plan Check tool. At any rate, you can trick Chief into giving you back your Living Area Label on Floor 0 by enclosing a little room off to the side that is completely separate from the rest of the structure. Now connect that room to the existing structure with a connecting wall. Now simply delete all those new walls. What's really happening is that you're tricking Chief into recognizing a new Living Area and therefore generating a new Living Area Label. When you draw the connecting wall, Chief considers them both part of the same structure and includes both areas in the total. Deleting the extra walls just deletes that one room and the new label stays.

Turn off Blend Colors with Materials. And like some of the other guys have already mentioned, take advantage of the Help files.

The tool is called the Material Painter

We do basically the same thing and have no problems whatsoever. I would note that I only use that method when the barge overhang is under 2 ft. though.

Did you ask your Nana? Or how bout maybe the local pawn shop?

Hey Joe, I assume you are talking about this part of the code... ...since I'm pretty positive you understand the rest quite well. If my assumption is correct, I may be able to help as it's something that took me quite some time to fully grasp and I personally couldn't even work without anymore. If it doesn't help you, maybe someone else can take advantage of the free lesson (note that this is NOT intended as a beginner lesson). It's a lot simpler than it actually seems on the surface. First off is the .map function, which is really the key to the whole operation. In plain English, the .map function essentially tells Ruby that you want to do something to every element in your array. The brackets ({}) encapsulate the thing you want to do. The .map function is unique in that it will output the results as a modified array. Anyway, moving on... Inside those brackets are some pipes (||); and inside those pipes you are essentially just giving a generic name that represents the generic array element. I believe this generic name (as I call it) is technically called a block parameter but I could be wrong about that part. In this particular case, Gerry used the letter r, but it could have been any letter. Right or wrong, I personally just look at this like I'm assigning a temporary variable name. In fact, you're not even limited to using a single letter (as you'll see in my example below), but a single letter seems to be the typical approach. After those pipes (and still inside the brackets) is where you describe what you want to do to each element in your array. I look at this like I'm just modifying a single variable except that whatever I tell Ruby to do will happen to each and every element in the array. In this case, Gerry used the Rational method using the block parameter (r) as the argument. For all intents and purposes, Rational(r) is the same thing as r.to_r and is also the same thing as r.rationalize. Just 3 different approaches. So, as an example, I want to tell Ruby to take my list of numbers, automatically square them, and return them as a list of equations in this basic format: 6² = 36 Creating the array is something I'm sure you're familiar with. There are many ways, but here's one: my_list = [1,2,3,4,5,6] I'm sure you're also perfectly familiar with how to create a variable and how to modify that variable to get the desired format. Again, there are many ways, but here's one: temp = 1 temp.to_s + "² = " + (temp*temp).to_s > 1² = 1 Let's put it all together now by taking your array (my_list) using the .map function starting the code block ({) assigning your "temporary variable name" inside pipes (|temp|) inserting the code you want to execute on each element (temp.to_s + "² = " + (temp*temp).to_s) adding a carriage return so that the new list is generated as multi-line text (+ "\n") ending the code block (}) which will essentially result in a new array with appropriately modified elements joining each element in that new array back together as a single text string (.join) and removing the extra carriage return at the end (.strip) my_list.map{|temp| temp.to_s + "² = " + (temp*temp).to_s + "\n"}.join.strip >1² = 1 2² = 4 3² = 9 4² = 16 5² = 25 6² = 36

You can also just hit Undo or Save and reopen the plan.

This is a long standing bug Doug. Not sure I remember all the nuances, but I believe it's always triggered by having Auto Rebuild Roofs toggled on and Automatically Build Roof Framing toggled off. To fix, you have to group select the offending items (using Match Properties makes this quick) and then Cut/Paste Hold Position. I would also recommend turning OFF Auto Rebuild Roofs or you'll just have to keep fixing it.

https://mygeodata.cloud/converter/dgn-to-autocad

Not hashed Rich, arrayed. .... I am so sorry

Don’t be afraid of deleting it all. Your plans will be unaffected.

Can you elaborate on this? It should only be blank if there's nothing in the plan to populate the schedule...in which case I would expect it to be blank. You have to copy/paste however you can make really quick work of this process and of editing that particular note by familiarizing yourself with the Find Object in Plan tool and the Open Row Object(s) tool.

From the documentation: Returns the result of interpreting leading characters in str as a rational. Leading whitespace and extraneous characters past the end of a valid number are ignored.

Just tested quickly and it seems to remove all trailing non-numeric characters.

You are correct. My bad. The rationalize method does that automatically (removes or ignores non-numeric characters). Never realized that before. I guess it makes sense. Most of the other numeric methods do that as well.

Quite a few ways Joe, here's what I would do though: Remove the inch notation Break into an array of whole numbers and fractions Convert those whole numbers and fractions to rationals as Eric suggested Convert those rationals to floats Add those floats together If the string could potentially have foot values as well I would probably start by splitting into an array of 2 values using the foot notation as the pattern, multiplying that value by 12 and then adding that to the results obtained from the other half of that array (using the steps mentioned above). Does that help?

The Time Log is a little tricky to work with if you're trying to pull out totals for a specific subset of entries. There are a few options that come to mind though... Delete all entries you want excluded from your calculations, get the total you need, and then hit Cancel. Copy and paste values to a spread sheet. It's not apparent on the surface, but you can select any given cell and hit Control+C (Copy) and then paste that value elsewhere. Using Contorl+C (Copy), Contorl+V (Paste), Alt+Tab (to switch between programs), and the arrow keys (to move cells), you can make pretty quick work of copy and pasting values. Export the whole Time Log and Import into a Spreadsheet to work with it there. I posted a free starter kit that you can use to make quicker work of this here...

I think the closest you can get is with custom text macros set to report different text depending on either the layer_set or the settings thereof. Aside from that though, my personal opinion is that text boxes are the way to go. I find that copying and pasting text boxes with the appropriate macros results in a lot more flexibility and is a lot quicker and easier to customize and control on a room by room and situation by situation basis.

I wouldn't recommend this approach at all. Text macros can be used for such a broad range of purposes and in such a broad range of ways that you could get totally lost without knowing what the specific macro(s) were for and exactly how they were intended to be used. If you jump in too quickly with both feet and without testing the waters, I think you're likely to get overwhelmed, jump back out, and never try to swim again. The best approach in my opinion is to start with the basics and then take it from there. Shoot me over an email if you're interested in discussing further.

Nice! I remember the first video card I used to run Chief. It was a GeForce GT 430 and at approx. 5.7" x 2.7" may have been even a little smaller than that one. I remember thinking it was freaking awesome too.... ....I still kinda do actually.

Yep. Was just typing that up too. I would recommend resetting Dialog Sizes and see if that does the trick.

Just upgraded Firefox to 84.0.1 and I get the same behavior as you now. I have to change the extension manually.