Best Of
Re: Tool Chest UX regressions
I concur with the issues/problems noted above.
Additionally, I am having another extremely aggravating problem, which only started happening after updating to v21.6. Quite often, no matter how carefully I do it, the instant I click on a tool in the tool chest, the whole tool chest side panel will jump as if I had scrolled the mouse wheel, which causes the tool that I clicked on to move to a different location relative to all of the other tools within the set, and sometimes even causing it to move from its original tool set into an entirely different set.
Wondering if anyone else is seeing this behavior. Not sure if it is a bug in this latest version Bluebeam, or if it is possibly a problem with my mouse or PC that just coincidentally started at about the same time I installed the BB update.
RickO
Re: Is there a way to downgrade the version of REVU I am using?
Managed to find the old version. I had to delete the existing application off my computer and redownload the older version. Worked pretty seamlessly. Tool chest is back in working order
Is there a way to downgrade the version of REVU I am using?
Resolved: Delete existing version and install old version.
Question is in the title. I use the tool chest for my job, I make/edit/modify maybe 50-100 markups a day and whatever was done to the tool chest has ruined its functionality.
A few examples:
- Double click to edit name is now extremely inconsistent.
- The markups are also no longer "glued" to their spots. I'll try to double click a markup to change the name and my markup flies up or down the list.
- See above, the markups feel like they're on a stick of butter. I try to click them to select them and they somehow manage to move around.
- The search bar feels very slow now, or rather has started lagging which I've never had happen before.
- Editing names has now become very difficult for no reason.
- Use to be able to double click then hit my arrow key to place my cursor so I could edit my text where needed. Now it deletes the entire now
- The text will highlight and when I click the text, approximately 50% of the time it'll exit out of the rename function.
Re: Auto Save
You don't support it because it wipes the undo list? What world is this not something that can be achieved. If only other programs could do it. Like … Word and Excel…
Falsifying excuses is aggravating. I'm now up to 25 hours of lost work due to no autosave feature. And don't even start about the non effective recovery options or "prompts to save".
Re: Measure Markup will not display
Is the markup greyed out or missing completely?
Is this happening on all PDF's or just this one package?
My first thought is that a Filter has been applied somewhere and needs to be removed.
Second would be that the drawings have been locked.
Re: Offset Tool
The Multiply tool has been amazing so far. I'd love to see that expanded upon to allow more options when offsetting things. It's fairly cumbersome to use at the moment, but looks like it could be very powerful eventually.
Re: Blue Beam Studio , Why cant we add layers to uploaded PDF in a set
Shanoc, the extreme lockdown of options in bluebeam sessions is a feature great for collaborating with outsiders to your organization, but users have wanted for years to be able to reduce those restrictions and collaborate internally on one PDF, with the ability to edit others markups and you know, use the program for all its features.
Re: Cannot Change Status of Markup in a Session
As Luke posted before, the status model has to be added to a file prior to upload into a session in order to be used during a session. We use custom models so it's on our checklist of things that need to happen to files prior to being uploaded. The common workflow is saving the custom status model to the profile, set that profile current when preparing additional files to be used in the session, check to see that you could set that status to the desired state within the file and then save the PDF prior to uploading into the session.
We occasionally receive files from 3rd parties that we need to review, and to add the custom status model into those, we keep a clean pdf that just has the status models in it that we can add to other files as needed, save, remove the status page pdf, save, and the statuses will remain.
Any markup that was made on a file prior to the file being uploaded will be locked (non-editable) once loaded into a session - even to the person who made that comment, but status can still be changed, as you can with markups made by others within a session.
If you are not seeing any status available to select within a session at all, open a file (any file) outside of a session and within the markups list, go to Manage Status and in there, check on one or both of the default status models (Review and Migration). Go back to your session and you will at least have those to select from. You can't add in new models at that point, but you can at lease use the embedded ones.
Re: Revu has high memory usage
Seems high, indeed! I have never noticed any lagging due to local resources. That problem usually comes from ISP/Network/Bandwidth issues and is sporadic.
System: Windows 11 Home. 64-Bit. Intel Core i7. Running Bluebeam 21.6.
You might check to make sure your machine matches, in case something there may be out of sync with your BB Setup.
I looked into what mine is running, for comparison. 5 tabs (local) sits at ~ 830 MB.
Adding a BBStudio connection and opening a file from that kicks it up to ~1300 MB.
Couple of ideas… Have you changed settings for any kind of graphics optimization that could be funneling resources to Bluebeam? Also, have you changed priority for Bluebeam in your Task Manager?
Hope this helps get this thing working with the rest of your system.
JEsurfer
Re: Is There a Way to Lock a Form Field?
There are several options, Lock will keep it in place and the properties will be locked but still able to be modified. Read only will keep people from modifying it. Visibility settings can hide it. Putting it on a layer and disabling, or even setting it to be off by default is a way to keep it out of the way as well. The last two options are pretty similar, in that the fields still exist, but you just can't see them unless you go into form selection mode. Personally I like the layers because I can use JavaScript to turn the layers on and off with buttons.


