| View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0012681 | ParaView | (No Category) | public | 2011-10-25 20:23 | 2016-07-13 21:30 | ||||
| Reporter | Alan Scott | ||||||||
| Assigned To | Alan Scott | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | closed | Resolution | fixed | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 3.12 | ||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0012681: Prism does not find remote plugin correctly | ||||||||
| Description | When starting Prism for the first time (and I suspect any plugin) remote server, if you have started in a different directory than the normal bin directory, the plugin library will not be found. Try this: start client from top of build, as in ./bin/paraview... start server from top of build, as in ./bin/pvserver ... Now, try to load the remote server Prism plugin. It won't show in the window. If it does, try again without reading in config state. One option, although not a good one, would be to have an environment var that points to optional plugins that need to be loaded. Another would be to include a .plugins file in the server side. | ||||||||
| Tags | No tags attached. | ||||||||
| Project | Sandia | ||||||||
| Topic Name | |||||||||
| Type | incorrect functionality | ||||||||
| Attached Files | |||||||||
| Relationships | |
| Relationships |
| Notes | |
|
(0036453) Alan Scott (manager) 2016-07-13 21:30 |
Prism has gone away. Closing bug. |
| Notes |
| Issue History | |||
| Date Modified | Username | Field | Change |
| 2011-10-25 20:23 | Alan Scott | New Issue | |
| 2016-07-13 21:30 | Alan Scott | Note Added: 0036453 | |
| 2016-07-13 21:30 | Alan Scott | Status | backlog => closed |
| 2016-07-13 21:30 | Alan Scott | Assigned To | => Alan Scott |
| 2016-07-13 21:30 | Alan Scott | Resolution | open => fixed |
| Issue History |
| Copyright © 2000 - 2018 MantisBT Team |