tapnair
2nd add-in using apper gets mixed with the first one
I just started to develop my 2nd add-in and I would like to user apper again. So I've generated a new instance using cookiecutter, changed the id in the manifest and started it up in Fusion 360. But the result is not nice.
The problem is, that it doesn't create a new workspace and mixes the commands with the existing one. Any idea how to solve this or how to not create a new workspace?
It seems to me that Fusion or apper (I'm not sure where the problem lies) references the first add-in's config.py file for all apper add-ins. As far as I can tell, the only place config.py is used is here in the add-in's main py file.
my_addin = apper.FusionApp(config.app_name, config.company_name, False)
If you replace the references to config.py with the strings directly, it will create a separate workspace tab.
my_addin = apper.FusionApp('Some App Name', 'Some Company Name', False)
Ahh yes because of the fact that Fusion add-ins share a single python runtime, commonly named modules will interfere. This is an issue we are currently looking at a much larger solution for, but for now there is not a great solution other than renaming the modules in the second addin. Or just knowing they will conflict and accepting them on the same toolbar. I am hoping we have a much more comprehensive answer for this soon.
On Fri, Aug 21, 2020 at 3:05 PM Justin K [email protected] wrote:
It seems to me that Fusion or apper (I'm not sure where the problem lies) references the first add-in's config.py file for all apper add-ins. As far as I can tell, the only place config.py is used is here in the add-in's main py file.
my_addin = apper.FusionApp(config.app_name, config.company_name, False)
If you replace the references to config.py with the strings directly, it will create a separate workspace tab.
my_addin = apper.FusionApp('Some App Name', 'Some Company Name', False)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/tapnair/apper/issues/3#issuecomment-678535666, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACT5ODK7ZZSU7CPECUXFTYTSB3VQ5ANCNFSM4PGED5DQ .
--
Regards,
Patrick Rainsberry
It should, but if you look into some of the modules inside apper also use config.py to manage some global values. So these also would need to change for each app. I've spent quite a bit of time looking into a better way to handle this conflict and come up pretty empty handed. I am hopeful about a solution that is being investigated right now on the Fusion side, but no promises.
On Sun, Aug 30, 2020 at 1:52 AM WilkoV [email protected] wrote:
@tapnair https://github.com/tapnair : So renaming config.py wouldn't be enough?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/tapnair/apper/issues/3#issuecomment-683394314, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACT5ODIDHQ6YN7EUQCEPLZTSDIHLTANCNFSM4PGED5DQ .
--
Regards,
Patrick Rainsberry