-
Notifications
You must be signed in to change notification settings - Fork 46
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
FutureWarning for accessing napari qt_viewer #189
Comments
I see that this is used as a way to add custom napari widgets to the interface anyway... |
Should we do anything about it? |
Heyy hope all is good guys :) I would say try to add an issue to their repo and ask for an alternative way, I used something similar to add available napari plugins to ImSwitch and the code was something they suggested. So probably they have better alternatives now. |
@kasasxav will do that, thanks! |
Sorry forgot to say what it does, There are some widgets that are subclass of NapariBaseWidget, like the shift buttons or the Reset for update levels (
Also, there is a subclass of NapariBaseWidget called NapariHybridWidget, that is used as a superclass for those widgets that want to add stuff into the viewer like the ULensesWidget that adds a layer of an array of dots superimposed to the image. But they don't use specifically the functions addDockWidget and removeDockWidget |
Awesome, thanks Xavier. I'll report this to the napari devs and see what comes out of it |
As you see, you are a standalone application, not a plugin. So instead of using Viever, you may use |
Since napari 0.5.0 is approaching release, I think we should focus on the following warning:
From the stack trace I see that these warnings are caused by the following code in the
NapariBaseWidget
class:@kasasxav do you know what does this do? Is it necessary or can we remove it?
The text was updated successfully, but these errors were encountered: