Takeoff Enhancements

Thanks for the feedback Rick. 🙂 These are some good enhancements for us to add. We will get working on them.

As Rick had mentioned: "Be able to change line width and also line style (meaning dash-dot, dot-dot, dash-dash)"

Additionally, adding the option to use text as the path outline would be fantastic.

For example:

- Use text like "HOT" or "COLD" along the path.

- Include directional indicators like ">" or "<" to show flow direction.

This would allow for more detailed and customized annotations directly on the takeoff, improving clarity for plans like plumbing or HVAC..

Recently Implemented:

4. Quantity List & Export:

• Available in Reports tab
• Right-click grid functionality to export to Excel
• Both CSV and Excel export options available

8. Adjustable Sidebars:

• This was implemented in a previous update

9. Scale Warning:

• Now shows "Page Not Scaled" warning
• Alert message: "You must scale the page before doing takeoff measurements"

10. Count Symbol Enhancements:

• You can now enlarge count symbols
• Multiple symbol styles available (circle, square, diamond, triangle, star)
• Size control in either Pixels or Scaled mode

6. Hide Measurements:

• Show/Hide functionality available through:
• Pages panel
• Takeoff Totals panel
• Bulk "Show All"/"Hide All" options in page menu

Still Pending:

1. Line width and style customization (dash-dot, etc.)
2. Different patterns for area takeoff
3. Trace library saving and editing
4. Zoom to area button
5. Addendum sheet overlay feature
6. Page-specific measurement display

The development team continues to release updates frequently. Each update addresses specific user requests to improve functionality and user experience.

Just came to also vote for linear widths based on drawing scale. Also, would like to have, at minimum, square/rectangle scales for point counts based on dimensions/scale.

Also would like to be able to see the perimeter LF in the reports area for a point count if it's scaled.

In example below i would expect to see "F10.0" show 100 sf * 17 ea (under "Area" column) and 40 lf * 17 ea(under "Linear/Perimeter" column) and 4 ea * 17 ea (under Segment Count) because I've entered 10' or 120" as width (vert) and the same for length (horiz).

Thanks for the input.

@Chasstan:

Here's a quick question on point count sizes: do you think you would want a width / height separately for the size of a point count (rectangle vs square)? Currently we just have a "size" for point counts, but we could break that out to a separate width/height. Might make sense if we start calculating volumes, areas, perimeters from point counts. It might get a little strange with the other shapes though, such as star or diamond, etc.

Hey @Heber personally I'd prefer a vert/horiz input for square or rectangle. If there's weird shapes like triangle and octagons I would still give length/width. Height would certainly be key in the future for estimating excavation/concrete/forming costs. Wouldn't hurt at this stage for QTO data. Rectangle vs square doesn't mean much - as in typing 6' x 6' and 6' x 9' would be the same to me. A diamond, triangle, etc I would usually just use as a point count for items that didn't really have any real data behind them except count. If a volume count would be in order vs just a count item that makes sense enough to me, just as well as a point count with a drop type would make sense as well if I were more MEP focused.