Change Log - vvvv45beta26
released on 17 08 11
more control over and comfort for numeric values and strings
you still can trust on the magic mechanism that helps you with entering valid values into ioboxes (subtype inference). Valid are only values that nodes connected to the output of the iobox can works with... (Think of the Index (subtype: integer) of a GetSlice (Spreads) connected to an iobox resulting in an iobox that helps you with entering integer values...)
however from now on you additionally can modify this subtype (and therefore behavior of an input pin of e.g. a module and its upwards connected ioboxes) in the following way:
set the BaseSubType (Real, Integer, Boolean) (meaningless configuration pins as a reaction get hidden)
specify the (visual) Precision of a real number
enter a Vector Size used for visual grouping of slices and as a default slice count when user resets via Alt-Right-Click
again a Default value
the Units of measurement to get a better feel for certain values (use s for seconds,m for meters...). (these can easily be entered directly in the iobox when entering a value, e.g. "5 km/h")
Minimum and Maximum now also modify the subtype, that helps entering valid values in this and all upwards connected ioboxes.
if the string representation of a value wouldn't fit into the iobox, a shorter is found by cutting of least significant digits.
"Integer" added to the quick node list
tooltips for vector & matrix subtypes also show up on ioboxes
general improved accuracy in tooltips (scientific notation is used for very big and very small values, otherwise the shortest easiest representation is used). A ~ says that the decimal representation of the value would be longer and has been cut off.
still ioboxes created over middle-click on any vector pin followed by a middle-click on the patch are the easiest way to configure ioboxes
now most subtype properties are copied into the iobox settings and typically need no further adjustment. (e.g. try this feature by fully configuring a first iobox, then middle-clicking on its in or output pin, followed by a middle-click on the patch)
hint: a further middle click labels the iobox (no new feature)
no longer sets the "ColsRowsPages" SliceCount mode, which eases the use of vector ioboxes as inlets for modules
better defaults for vectors, filenames and paths
relative paths (to files and folders) are now converted into absolute paths relative to the patch where they were entered. they still are saved as relative paths though. this should solve bugs in modules that received file paths, since they now already receive a solid absolute path...
Pin Visibility lets you specify how an iobox shows up as a pin from outside the patch (if a Descriptive Name has been entered))
less confusing node pin tool tips
major fixes on texture feedback and resource handling for multi monitor setups
new quitoptions: open patch, new patch, quit
implemented new caching mechanism via nodelist.xml;
if a search path (added via NodeList (VVVV)) contains a nodelist.xml, all node infos beneath this path are read from the nodelist.xml file only.
if a search path does not contain a nodelist.xml, the directory is scanned as usual.
vvvv and the addonpack are shipped with their nodelist.xml files respectively.
for power users: a nodelist.xml file can be generated for a user defined search path by calling 'vvvv.exe /nodelist SEARCH_PATH'.
comparison of startup times incl. addonpack (after windows reboot / second time):
beta23 (1047 nodes): ~9s / ~3s
beta26 (1380 nodes): ~12s / ~3s
Layer outputs on Quads, Effects (...) only show up one slice, reflecting that you can't index into a "layer spread".
some filter nodes now work with "seconds" (time value subtype)
Reloading a patch now doesn't result in disconnecting from its surroundings in the parent patch any longer. You are also asked for if you would want to save your work from now on.
fixed some (last) enum bugs
under some circumstances disabled nodes using transform input pins didn't fetch upstream transforms when switched to enabled state
a color pin didn't report that its values changed if the change wasn't greater than a certain threshold. this led to various inaccuracies in some nodes.