Commit 9afd422a authored by Cory Quammen's avatar Cory Quammen Committed by Kitware Robot
Browse files

Merge topic 'misc-typos'

29f5b74a

 Misc. typos
Acked-by: Kitware Robot's avatarKitware Robot <kwrobot@kitware.com>
Acked-by: Cory Quammen's avatarCory Quammen <cory.quammen@kitware.com>
Merge-request: !2561
parents 20a85cdf 29f5b74a
Pipeline #108894 passed with stage
in 0 seconds
#New QVTKOpenGLWidget Implementation
A new implementation of the QVTKOpenGLWidget have been added to VTK and ParaView now makes uses of it.
A new implementation of the QVTKOpenGLWidget has been added to VTK and ParaView whom now makes uses of it.
* The main feature of this new widget is the support of quad buffer based stereo mode "Cristal Eyes" wich was unsupported since the switch to Qt5.
* This new widget ensure the rendering can only happen with a valid widget (aka ready for rendering)
* This new widget support HiDpi rendering
* This new widget improve also a few issues of flickering with the old widget.
* The main feature of this new widget is the support of quad buffer based stereo mode "Crystal Eyes" which was unsupported since the switch to Qt5.
* This new widget ensures the rendering can only happen with a valid widget (aka ready for rendering)
* This new widget supports HiDpi rendering
* This new widget also improves a few issues of flickering with the old widget.
* The old widget have been kept and renammed QVTKOpenGLSimpleWidget and should be used for simple rendering or when the widget is automatically native.
* This new QVTKOpenGLWidget class does not support Qt::WA_NativeWindow flag but the QScrollArea used in pqTransferFunctionWidget force it to be native.
* The old widget is used in pqTransferFunctionWidget
......@@ -23,7 +23,7 @@ IF(PARAVIEW_BUILD_QT_GUI)
GROUP_NAME "ToolBar/MyActions")
# another way of adding a toolbar is to simpy add a new QToolBar subclass.
# another way of adding a toolbar is to simply add a new QToolBar subclass.
ADD_PARAVIEW_TOOLBAR(IFACES_2 IFACE_SRCS_2 CLASS_NAME MyToolBar)
# create a plugin for this panel
......
......@@ -55,7 +55,7 @@ void vtkPVRampKeyFrame::UpdateValue(double currenttime, vtkPVAnimationCue* cue,
unsigned int end_novalues = next->GetNumberOfKeyValues();
unsigned int min = (start_novalues < end_novalues) ? start_novalues : end_novalues;
// interpolate comman indices.
// interpolate common indices.
for (i = 0; i < min; i++)
{
double vmax = next->GetKeyValue(i);
......
......@@ -539,7 +539,7 @@ void vtkSMSessionClient::PushState(vtkSMMessage* message)
msg.set_global_id(message->global_id());
msg.set_location(message->location());
// Add extra-informations
// Add extra-information
msg.set_share_only(true);
msg.set_client_id(this->ServerInformation->GetClientId());
......
......@@ -947,7 +947,7 @@ int vtkPGenericIOMultiBlockReader::RequestData(vtkInformation* vtkNotUsed(reques
output->SetNumberOfBlocks(this->MetaData->NumberOfBlocks);
// Get the global dimensions and physical orign & scale from
// Get the global dimensions and physical origin & scale from
// the genericio file and add them to the dataset
uint64_t tmpDims[3];
double tmpDouble[3];
......
......@@ -738,7 +738,7 @@ vtkIdType* vtkAMRDualClipLocator::GetCornerPointer(
// The problem is that the range may become larger than our locator array.
// The minimum extent can get smaller when we mask bits off.
// Also, we have to convert back to relative index to remove the global offset.
// Different point in the locator may be in different degnerate levels,
// Different point in the locator may be in different degenerate levels,
// so we do need to convert index back to the original level.
// It looks like we need to know the origin of the block.
xCell += blockOrigin[0];
......
......@@ -74,7 +74,7 @@ int vtkIsoVolume::RequestData(vtkInformation* vtkNotUsed(request),
vtkDataObject* inObj = inInfo->Get(vtkDataObject::DATA_OBJECT());
vtkDataObject* outObj = outInfo->Get(vtkDataObject::DATA_OBJECT());
// Comman vars.
// Common vars.
vtkStdString arrayName("");
int fieldAssociation(-1);
// double* range (0);
......
......@@ -1645,7 +1645,7 @@ void vtkRectilinearGridConnectivity::ExtractFragmentPolyhedra(
double dataBbox[6];
double acumVols[8]; // accumulated volume a vertex scatters
double lastFrcs[8]; // to reuse quad scalars (1, 2, 5, 6 only)
double nodeFrcs[8]; // fractions of the ORIGINAL hexas (noe nodes)
double nodeFrcs[8]; // fractions of the ORIGINAL hexas (now nodes)
double lastVols[8]; // to reuse --- similar to lastFrcs
double nodeVols[8]; // volumes of the ORIGINAL hexas (now nodes)
double lastCord[3];
......@@ -2920,7 +2920,7 @@ void vtkRectilinearGridConnectivity::AddPolygonsToFaceHash(
vtkRectilinearGridConnectivityFace** newFaces = NULL;
// determine the number of integrated components (including the material
// volume) to be saved to the global fragment attributs array and allocate a
// volume) to be saved to the global fragment attributes array and allocate a
// buffer for a tuple
tupleSiz = this->Internal->NumberIntegralComponents + 1;
tupleBuf = new double[tupleSiz];
......
......@@ -2,8 +2,8 @@ GmshReader Plugin
ParaView/VTK reader for visualization of high-order polynomial solutions under the Gmsh format.
Version: 1.0
See Copyright.txt, License.txt and Credits.txt for respectively copyright,
license and authors informations. You should have received a copy of
See Copyright.txt, License.txt and Credits.txt for respective copyright,
license and authors information. You should have received a copy of
these files along with ParaViewGMSHReaderPlugin.
-For more information on Gmsh see http://geuz.org/gmsh/
......@@ -161,7 +161,7 @@ If present, FieldInfo contains at least three elements related to the solution d
* The TimeSteps element contains TimeStep sub-elements. Each TimeStep element specifies an index (index_attribute), an index used in the geometry filename pattern (geometry_index), an index used in the field filename pattern (field_index) and a time value (float).
1. number_of_steps specifies how many steps of your solution you want to visualize. These steps can then be visualized sequentially with the ParaView play button (green arrow).
2. Normally there is one TimeStep element per timestep. However, it is possible to ask the reader to automatically generate timestep entries. This is done by setting the (optional) auto_generate_indices to 1. This is the usual and recommended mode for contant intervals between successive time steps. In this case, the reader will generate number_of_steps entries.
2. Normally there is one TimeStep element per timestep. However, it is possible to ask the reader to automatically generate timestep entries. This is done by setting the (optional) auto_generate_indices to 1. This is the usual and recommended mode for constant intervals between successive time steps. In this case, the reader will generate number_of_steps entries.
3. The geometry_index and field_index of these entries will start at start_index and will be incremented by increment_index_by.
4. The time value of these entries will start at start_value and will be incremented by increment_value_by.
......
......@@ -71,7 +71,7 @@ protected:
/**
* Convenience method to fill field data of provided dataset
* using data for the speicfied leaf number
* using data for the specified leaf number
*/
void FillFieldData(vtkDataSet* dataset, int leaf);
......
......@@ -19,7 +19,7 @@ def _count(values):
return 1
def _stringify(values):
"""internal method: used to convert values to a stirng suitable for an xml attribute"""
"""internal method: used to convert values to a string suitable for an xml attribute"""
if type(values) == list or type(values) == tuple:
return " ".join([str(x) for x in values])
elif type(values) == type(True):
......@@ -517,7 +517,7 @@ def load_plugin(filepath, default_modulename=None):
return module
def reload_plugin_module(module):
"""helper function to relead aplugin module previously loaded via
"""helper function to reload a plugin module previously loaded via
load_plugin"""
from inspect import getsourcefile, ismodule
if ismodule(module) and getsourcefile(module):
......
......@@ -69,7 +69,7 @@ to build the ParaView-specific XML via decorators.
Decorator Basics
================
There are four main classes currently avilable: `smproxy`,
There are four main classes currently available: `smproxy`,
`smproperty`, `smdomain`, and `smhint`. Each provides a set of decorators to
declare a proxy, property, domain or a hint, respectively.
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment