-
-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
BIM: provide migration to new BIM workbench #14072
Comments
does this also happen with the latest BIM Addon version? |
@maxwxyz this happened with BIM workbench version |
as I recall, there was a recent update of the addon to get rid of that problem. But for users that did not upgrade, they will have this error. |
Indeed this last commit yorikvanhavre/BIM_Workbench@02b509d does show a popup message telling the user to uninstall the BIM addon. Unfortunately indeed they need to update, and I see no way for the new BIM WB to detect this, as it is not loaded when the addon is there. Anything we can do is in the BIM addon, which indeed needs to be updated.... But I think
|
Or have another WB do this? Detect the clashing BIM addon and remove it? Maybe the addon installer could do that? What do you think @chennes ? |
That would rely on the user running the Addon Manager -- I'll mark BIM as obsolete, so the AM should warn you that you have a deprecated addon installed, but FreeCAD could also be more proactive, and during the calls to Init.py we could add code that manually checks for a user-installed BIM and warns about it. We can remove that code in the next release or something like that. |
The thing is, which Init.py... Since the "new" BIM is never run because the old one takes precedence. Maybe Tux could do that? It does a couple of fixes om other WBs already. |
@yorikvanhavre Shall I create a new issue for this?
|
It might be worth a new issue to investigate it properly. I cannot reproduce it on:
|
I'll wait for the next weekly this was my own build. |
@maxwxyz you are compiling FreeCAD yourself, right? The Arch WB is then a leftover from a previous compilation (same happened when Path was renamed to CAM). Just remove Mod/Arch from your install or build folder. This problem will not happen with users using a prebuilt package, so I don't think we need any special action about that... |
@yorikvanhavre yes, thanks for clarification! |
A new scenario is popping up that I had not foreseen... People don't want to delete the BIM addon because they also use a stable 0.21 version side-to-side... Of course, this should not be a problem anymore after publishing 1.0, but it's still annoying, and I'm not sure how best to solve it. Maybe the BIM addon should be renamed to something like BIM021? The problem is, how will that work for people who ALREADY have the BIM add-on installed... |
@yorikvanhavre Maybe 'update' the existing 'external BIM' so it detects whether it is running on 0.22/1.0 so it 'transfers back' to the built-in BIM, or even remove / rename 'itself'? |
Yes that's more or less what it does already (it pops up a warning), the problem is 1) when people didn't update the BIM addon and 2) People do want to keep the BIM addon |
Is there an existing issue for this?
Problem description
After Arch becoming BIM, one of the effects is that the originally external BIM workbench is now part of the FreeCAD install.
After upgrading to a version of FreeCAD with the built-in BIM workbench, users who installed the external BIM workbench in the past, are welcomed with a Python traceback on the Report view and/or the notification area. This is because the two workbenches clash: uninstalling the external BIM workbench solves the issue.
A usability improvement would be to warn users if the external workbench is detected, and suggest to remove it.
Full version info
Subproject(s) affected?
Arch
Anything else?
Traceback that pops up if the two BIM workbenches are present in the system:
Code of Conduct
The text was updated successfully, but these errors were encountered: