I’m a little confused about why we are doing this in this manner. Why don’t we just use an area once and copy and paste the rest, using the sections count as the count? Or if need be, allow the use...

I am of the opinion that material/assemblies should all show as Depth x Width x Length, where depth is the least variable dimension, width is somewhat variable, and length is the most variable. Fur...

I think this is part of what made the PlanSwift advanced properties view so good. It could show you everything and how it worked with spreadsheet-like ease.

PowerToys. Done.

I think a lot of this is solved by separating blueprint page operations and takeoff operations by having a separate Blueprint Tab or Plans Tab, as has been previously discussed. Don’t get me wrong;...

This is similar to what I have been saying: the takeoffs should be independent of the plan pages. See Takeoffs On Overlays Instead of Pages. Make the “root” plan page a blank page (instead of the f...

Oh Todd, how I wish it was that easy! xD

Finixney’s 3rd point would be great with the area tool, as has been mentioned before.

Heber, What I meant by convenience is that it is convenient to describe an assembly that is “mostly like this, less a little of that, and some of this where there is no longer that.” And this is co...

Heber, Happy to hear about the Plans page. But working from supply side, I have precious little interest in page totals (as they are) or thumbnail views. Not sure what is meant by “views for the ta...

Kyle, I get what you are saying, but both examples you are siting give only one side of the story. I am suggesting both are combined. But perhaps “takeoff summary” is a misnomer; “takeoff” would pr...

And this is why I keep plugging the idea of a basic model…. Neither the left panel nor the right panel will be capable of accurately communicating “what is happening when” between users without bas...

Heber, If you implement the pitch factor as a scalar for the linear total (ignoring direction) then there shouldn’t be an issue with the takeoff running in different directions. Honestly, I cannot ...

Would be awesome if pitch or wall height or whatever could be implemented at the section level instead of the parent takeoff so that we don’t have to have 10 takeoff items for the same assembly wit...

For the most part PlanSwift’s implementation was pretty good…particularly because of the customization. That said, I think zzTakeoff needs to be strong in a few key areas: 1. Customization 2. Disti...

Being able to export to an excel template may go a long way in zzTakeoff playing well with others.

Right now we use such an intermediate excel file to get from PlanSwift to a fixed width text file for our POS. Formatting of takeoff data before export to excel would be highly desirable.

This was part of the idea behind Takeoffs On Overlays Instead of Pages. But I do like the “viewport” terminology.

This level of detail would be great for the Blueprint Tab idea!

Kyle/Heber, I agree to a point. The future is in realtime collaboration…but it is not in collaborative reporting. Everything in the construction industry is moving towards science: materials scienc...

If using Takeoffs On Overlays Instead of Pages, the behavior of linking relevant drawings/tables/pages is naturally part of preparing for takeoff. Let’s say you wanted a separate takeoff for framin...

Jes/Mark, This navigational concern was precisely the point of having general blueprint study, manipulation, and navigation relegated to a Blueprint Tab. This way, you never leave what you are work...

Sam, I just realized that the toggle for hover hints was never implemented. So if you were continually working (moving) over a large area takeoff, the hover hint will still pop up once the delay ti...