|
Notes |
|
|
(0014415)
|
|
Utkarsh Ayachit
|
|
2008-12-22 09:14
|
|
|
We may also want to provide simple mechanisms (and/or documentation) to check components of the plugin were loaded eg. test if proxy can be created etc. |
|
|
|
(0017456)
|
|
Utkarsh Ayachit
|
|
2009-09-14 14:05
|
|
|
Add information about what version of ParaView the plugin was compiled with into the plugin and use that to match the ParaView version at run-time. People often load different version plugins on different versions of ParaView which we clearly don't support. This will save us a lot of headache. |
|
|
|
(0017706)
|
|
Utkarsh Ayachit
|
|
2009-09-22 13:39
|
|
|
This is going to be tricky for 3.6.2 since the current plugins don't have meta-data to compare version information etc. Unless someone objects, I am deferring this to 3.8. We need to do a revamp of plugins for 3.8 to provide for better debugging and error reporting. |
|
|
|
(0019088)
|
|
Utkarsh Ayachit
|
|
2010-01-11 14:09
|
|
|
Added a PV_PLUGIN_DEBUG environment variable (following Qt's model for providing verbose errors for plugins). If this variable is set, then ParaView prints logs on the terminal which are helpful at determining why the plugin load failed. |
|
|
|
(0019464)
|
|
Alan Scott
|
|
2010-02-05 20:01
|
|
|
I THINK it's fixed. Tested local server, XP. |
|