Best Of

This is the intent of the filtering though, to allow you to focus on the markups being filtered for. I understand your idea though, you would like to option to retain the color when you are specifically focusing on the review comments. Maybe you can leverage the markup list instead. For example make a new column (or use the checkmark column) and tag the review comments:

Then you sort (not filter) for the yes (or checked) and when you click on that item it jumps you to that comments but all other markups stay in full color on that page. In the case above I set a custom column to a choice option. Then assign the review comments with a yes. And when done reviewing you can set to reviewed. The sorting will move that item down. So the top part of the list just has your outstanding items. Not filtering, just sorting. You just need to pre-tag the items to be reviewed with yes, items without a entry are sorted to the bottom. Your other choices are sorted inbetween. Unless you have Z code, then it'll be first…

That's a pretty specific nuance. At this point, exactly what you're asking for isn't possible. HOWEVER, a portion of what you ask for is. You can change the default behaviour of the highlighter tool. So if you want to hightlight text with the 'select text tool' you can have it highlight with your custom requirement. But it's only one custom at a time as you have to change the default of the highlighter tool itself each time if you want different outcomes. You maybe already know this:

Make at least one highlighter mark, then change all the items you want to change and set as default. Now when you select text and 'highlight selected text' the attributes you just updated will be applied.

Otherwise I find the base behaviour of the highlighter tool adequate. When text is detected the highlighter locks the highlight to the text (you'll notice you can't copy those markups and i find this usefule when i review codes and standards then i can use th emarkup list to find the text that i highlight). Or you can use ctrl to unlock the highlighter to make it freeform over text (or you can turn the text highlight feature off completely in settings).

I generally don't like having a markup locked to text when working with drawings as I can't select all markups and copy them if one markup is locked to text. So instead I use a polygon tool that is set to have highlight properties. This way i can always copy paste my markups if need be.

I do this with split screen. I pop out the second view and make it a smaller window. by defualt in floats above your base instance on Bluebeam (i drag it on and off screen as required). And i can also keep Thumbnails open. This way I have my main drawing, a zoomed portion and a thumbnail that shows me where I zoomed into. For drawing reviews, I would use the floating window to zoom in on project or construction notes, or smaller drawing details. If you have mastered the use of the scroll wheel on your mouse then this works quickly (scroll when 'fit to page' is enabled, ctrl+scroll when 'scrolling pages' is enabled). There are other ways to zoom in and out but they are slower.

I understand the request here, and I can get behind the arrows dedicated to pages (since the up & down go forward & backward for pages).

However, the previous and next view hotkeys can be extremely helpful in meetings or redlining and I would hate to get rid of that having a hotkey function.

For anyone interested, we found a way to accomplish this using a JavaScript in the target text fields that allows copying/pasting of pages while maintaining the link to the source field. I believe this is called a dynamic search, so this code can find fields containing partial text strings.

1. Add the target (or dependent) text form field
2. Go to the Calculate section of the settings for that form, then select "Custom calculation field"
3. Click "Edit", then add the code below
4. Edit the "Target Field Name" and "Source Field Name" variables to match your field names.

// Array to hold matching fields
var matchingFields = [];

// Loop through all fields in the document
for (var i = 0; i < this.numFields; i++) {
var fieldName = this.getNthFieldName(i);
if (fieldName.includes("Target Field Name")) { // Match partial name
matchingFields.push(fieldName);
}
}

// Set values for matching fields
for (var j = 0; j < matchingFields.length; j++) {
this.getField(matchingFields[j]).value = this.getField("Source Field Name").value;
}