Closed Taste62 closed 6 months ago
@Taste62 just checked. DMX USB is working as expected on GitHub Action Windows builds.
I just couldn't figure out, what file to download from the drivers page for Windows 10 64bit, so i disabled it like I was told to do in the build instructions. I don't know if that somehow influenced the velleman plugin, but the build stoped with this error message, so just disabled it too.
[ 55%] Automatic MOC and UIC for target midi_test [ 55%] Built target midi_test_autogen [ 56%] Built target midi_test [ 56%] Automatic MOC and UIC for target velleman [ 56%] Built target velleman_autogen make[2]: No rule to make target 'C:/Qt/K8062D/K8062D.a', needed by 'plugins/velleman/src/velleman.dll'. Stop. make[1]: [CMakeFiles/Makefile2:5850: plugins/velleman/src/CMakeFiles/velleman.dir/all] Error 2 make: *** [Makefile:156: all] Error 2
Oh, I thought you were using automated builds. Step back..do you know what GitHub action builds are and how to download the built artifacts?
Nope, how do they work?
Every time I push a change to GitHub, 4 builds are automatically generated and can be downloaded from the "Actions" section of GitHub. Pick a commit and scroll down until you see the Artifacts section.
Ok, thanks, found it!
Having at least one property of type "string" in the property list results in it taking up all available space, instead of just a bit as the other components.
Normal property window:
-> The property window has it's usual width.
Property window of the String function:
-> The property window has it's usual width.
Property window with "string" property and a large rgbmatrix:
-> The property window width is limited by the size of the rgbmatrix.
Property window with "string" property and a small rgbmatrix:
-> The property window width is limited by the direction control UI under the rgbmatrix.
Windows 10, QLC+ 4.12.8 from GitHub DMX USB & Velleman are disabled