This post explains how to combine boolean (Yes/No or True/False) expressions in your PropertyWizard formulas. I’ve written about finding text and using boolean expressions before, but never explained how to combine more than one boolean together. This post fixes that omission.
There are two different ways to combine booleans in PropertyWizard: Logical Functions and Logical Operators. They both do exactly the same thing, so you can use whichever you find easier.
This version removes the WorksharingInfo feature, because after further exploration and testing, it is clear that it cannot be made to work properly with synchronisation. The way the data moves between the Revit session and the Central file means that formulas using the feature will not work properly over time.
There’s a first time for everything, and this is the first time I’ve had to remove a feature from PropertyWizard.
In happier news, this version adds support for centimeter and inch units in formulas, using the suffixes ‘cm’ and ‘inch’. This should allow you to write formulas directly in those units, rather than having to input odd values in ft and mm.
PropertyWizard 1-8-2 includes an extra inverse tan function, ‘atan2’:
The new function allows you to calculate the angle of a line from the line’s Y and X components (note the order of the arguments!) and it will return angle values from -π to +π radians (-180 to +180 degrees).
This is more versatile than the existing function ‘atan’, which can only return angles from -π/2 to +π/2 radians (-90 to +90 degrees).
There are three new text extraction functions in PropertyWizard version 1-8-2. They give you more options for extracting sub-strings from a string of text, alongside the existing substr(<text>, <index>, <count>) function.
This new function returns the end of the <text>, starting from character number <index>. The first character index is zero.
This operates just like substr(<text>, <index>, <count>) but returns all the characters from <index> to the end of the text, not just <count> characters. It’s useful if you want to get rid of the first <count>+1 characters from the text, but don’t know how long the text will be.