Filtered Markups - Make It So They Can't Be Selected

One of the things that I do regularly is to allocate markups to plots on site layouts e.g. drainage, garden walls, etc.. These markups cross plot boundaries and using Spaces is definitely not an option.

What I'd like to be able to do is filter out the markups once they have been given a plot number AND not be able to select them again.

However, at present, even if the markup is greyed out as a result of being filtered, it can still be selected and the properties (Plot Number, etc.) can still be changed. This basically makes the filtering process pretty pointless and therefore the allocating process much more difficult that it needs to be. When you're looking at a site of 200+ units, this can add a significant amount of time to your workflow.

Find more posts tagged with

Active

Revu

Markups

Takeoffs

Status: Active

Comments

David Cutler

Interesting observation @Vince French. I haven't used filtering extensively to have this experience, yet.

Would it be an option to establish a layer for each plot and then turn those layers off as you assign them? Basically you would be using the layer as a space - without the issue of markups crossing space boundaries.

(Full Disclaimer - I'd expect that you are already using layers extensively so this may not be a viable option in your workflows) 😎

shipshape

I've also ran into this issue. My work-around is to ensure my markups are created in layers and then I flatten the layers. It protects the markups from being selected or tampered with and I can always unflatten when needed.

Vince French

Hi @David Cutler - yes I'm already using layers which can't be changed unfortunately.

Vince French

Hi @shipshape - unfortunately this sort of flattening then unflattening isn't really an option for the workflows that I'm looking at.

shipshape

Ah that's too bad. The other way I might go about protecting the markups would be locking them and filtering only unlocked markups. That would gray them out and prevent tampering but they could still be accidentally selected which is pretty annoying, especially if you have a lot of overlapping markups.

Quick Links

Popular Suggestions

Edit/Unlock markups in Studio Sessions
Please add the ability to allow some users to edit/delete other peoples comments. This can be controlled through permissions. At our organisation when reviewing drawings there is a review manager that consolidates comments before sending them back. This process occurs regardless of if we are using Bluebeam or another tool.…
Add Folders for Studio Sessions!
Add folders for studio sessions to organize the list of recent Studio sessions. Some of our clients utilize one Studio session per deliverable on large projects that have multiple reviewers. It can be quite a task to find the one studio session for a smaller project amidst the rows and rows of studio sessions per…
Bullet points & Indent text
With more people using bluebeam as a CAD/drawing program. It would be nice if bullet points/numbers points with auto text indent was a feature.
Auto Save
It would be helpful to have an autosave function for PDFs being used in Revu. Currently this does not exist and would be very beneficial.
Numbered Lists and Bulleted List
This has been requested many many times in the past by many Revu users. WHY is there STILL no numbered/bulleted list function??
Grouping Tabs for Open PDFs
Request is for the ability to group open PDFs into tabs, similar to the way that Microsoft Edge allows for web pages to be grouped together into tabs (Edge allows you to take a number of open websites and add them to a named / color-coded group tab. This allows for multiple websites to be open, but organized into group…
Feature Request: Add "Crop" Functionality to Snapshot Markups
Hi Bluebeam Team, I am writing to suggest a feature update that would significantly improve the workflow efficiency for users who rely on the Snapshot tool (G). Current Issue: Currently, if a user takes a snapshot and realizes there is excess content or "clutter" around the edges, they must delete the snapshot and re-take…

View All