This file is indexed.

/usr/include/paraview/pqUndoStackBuilder.h is in paraview-dev 5.0.1+dfsg1-4.

This file is owned by root:root, with mode 0o644.

The actual contents of the file can be viewed below.

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
/*=========================================================================

   Program: ParaView
   Module:    pqUndoStackBuilder.h

   Copyright (c) 2005-2008 Sandia Corporation, Kitware Inc.
   All rights reserved.

   ParaView is a free software; you can redistribute it and/or modify it
   under the terms of the ParaView license version 1.2. 

   See License_v1.2.txt for the full ParaView license.
   A copy of this license can be obtained by contacting
   Kitware Inc.
   28 Corporate Drive
   Clifton Park, NY 12065
   USA

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR
CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

=========================================================================*/
#ifndef pqUndoStackBuilder_h
#define pqUndoStackBuilder_h

#include "vtkSMUndoStackBuilder.h"
#include "pqComponentsModule.h"
#include "vtkSMMessageMinimal.h"

class vtkCommand;

/// pqUndoStackBuilder extends the vtkSMUndoStackBuilder as follows:
/// \li If properties on registered proxies are changed when the builder is not
/// with a BeginOrContinueUndoSet - EndUndoSet block, unless 
/// IgnoreIsolatedChanges is true, it will create a UndoSet with that change 
/// alone and push it on the stack. IgnoreIsolatedChanges does not have any 
/// effect in a BeginOrContinueUndoSet-EndUndoSet block.
/// \li pqProxy objects can be added to be ignored for all changes. Thus,
/// any change event triggered from any of the proxies in the ignore list
/// don't result in updating of the undo stack even when those changes happen
/// with a BeginOrContinueUndoSet - EndUndoSet block (this feature isn't 
/// implemented currently).
/// With these extensions, following are the points we must remember to ensure
/// that Undo/Redo works.
/// \li For any multi-change operations or proxy creation/registration 
///     operations such as creating of a source/reader/filter etc. we must 
///     explicitly use Begin() and End() blocks.
/// \li For modal dialogs which change a bunch of properties when the user 
///     hits Ok, such as Application Settings dialog, change input dialogs, 
///     we must use Begin() and End().
/// \li Any GUI wiget that is a single widget but changes multiple server 
///     manager properties or can lead to mutiple undo steps should use 
///     Begin and End block eg. Accept button, widget to select scalar to color 
///     by etc.
/// \li GUI Widgets that are directly linked to a Server Manager property and 
///     don't need to be accepted, don't need to worry about Undo/Redo at all.
///     The pqUndoStackBuilder will automatically create elements for such 
///     changes and even try to given them friendly labels eg. most Animation 
///     panel properties, display panel widgets etc.
/// Currently, this class automatically adds property modifications alone to 
/// the stack. We may want to explore the possibility of automatically adding 
/// all types of server manager modifications to the stack.
class PQCOMPONENTS_EXPORT pqUndoStackBuilder : public vtkSMUndoStackBuilder
{
public:
  static pqUndoStackBuilder* New();
  vtkTypeMacro(pqUndoStackBuilder, vtkSMUndoStackBuilder);
  void PrintSelf(ostream& os, vtkIndent indent);

  /// Get/Set if all modifications triggerred when not within a Begin/End
  /// block should be added to the undo stack or not. On by default.
  /// Must be set before performing changes to Server Manager which the
  /// GUI is certain shouldn't be added to the Undo stack.
  vtkGetMacro(IgnoreIsolatedChanges, bool);
  vtkSetMacro(IgnoreIsolatedChanges, bool);

  /// Overridden to add observers to not record changes when the
  /// stack is being undone/redone.
  virtual void SetUndoStack(vtkSMUndoStack*);

  /// Overridden to filter unwanted event and manage auto undoset creation
  virtual void OnStateChange(vtkSMSession *session, vtkTypeUInt32 globalId,
                             const vtkSMMessage *previousState,
                             const vtkSMMessage *newState);

protected:
  pqUndoStackBuilder();
  ~pqUndoStackBuilder();

  /// Return false if this state should be escaped.
  bool Filter(vtkSMSession* session, vtkTypeUInt32 globalId);

  bool IgnoreIsolatedChanges;
  bool UndoRedoing;

private:
  pqUndoStackBuilder(const pqUndoStackBuilder&); // Not implemented.
  void operator=(const pqUndoStackBuilder&); // Not implemented.
};

#endif