Certain rule numbers, when entered in WolframCA's Rule parameter field, cause that instance of WolframCA generator to break* until deleted / restarted.
*Break looks like: only prints alternating solid/empty lines on every odd rule numbers, and prints nothing on even rule numbers.
To replicate bug: try typing in a rule >= 200 or rule 0.
UPDATE: this seems to also have something to do with the OSC messages causing this bug (that, or the bug is not entirely consistent).
Below is a photo of the issue when it does occur.
Could also have to do with an error on the QT console which occurs sometimes when sending osc messages to WolframCA (and no other generators). This error reads:
qrc:/components/fields/TextField.qml:11:5: Unable to assign [undefined] to QString
(I believe this has something to do with formatting done in the meta.json file associated with WolframCA, but I'm not sure)
Finally, in doing further testing on this bug, I was able to cause a full crash of the program with the following errors on the QT console:
Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt.You must not let any exception whatsoever propagate through Qt code. If that is not possible, in Qt 5 you must at least reimplement QCoreApplication::notify() and catch all exceptions there.
libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: generator does not exist18:38:57: The program has unexpectedly finished.
Hopefully this issue will be resolved with the refactoring of the osc messages, but I'm leaving this info here in case it does reoccur.
Certain rule numbers, when entered in WolframCA's Rule parameter field, cause that instance of WolframCA generator to break* until deleted / restarted.
*Break looks like: only prints alternating solid/empty lines on every odd rule numbers, and prints nothing on even rule numbers.
To replicate bug: try typing in a rule >= 200 or rule 0.
UPDATE: this seems to also have something to do with the OSC messages causing this bug (that, or the bug is not entirely consistent).
Below is a photo of the issue when it does occur.
Could also have to do with an error on the QT console which occurs sometimes when sending osc messages to WolframCA (and no other generators). This error reads:
qrc:/components/fields/TextField.qml:11:5: Unable to assign [undefined] to QString(I believe this has something to do with formatting done in the meta.json file associated with WolframCA, but I'm not sure)Finally, in doing further testing on this bug, I was able to cause a full crash of the program with the following errors on the QT console:
Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt.You must not let any exception whatsoever propagate through Qt code. If that is not possible, in Qt 5 you must at least reimplement QCoreApplication::notify() and catch all exceptions there.libc++abi.dylib: terminating with uncaught exception of type std::runtime_error: generator does not exist18:38:57: The program has unexpectedly finished.Hopefully this issue will be resolved with the refactoring of the osc messages, but I'm leaving this info here in case it does reoccur.