Good idea Kyle. We'll discuss and see if we can control page visibility for those you share with along with the takeoff data 🙂 We have lots of discussions happening about this internally right now.

Hi Eric. Yes, we're working on this as part of the update. It will either be called "Layers" or "Spaces" (we haven't finalized the name yet, but will have the same general concept). There are a cou...

Hi Aaron. We will definitely be adding this. Thanks for all the input you guys are sending in 🙂 We love all the community interaction and comments helping us make zzTakeoff better.

I have not been able to reproduce this issue yet, but if anyone is able to please let us know.

Hi Brandon. Yes, we will be adding this for sure. We'll push to get it in as quickly as we can.

We don't have an exact date, but we're working on it as fast as we can. I can say it's near the top of our priority list along with wall heights, slopes, layer visibility per user, grouping projec...

Awesome. We'll do it. Should be easy for us to add, so you can expect it in our next release.

What if we add 2 sub-buttons for "Show All" and "Hide All" (in the right click menu and "..." menu on the page). One with an icon for "takeoff items" and another for "annotation items". Would this ...

Sounds good. Thanks for the input and real world scenario. Giving real world scenarios helps us go through lots of "what if" scenarios on our end. We'll discuss internally how to make it happen.

Hi Ben. Good input. Do you think you would want the expanded/collapsed state of folders & pages to stay in sync between tabs, too (if you expand a folder in one tab, it also expands in the other in...

Thanks for the input. Regarding copying the takeoff Qty from the sidebar, you can just click right on the number, and it will flash orange when it copies to the clipboard.

Hi Ben. Thanks for the input. Yes, we're planning to add an additional "Custom Scale" option, and you can enter custom scales and page sizes. You could enter a custom value for the 1" and custom...

Good idea. We'll add to the list.

Thanks for all the input. Good info and insights. @Sophia Regarding your comment about reusable components above, I agree. There's so much inefficiency and data duplication, and the whole industr...

Another thought we had was to call these "layers" instead of "spaces", which would work well from the graphical side (most users understand how layers in graphics apps work), and we could show/hide...

Thanks for sharing Jes. I love these real world examples for us to discuss.

I like annotations over markup, but the challenge then becomes: we need a word that includes area, linear, note, arrow, clouds, etc. any time of thing that can be drawn on the page. Currently we ...

Hi Sofia, interesting that you are calling it "fork" 🙂 We have discussed internally a concept for "Spaces" or "Shared Spaces", and we were tossing around the idea of calling it a "Branch" or "Fork...

Thanks for all the input. Interesting concept on the magnifier to zoom the whole screen temporarily using "M" like a "zoom shift" for the whole image view area. Honestly, from a technical standpoin...

Thanks for the input. We'll add this to the list 🙂

We could easily add this to the workspace menu. The key consideration is UI real-estate. We're trying to put most commonly used features extremely visible, and less commonly used features a little ...

Sounds good Jes. We'll get some customizability in the works. I do like the idea of allowing a button that shows a small dropdown with more tools/commands, also. As a side note, we are also cons...

When using AI to help us with coding, it is wrong a lot. The good news is that even though it's wrong, we can sift through it's suggestions (like a big pile of scrap metal you can use to build some...

If anyone has ideas where we should put this in the UI, feel free to shoot them over. We're trying our best to keep the UI as simple as possible, yet have all the features needed.

Thanks for the info Eric. We have not been able to reproduce the issue on our end, so hopefully this fix corrects it permanently. Just let us know if the issue re-surfaces.