Alaskan_Son

Members
  • Posts

    12207
  • Joined

Everything posted by Alaskan_Son

  1. There are a couple other options in addition to what Robert suggested... Consider not turning the lines off completely but rather reducing them to a smaller line weight and lighter color. I personally do this by sending to Layout using Pattern Line Defaults and then setting the Pattern lines to a line weight of zero and a gray color. The pattern lines don't jumble the view that way but they still communicate some information about what you're looking at. You can turn ALL the patterns off for a specific view by using a specific Layer Set for that view and then toggling off the "Pattern, 3D Views" layer for just that layer set. Dermot mentioned this, but I spelled it out in a little more detail to underline the importance of using a different layer set. Also, don't confuse this method with using with the Toggle Patterns tool which will Toggle Patterns for ALL views.
  2. Yup. Definitely some weird behavior. To fix issues like this you can always select the object and Convert Selected To Symbol to get a new symbol and a new 2D Block.
  3. There are ways to even further speed the process up too. Most notably you can increase the Smoothing Angle for your symbols to greatly speed up surface deletion for some cases.
  4. Ya, I know how to use it and I currently have a base macro set up that I can modify and simply copy as necessary for various formatting. I was just thinking aloud and wondering whether we could access the settings for the class itself or not. Not a big deal at all. I might search the program files to see if it’s hidden in there somewhere. It’s just a personal curiosity really and not too important.
  5. I’m curious if there’s a way to access and modify the initial settings in the NumberFormatter class.
  6. Alan, I think your quickest solution might be to group select your doors, add a casing to provide the offset, generate the Room Molding Polyline for the rail, and then group select the doors and change the casing back.
  7. Nope. Don't think you;re missing anything. Make sure to send this in as a suggestion.
  8. Not sure if you’re suggesting the tools be combined, but if you are, hold your horses. The tools don’t behave exactly the same, particularly the single click behavior. It’s handy to have the 2 different functionalities available.
  9. Yes. There are a good handful of scenarios where we might not want a different block. Electrical symbols are one of the most obvious and there are sink blocks along with their associated Countertop Holes but there are plenty others as well.
  10. I believe it's indicative of the fact the auto generate status is in limbo so to speak. If you try to rotate that block in a section/elevation view, you will get a pop-up message asking "Do you want to regenerate....". Whether that box becomes checked or unchecked depends on your answer to that question. In other words, the setting is somewhat undecided till you get the pop-up dialog. NOTE: While that setting is "in limbo" (my term not Chief's), the block will remain unchanged with any plan view changes. As far as I know, it's only rotation around the x and/or y axis that trigger the pop-up.
  11. it does. Look closer at that dialog.
  12. It's not a full list if what can be done, an explanation of exactly how the conversions work, or an explanation of the different types of Measurements (Linear vs. Area vs. Volume), but here's a list of a few of the basic methods you can use to convert measurements to floats based on other units: .to_inch .to_in .to_foot .to_ft .to_yard .to_yd .to_mm .to_cm .to_dm .to_m .to_sq_inch .to_sq_in .to_sq_foot .to_sq_ft .to_sq_yard .to_sq_yd .to_sq_mm .to_sq_cm .to_sq_dm .to_sq_m .to_cu_inch .to_cu_in .to_cu_foot .to_cu_ft .to_cu_yard .to_cu_yd .to_cu_mm .to_cu_cm .to_cu_dm .to_cu_m And here's a list of what you can use to convert a float to a measurement... .inch .in .foot .ft .yard .yd .mm .cm .dm .m .sq_inch .sq_in .sq_foot .sq_ft .sq_yard .sq_yd .sq_mm .sq_cm .sq_dm .sq_m .cu_inch .cu_in .cu_foot .cu_ft .cu_yard .cu_yd .cu_mm .cu_cm .cu_dm .cu_m ...again, learning exactly how the conversion works is a bit more complicated but if you use .to_s you will get the newly created Measurement and its units. There are other similar methods as well such as .convert_to (as was mentioned above by Ben) as well as Measurement.new(value, optional unit). In addition Chief also has a built in NumberFormatter functionality that you can use to format various measurements. It basically works exactly like the Dimension formatting options we have. I don't have the time or inclination to go into all of it in this post, but it's pretty cool.
  13. It can actually be even shorter. I believe area.to_sq_m.round(2) does the same thing right?
  14. Texture and Pattern are 2 entirely different things. You’ll need to find or create a seamless texture.
  15. You can't. You can download the MiTek® Viewer though.... https://www.mitek-us.com/software/Viewer/
  16. All you have to do is open the Note Schedule in your previously attached plan and add the 2D Symbol column.
  17. Alan, Is there some reason you're opposed to using the 2D Symbol column?
  18. I could be misunderstanding, but I don't believe the soffits in the picture are sloping any differently than the roof. It just looks like a depth perception illusion.
  19. This isn't true. Here are 2 manually placed callouts as they are displayed in Plan... Same view sent to layout and rotated... You need to set the text style being used to not Rotate With Plan. Same goes for other text like that Room label. As shown above it is set to Rotate With Plan. Here's what it looks like in layout if I uncheck that setting...
  20. Alan, The schedule_number is already a string to start with. As long as you don't try modifying it, it will work just fine. It's modification of any kind that breaks it. As I stated above... "Macros using schedule_number don’t work consistently in schedules..." I should have said macros attempting to modify schedule_number don't work. It has something to do with the way the schedule_number is generated by it's own schedule and the order in which those macro executions take place. At any rate, you have to either use the 2D Symbol column or another custom solution. I personally usually just use the 2D Symbol.
  21. It’s exactly what it sounds like… If the box is checked, then the layout box will remain linked to that saved plan view. Any changes to the saved plan view and the layout box changes to suit. If it’s not checked, then the layout box will NOT be linked to the saved plan view. It will use the same layer set, reference display, floor, etc. as the current saved plan view, but once sent to layout, the plan view being used will be set to “None”.
  22. I stepped into the office real quick Alan. Your problem is that you’re not using the 2D symbol. Macros using schedule_number don’t work consistently in schedules. You either have to use the callout label or you have to use a different macro to generate the numbers inside your schedule.
  23. Not at my computer to open your plan, but I can see from the code you posted that you’re just opening the door to a bunch of problems with a handful of unnecessary code. Specifically though, your defining a global variable for no reason. That’s what’s likely causing the same number in the schedule. With a few very unique exceptions and for all intents and purposes, a global variable can only ever have one value in any given view.