[Doug McLean]

have yet to update, so I haven’t seen this yet.
Is it just a case of the highlighter function being reset?

[Charles Yancoskie]

No, highlight button is still on for Fill Color such as Area Measurement, Polygon, Rectangle, Cloud, etc. Of course, selecting “No Fill” for Fill Color does not block any content except at the lines, but lines are not the problem, the Fill Color is the problem. This does not affect the Highlighter Tool, only shapes with Fill Color. Btw, do your Count Measurements show up in the Recents Tool Chest?

[David Cutler]

I haven’t made the update to 21.7 yet @revu-user – I tend to wait a couple of days to install the updates so that early adopters, like yourself, can find these issues… 🙂

I too have wondered why the count tools don’t show in the recent tools. Might have to ask the Developers at Unbound at the end of the month about that…

As a work around you could right click on a count tool that you are already using and select “resume count”. While this isn’t always convenient if the pervious markup is on a different page in your PDF it does get it done…

[Charles Yancoskie]

Yes, I too normally wait at least 2 weeks or so before updating, but this time the reminders just got annoying so took the bait. For the count tools, I just copy them as well as other selected tools into a holding tool chest and then just delete once a project is complete and then refill for the next project, but quite often use the Recents tool chest for certain tools because I can modify custom column values for a particular tool placement in the Recents tool chest and keep the default custom column settings for that tool intact in the holding tool chest.

For the shape tool fill block-out issue workaround, I duplicate shape tools with fill in the holding tool chest, eliminate the fill, and then set the line width to 0.25, although that is still too thick since the lines also block content now, and then, once the markups are placed, just use the paint brush from the unmodified tool to re-establish the fill and line settings, but this is an annoying time waste. Submitted tickets for both these issues, but only received the robot “We’re working on it” replies so far; imagine either others submitted tickets as well or they’re just too busy getting ready for the annual Bluebeam shindig.

[Troy DeGroot]

Good thinking on the workarounds. I’m guessing that anytime they come out with a single decimal update (21.x), they get a bunch of bugs and support tickets. Once they get to the double decimal (21.x.x), they are fixing the bugs within the update. If that makes sense. And I doubt any of the support team are lucky enough to attend the conference.

[Charles Yancoskie]

Email Received from Bluebeam yesterday:

“Thank you for reaching out. This issue was brought to our attention after the launch of Revu 21.7, and we are at work trying to repair this portion of the update. At the moment, there are 2 workarounds; you can edit the fill opacity to around 80%, save your tool/defaults, and then it should allow you to see through for the filled Measurement tools, or you can rollback to the previous patch to 21.6.1.”

[David Cutler]

I’ve done something similar in the past @revu-user using a “Working Set” tool chest for project specific tools.

One idea that might speed up the extra step of using the format painter would be to filter your markups list for a certain markup – say respread topsoil as one of my tools – and then select all of those markups and make the line thickness/fill color changes once for all of the selected markups. The format painter works well if you have a couple of markups to match, but there are more efficient ways if you are dealing with dozens or hundreds of markups. 🙂

Hopefully Bluebeam issues a 21.7.X update shortly and addresses you other issues….

[Charles Yancoskie]

Email received from Bluebeam yesterday (one would expect the developers to write code required to clear the count quantity after use of the Count Tool and then add the Count Tool to the Recents, but maybe this is too complex?):

“I will be more than happy to help you, and thank you for all your patience, as we have been experiencing a large backlog with longer-than-normal wait times.

This is, in fact, by design within Revu. It is best explained by our engineering team:

“Both Count and Sequence behave this way. They are not meant to be added to Recent Tools because they are a specialized tool that counts other things. Before one of those Tools is recognized as ‘used’ you have placed X number of them on the document, maybe even paused and resumed, and the tool has a total.

The base markup used to Create a Count or Sequence is not what is added to Recent Tools, you add the result….for example when you place a Text Markup, what gets added to Recent Tools is not the base text markup, it’s the markup that resulted from the placement (it has all the text you entered). What would get added to Recent Tools would be a Count or Sequence that has a total already. So it is best not to add those to Recent Tools.”

I hope this clears things up and please let us know if you hae any other issues”

[Troy DeGroot]

Thanks for sharing the response @revu-user

This does make sense, what they’re saying is the tool in the recent toolbox is no longer current. I’ve never run into this issue simply because I’ve never tried it, so this was a great learning opertunity for me as well. Out of curiousity, where you able to do it before the lastest update?

[Charles Yancoskie]

Cannot remember exactly, but somehow in the fog of memory do seem to recollect count measurements showing up in Recents.

[David Cutler]

@revu-user if you haven’t already found it Revu 21.6.1 is available for download at:

https://support.bluebeam.com/download-archive.html

support.bluebeam.com

Download Older Software | Bluebeam Technical Support

Download Older Software | Bluebeam Technical Support

[Charles Yancoskie]

Thank you, they did send a link in their response to revert to previous update, just did not include it in the post.