Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
Show only
|
Search instead for
Did you mean:
This page has been translated for your convenience with an automatic translation service. This is not an official translation and may contain errors and inaccurate translations. Autodesk does not warrant, either expressly or implied, the accuracy, reliability or completeness of the information translated by the machine translation service and will not be liable for damages or losses caused by the trust placed in the translation service.Translate
The idea is simple: do not reset the zoom after canceling a command.
You are drawing, making adjustments, checking if everything looks good. You press Escape when you finish, but the view resets to the one from the last click.
Please don't insult me. I have used Revit in architectural practice for over 18 years. I was unable to reproduce the issue you have. (in other words, the zoom did not reset for me after canceling the command when creating or editing an object.) The more details you can give our team, the easier it will be for us to try and help you.
Ok. @fruity101079 please feel free to add additional specific scenarios where this behavior occurs, the simplest case for demonstration purposes I've found is cancelling a filled region. Most of the others are cancelling sketches, and cancelling out of placing a spot elevation, for instance. Cancelling (pressing escape) walls, detail lines, and text notes does not exhibit this behavior.
So yes, this is a behavior that occurs with any command. My example: draw a duct or a wall, anything, while leaving the command active, move around the plan, then press escape (or right-click/cancel). The zoom returns to where the duct (or wall or anything else) was drawn.
@kimberly_fuhrman-jones I shouldn't have said thats its an "unwanted" behaviour, it's really a combination of Revit behaviour and individually workflows. Some will like it and some won't.
@Mark_Engwirda No, you're right. If the developers were users, many of the "complaints" mentioned wouldn't exist. Simply using the software is enough to notice all the UI inconsistencies.
@fruity101079Honestly, as much as we like to meme on this forum, a lot of architects leave to become Autodesk employees. Whether or not those same people are empowered by Autodesk to fix bugs to improve the software experience, or are instead redirected by the almighty monopoly power to compete with other things (like Procore), is another question. Autodesk has architecture locked in, and users get just enough of a trickle of new features (not bugfixes) to keep people from leaving. You and I are both complaining here instead of the Graphisoft forums, so mission accomplished.
In any case, despite my attempt at humor with my comment to Kimberly above, this is a "bug" that you only notice if you're new to the software, or if you've been using it since it was owned by RTC, and at that point you've been stockholm syndrome'd into just accepting that this is the way it's always worked, like @Mark_Engwirda said. I saw your comment and had to verify it for myself before realizing "yes, I am subconsciously frustrated by this, but consciously have come to accept and ignore it." For that reason I'd put fixing this low on my priority list versus things like legend views which are basically non-functional and have been ignored for years...or path of travel lines which, to show what US AHJs require, are actually modeled as railings, and railings, which are actually modeled as filled regions to avoid the brain damage of dealing with how Revit treats railings on stairs.
@adaversaYou put it low on your priority list, but actually, this is the kind of bug that can be fixed very quickly, just like other minor bugs that annoy users. Like the 3D orbit's pivot point.
