kindred/create
1
1
Fork 0
Code Issues 37 Pull Requests Actions Packages Projects 9 Releases 2 Wiki Activity

Misc. typos and whitespace fixes

Browse Source 
Found via `codespell -q 3 --skip="*.po,*.ts,./.git,./src/3rdParty,./src/CXX,./src/zipios++,./src/Mod/Assembly/App/opendcm" -I ../fc-word-whitelist.txt` and `grep`
This commit is contained in:
luz.paz
2018-10-21 18:04:43 -04:00
committed by Yorik van Havre
parent 968ce141d0
commit f976a4f734
8 changed files with 66 additions and 66 deletions
Download Patch File Download Diff File Expand all files Collapse all files

40
src/App/Property.h
View File

@@ -90,7 +90,7 @@ public:
virtual const char* getEditorName(void) const { return ""; }
/// Get the type of the property in the container
short getType(void) const;
short getType(void) const;
/// Get the group of this property
const char* getGroup(void) const;
@@ -121,11 +121,11 @@ public:
//@{
/// Set the property touched
void touch();
/// Test if this property is touched
/// Test if this property is touched
inline bool isTouched(void) const {
return StatusBits.test(Touched);
}
/// Reset this property touched
/// Reset this property touched
inline void purgeTouched(void) {
StatusBits.reset(Touched);
}
@@ -166,7 +166,7 @@ public:
protected:
/** Status bits of the property
* The first 8 bits are used for the base system the rest can be used in
* descendent classes to to mark special stati on the objects.
* descendent classes to mark special statuses on the objects.
* The bits and their meaning are listed below:
* 0 - object is marked as 'touched'
* 1 - object is marked as 'immutable'
@@ -196,7 +196,7 @@ private:
/** Base class of all property lists.
* The PropertyLists class is the base class for properties which can contain
* multiple values, not only a single value.
* multiple values, not only a single value.
* All property types which may contain more than one value inherits this class.
*/
class AppExport PropertyLists : public Property
@@ -204,24 +204,28 @@ class AppExport PropertyLists : public Property
TYPESYSTEM_HEADER();
public:
virtual void setSize(int newSize)=0;
virtual int getSize(void) const =0;
virtual void setSize(int newSize)=0;
virtual int getSize(void) const =0;
};
/** A template class that is used to inhibit multiple nested calls to aboutToSetValue/hasSetValue for properties.
*
* A template class that is used to inhibit multiple nested calls to aboutToSetValue/hasSetValue for properties, and
* only invoke it the first and last time it is needed. This is useful in cases where you want to change multiple
* values in a property "atomically", using possibly multiple primitive functions that normally would trigger
* aboutToSetValue/hasSetValue calls on their own.
* A template class that is used to inhibit multiple nested calls to
* aboutToSetValue/hasSetValue for properties, and only invoke it the first and
* last time it is needed. This is useful in cases where you want to change multiple
* values in a property "atomically", using possibly multiple primitive functions
* that normally would trigger aboutToSetValue/hasSetValue calls on their own.
*
* To use, inherit privately from the AtomicPropertyChangeInterface class, using your class name as the template argument.
* In all cases where you normally would call aboutToSetValue/hasSetValue before and after a change, create
* an AtomicPropertyChange object before you do the change. Depending on a counter in the main property, the constructor might
* invoke aboutToSetValue. When the AtomicPropertyChange object is destructed, it might call hasSetValue if it is found
* necessary to do (i.e last item on the AtomicPropertyChange stack). This makes it easy to match the calls, and it is also
* exception safe in the sense that the destructors are guaranteed to be called during unwinding and exception
* handling, making the calls to boutToSetValue and hasSetValue balanced.
* To use, inherit privately from the AtomicPropertyChangeInterface class, using
* your class name as the template argument. In all cases where you normally would
* call aboutToSetValue/hasSetValue before and after a change, create an
* AtomicPropertyChange object before you do the change. Depending on a counter
* in the main property, the constructor might invoke aboutToSetValue. When the
* AtomicPropertyChange object is destructed, it might call hasSetValue if it is
* found necessary to do (i.e last item on the AtomicPropertyChange stack).
* This makes it easy to match the calls, and it is also exception safe in the
* sense that the destructors are guaranteed to be called during unwinding and
* exception handling, making the calls to boutToSetValue and hasSetValue balanced.
*
*/