-
-
Notifications
You must be signed in to change notification settings - Fork 337
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/show view range #2178
Feature/show view range #2178
Conversation
active view was actually the project browser had to call for view change and restore the lost selection
Stale issues bot
…ines Drop old ipy engines
extents without section box, wip ui components, follow doc change
Need to finalize the ui with a simple control to dinamically show the actual elavation values |
Let me know when you feel it is ready for review @thumDer |
Technically it is ready, the core functionality is working, can be tested. I could use some inputs for the ui, though... I'm a bit stuck. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I did some UI and cosmetic changes.
It seems the windows is not reporting distances for view ranges _ not implemented? Looking quickly at the code, it remains at None Line https://github.com/thumder/pyrevit/blob/d090a31116f70bf9b9219a0ead5aed87356784b7/extensions/pyRevitTools.extension/pyRevit.tab/Toggles.panel/toggles3.stack/ViewRange.pushbutton/script.py#L203
and following
All in all a great tool. |
yep that is still a TODO, but shouldn't take that long. Let me finish it, and it will be ready to merge. |
bump ;p @thumDer |
It's happening! :) I might replace the wpf grid to a table, and it would be really great to show the (length) units of the elevation. It is extracted from the project units, but showing it is a bit more complicated than I thought. |
Do you want me to merge this first iteration? @thumDer |
I'll try to finish this week with the fine tuning. If I don't have enough time I'll close the PR, and merge it as it is. (If you have no objections, of course.) |
🪖no objection. Sir. |
📦 New public release are available for 4.8.16.24121+2117 |
Hi there, I installed pyRevit v4.8.16.24121 and tested 'Show View Range' in Revit 2021.1.9 and I got this error. _IronPython Traceback: Script Executor Traceback: |
Yes, that is what I forgot to do to disable the script in versions lower than 2023, because that specific |
That seems like a different issue with the pyRevit loader. If it persists please post an issue, with the required information. |
@jmcouffin I've doublechecked and it might be possible to make this work in earlier Revit versions without the |
|
@thumDer I would avoid that. # minimium supported Revit version
min_revit_version: 2023 or do it in the tool script itself, but I prefer the use of the flag There is no particular will to support legacy versions when adding new tools. |
I thought that must be a thing, just didn't have time to doublecheck :D I'll update the bundle on the dev branch |
done via 5c12574 |
Yes, I'm aware Autodesk support is always restricted to the last 4 versions
of the product.
…On Thu, 2 May 2024 at 08:22, Jean-Marc Couffin ***@***.***> wrote:
Revit 2021.1.9 and I got this erro
@Robbo1234 <https://github.com/Robbo1234>
You know that 2021 is not supported by Autodesk anymore, right?
—
Reply to this email directly, view it on GitHub
<#2178 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACC6Z45WTLE7ND5VTP5KYRLZAHSTLAVCNFSM6AAAAABFO3DF6SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBZG44DKMZTGM>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
If Levels are turned off in v/g (our default), I get this:
Also, I notice the extents of the colored planes match the extents of Level 1 (or maybe the first Level in the model) instead of matching the extents of the view. |
Please create an issue/feature request @RevitIRL |
implementation of #2061