- 13 Aug, 2018 1 commit
-
-
Andrew Bauer authored
Fixes for both pvbatch and pvpython to let them know that they may want to check on the file name or path for misspellings. Fixes #17906.
-
- 31 Oct, 2017 1 commit
-
-
Utkarsh Ayachit authored
When`paraview` is imported in a standard Python interpreter (not via pvpython), we ended up initializing MPI due to !1987. That caused failures generating sphinx documentation with Python 3. In any cause, it sounds like a risky move to init MPI in a standard Python interpreter unless user explicitly asked for. They do can that by doing the following: import paraview paraview.options.batch = True
-
- 02 Mar, 2017 1 commit
-
-
Michel Zou authored
-
- 18 Oct, 2016 1 commit
-
-
Kitware Robot authored
This commit was generated automatically by running: Utilities/Scripts/clang-format.bash --tracked
-
- 26 Sep, 2016 1 commit
-
-
Shawn Waldon authored
This ensures consistent defaults across ParaView, pvpython and pvbatch. This affects all PV-based applications and moves this setting from something specified in ParaView's Qt UI to an internal default. See the MajorAPIChanges.md file for details. See ParaView issue #16913.
-
- 20 Sep, 2016 1 commit
-
-
Ben Boeckel authored
-
- 13 Apr, 2016 1 commit
-
-
Ben Boeckel authored
-
- 13 Nov, 2015 1 commit
-
-
Mathieu Westphal authored
THe pvPluginLoader will now check for a file in PV_PLUGIN_CONFIG_FILE if found, it will use this xml file t
-
- 20 Aug, 2015 1 commit
-
-
Brad King authored
Use the following commands to switch to standard header and namespace: git grep -l vtksys/ios | xargs sed -i 's|vtksys/ios/sstream|sstream|' git grep -l vtksys_ios:: | xargs sed -i 's|vtksys_ios::|std::|g'
-
- 13 Aug, 2015 1 commit
-
-
Mathieu Westphal authored
1. Using pqSettings location to provide User Setting path in pqCoreUtilities::getParaViewUserDirectory() 2. Emulating QSettings use of XDG_CONFIG_HOME in vtkInitializationHelper::GetUserSettingsDirectory() 3. Use of pqCoreUtilities::getParaViewUserDirectory in pqServerConfigurationCollection::userServers()
-
- 23 Jul, 2014 4 commits
-
-
Cory Quammen authored
If this isn't done, then the site settings collection, if it exists, will be treated incorrectly as the user settings collection, setting changes will be saved there, and that collection will be written to the user settings file. Change-Id: I3581efc6ecc2bb2ae43f41854c7f8580776632e9
-
Cory Quammen authored
Now instead of checking whether a settings file exists before attempting to load it, we just try to load it and use the return code from vtkSMSettings::AddCollectionFromString() to determine whether to search other locations. This required fixing some of the behavior of vtkSMSetting::AddCollectionFromFile() when the given file couldn't be loaded. Change-Id: Ic4f1caea33454453a4c7049c10642148a91f9cad
-
Cory Quammen authored
When set, the application will print information about where settings file are being looked for and whether loading them succeeded. Change-Id: Ie98c568c417cef4bdbfb545ea5fe87bb3663453f
-
Cory Quammen authored
The original intent was to indicate success or failure of loading settings. However, it's not clear what success or failure means because it is legitimate to not have a user- or site-settings file, so indicating failure if one of these cannot be loaded is not really accurate. Moreover, the return value wasn't used by the caller. In addition, there was a bug in the previous implementation. If the user settings weren't loaded, the site settings wouldn't be loaded either. Now this method no longer returns any boolean value. Change-Id: I039fc39aec3866e0d5b349fa43fc8f5c0d648d2a
-
- 17 Jul, 2014 1 commit
-
-
Cory Quammen authored
Change-Id: Id26c59f69e3a2d7984d7350bc6bdbdae94ed2f13
-
- 07 Jul, 2014 1 commit
-
-
Cory Quammen authored
Added check for sufficient path string length prior to searching for "/bin" at the end of the path. This solves exceptions thrown by a number of tests. Change-Id: Ibefe7356a9f5b0353822258155bba706f1e26f2e
-
- 05 Jul, 2014 1 commit
-
-
Cory Quammen authored
ParaView will now look under <install_directory>/share/paraview-4.1 for site-wide custom settings. Change-Id: I5a7226551090ecc15dd468995276d1da6b7d723c
-
- 17 Jun, 2014 1 commit
-
-
Cory Quammen authored
This matches what is done with the UserSettings.json settings file. Change-Id: Ic4b7be7d9ef7b7570455df2003809574edb7458e
-
- 10 Jun, 2014 3 commits
-
-
Cory Quammen authored
Changed default name to GenericParaViewApplication in the initialization helper to prevent any accidental reading/writing of ParaView's settings file by branded applications. Change-Id: I1d4b3e7df383a070df5b4c83db8de88a944d6316
-
Cory Quammen authored
Also, fixed a bug where settings with default values were being saved to the settings file. Change-Id: Ia3908b94678b1828c89d7ef4090bebc54d43e4d4
-
Cory Quammen authored
- Added organization name member to vtkInitializationHelper - Changed location of user settings file to CONFIG_DIR/ORGANIZATION_NAME/APPLICATION_NAME-UserSettings.json This will enable the same organization to have more than one branded ParaView application with different settings. - Creates the directory in which the settings file should reside if it does not exist. - Application and organization names are set in pqApplicationCore instead of branded_paraview_initializer.cxx.in Change-Id: Ic50a020c8acf984c2284e824fa99145a93ad028e
-
- 25 May, 2014 1 commit
-
-
Cory Quammen authored
Now settings are saved to a directory with the branded application name. Change-Id: I2a9f99d47d43e2567588eab0b1bac71cac64a9b7
-
- 23 May, 2014 1 commit
-
-
Utkarsh Ayachit authored
All server processes, including satellites in batch mode, were reading and saving settings files. That was incorrect. The settings files need to processed only on client processes. In symmetric batch mode too, we read the file on the root node and then distribute it to everyone. This commit fixes this logic. Change-Id: I7835f3c1ccc7eb8369ec4cf14ba7d838ee7ee2b6
-
- 19 May, 2014 1 commit
-
-
Utkarsh Ayachit authored
Fixed missing dependency on SMApplication module. We needed to add vtksys explicitly. Also added mechanism to disable loading/saving of settings files. vtkCPCxxHelper uses this mechanism to turn off settings loading/saving when coprocessing. Change-Id: I02c8612bc045ede82b7ae3c72b0410570dbf739f
-
- 06 May, 2014 8 commits
-
-
Cory Quammen authored
Looks for a file called SiteSettings.json in the same directories where .plugins is searched for withh the exception of Plugins directories. Change-Id: If0bb8ef1f8e92f6aa70eb8d2a4eb8bce48e862c8
-
Cory Quammen authored
Change-Id: I85b3fc1f2f845489d71f92f1809745ab0cca5efc
-
Cory Quammen authored
Maybe more portable? Change-Id: Iaf6bfb48e92568f673849e7dda6e473d024daf81
-
Cory Quammen authored
Settings will not be loaded when this flag is enabled. Also refactored vtkSMSettings class to load any number of settings strings/files and to assign priorities for the different settings. Change-Id: I6eed2553cd83579db1dbb1a15f831ad6ffe0e6b1
-
Cory Quammen authored
Change-Id: I700b3945548276e971e2e86f49882cbba5eb2166
-
Cory Quammen authored
Change-Id: Icf7f354a403e8b684fcf010d52a40ab710635516
-
Cory Quammen authored
This avoids the need to synchronize the Json::Value and JSON string member variables. Made member names for setting/getting settings from/to strings more accurate. Change-Id: Ic499a27cc0c12b4e97a0b32ddb975318b23593aa
-
Cory Quammen authored
This class is meant to be a central location for user-defined program defaults. It supports the notion of site-wide settings meant to be used for installations of ParaView in a centralized location for a specific computing site. Site-wide settings can be overridden by user-specific settings specified in a file in the user's home directory. The site-wide file is named .pvsitesettings.js and its location has yet to be determined. The user-specific a file is named .pvsettings.js and it is expected to be in the user's home directory. An example file for changing the properties in the SphereSource looks like: { "sources" : { "SphereSource" : { "Radius" : 4.0, "ThetaResolution" : 32, "PhiResolution" : 32, "Center" : [1.0, 2.0, 3.0] } } } A common pattern of usage is expected to involve calling vtkSMSettings::SetProxySettings(vtkSMProxy* proxy) after a proxy is created in the application. Change-Id: Ieaca8f4d1ea7258372bf84af87b6a1bae0c24ff5
-
- 18 Mar, 2013 1 commit
-
-
Utkarsh Ayachit authored
vtkInitializationHelper was using vtkSMUtilities which is in vtkPVServerManagerRendering. That added an unnecessary dependency on rendering which caused failure in Catalyst builds withoout rendering. Moving the ListAttachedMonitors() method from vtkSMUtilities to vtkInitializationHelper to overcome this issue. Change-Id: Ife732871fd70709f48c132ed13c0b6dc241baf0d
-
- 11 Feb, 2013 1 commit
-
-
David C. Lonie authored
This adds functionality to help users setup multidisplay windows environments. Running this on a multidisplay box gives output similar to the following: > paraview.exe --print-monitors Device: "\\.\DISPLAY1" Geometry: 1080x1920+0+0 (primary) Device: "\\.\DISPLAY2" Geometry: 1920x1080+1080+0 Change-Id: I938d41fba780c7ccbfd3bfaed8a72733150f984a
-
- 28 Sep, 2012 1 commit
-
-
Burlen Loring authored
Rename vtkInitializationHelper::TestingInitialize/Finalize to vtkInitializationHelper::StandaloneInitialize/Finalize. Change-Id: Icdb1ca8c22a42b6306ec47c93a85b7f90148eba6
-
- 19 Sep, 2012 1 commit
-
-
Burlen Loring authored
Added methods Initialize/Finalize methods vtkInitializationHelper for ctests to call. Explicitly calling these prevents the linker from removing VTK factories' auto initialization code which is otherwise unreferenced during static builds. The new methods also take care of protobuf cleanup. Remove sm xml from the plugin for the SQ algorithms that make use of RK45 integrator. VTK's implementation is not computing the step size correctly. Change-Id: Id0261d1e004cf7f9313bc0fee28aeca4feda7d65
-
- 05 Sep, 2012 1 commit
-
-
Utkarsh Ayachit authored
Ensure that the plugins in PV_PLUGIN_PATH are loaded after ParaView has been initialized.
-
- 26 Jul, 2012 1 commit
-
-
Utkarsh Ayachit authored
The vtkPVPluginTracker was being initialized prematurely resulting in the .plugins file not being located/parsed. Fixed that. Change-Id: I7cbbec224e8fe60d86406d3656ccad976f47be2d
-
- 25 Jul, 2012 1 commit
-
-
Utkarsh Ayachit authored
Fixing export macros (and other header testingn failures). Change-Id: Ib92aed44cd105f66abad99b88edccddb34ae9859
-
- 02 Jul, 2012 1 commit
-
-
Utkarsh Ayachit authored
-