Best Of

@Jeret Buerger - Buehler, Thanks for the thoughtful feedback. It’s clear we’re not meeting expectations yet, and that context helps. We’ve been focused on supporting Studio Sessions and other ways to get into files, whether from Projects or local storage, but that’s delayed markup improvements. A full offline experience is coming later this year, followed by tool sets and measurements. I’d love to know if anything else is holding you back. I'll send you a DM with more details.

I'd like to add to this recommendation if you'd allow it… I wish we could assign a certain number of digits with automatically filled in trailing or leading zeros. Right now, if I want to maintain 4 digits to name wire runs on a job, I start with a sequence that has two leading zeros, then when I get to A009 I have to switch to a sequence that only has one leading zero. Even that gets to not working relatively quickly on larger jobs as A099 would be the limit for the one leading zero. Having to make multiple sequences to maintain a uniform naming convention is pretty annoying and would be much better if the settings of the sequence allowed for a smarter numbering system. Our naming is actually more complicated than this because we use decimal places for runs that share either a line- or load-side termination. For instance, a conduit may be able to house three circuits. One circuit terminates in junction box 1, while the next one terminates in j-box 2, and the third in j-box 3. If the main run is named B001, the other two would be B001.1, and B001.2, respectively. I don't expect the sequence tool to be able to handle this strange naming convention, but it would really be great to have the main runs sequence more intelligently at least.

Seriously, a cloud only app does not make sense for IPad users. Most likely the reason we are using an iPad is because we are in the field at a construction site, customer site, traveling, etc. So to assume we are tied to our desk with a speedy internet connection is simply out of touch with your customers.

Please upgrade the app.

Simple. In the Sessions settings —> Permissions tab —> Applied Permissions list, new option "Markup Edit": Deny/Allow. There are already 6 options in the list, I don't think adding another one should be a problem.

By the way the "Full Control" option is not full control, cannot "control" markups. 😣

We don't want all sessions to have the markups editable. We only want the option to turn it on/off by the admin when required.

@Luke Shiras, not to be rude but did you even read the previous comments in this thread? I and many others already replied - in detail - with how our workflows are affected by being unable to edit existing markups.

Of course we can just overwrite other people's markups, but it is much harder to interpret 3 overlapping markups than 1 single markup edited by multiple people. Some legal uses likely require an explicit trail of who did what, so we're not asking Bluebeam to let everyone edit everything always.

When me and the others in this thread are working collaboratively with our colleagues in Microsoft Office 365 or Google Docs or on physical equipment, we all build on and edit each other's work. But when it comes to Bluebeam, we cannot edit each other's work, we have to essentially raze the building by hiding all their work with a filled white rectangle and then make our new edits from scratch. And then when a 3rd person comes along, they have to cover up everything again with a white rectangle and make new edits yet again from scratch.

Hi @Niklas - which view is being used? Selecting Scrolling Pages will achieve the scroll and zoom that you want. Larger page dimensions will open in One Full Page by default. Scrolling Pages can still be selected.

Additionally, you can go into Revu → Preferences and set both modes to scroll with the wheel, allowing you to zoom with CTRL when needed.

How to change mouse wheel behavior | Bluebeam Technical Support