A few tings i noticed

Report an issue that you found while using QLC+ 5.x.
Please provide as many details as you can, a sample workspace if available and don't forget to read the forum posting guidelines first !
Post Reply
Chris De Rock
Posts: 103
Joined: Tue Apr 14, 2015 6:54 am
Real Name:

Just found some issues that could be better (IMHO):
* when you are in the 3d view and use the mousewheel to modify values... if you are at the end of the range of a value the scroll-information goes direct to the view and zooms in or out. i didnt expect that behavior cause my focus is on the value
* linked fixtures are a great idea but they dont show up in the information window (power consumption, weight, etc.)
* another thing i see by testing the new features.. i dont know if this is what you want.. if you set a fixture to invisible the fixture will be hidden but the light from that fixture is still visible

yust see me as a heavy (and happy) tester ;)
Top
User avatar
mcallegari
Posts: 4710
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:
Contact mcallegari

#1 was a Qt issue, already resolved in 5.11.x: https://bugreports.qt.io/browse/QTBUG-66044

I'll have a look at the rest, thanks
Top
Chris De Rock
Posts: 103
Joined: Tue Apr 14, 2015 6:54 am
Real Name:

Ok, now i found the option to load custom items like your trussing. Sometimes the loading of such objects causes a segfault (i try to reproduce this to send you a better report). And for the future it would be great to have a list of current used objects.
PS: the position of the custom objects is not saved yet
PPS: found something..
by looking in the file i saved with the custom meshes i see the position is stored correctly. By loading the file and switching to the 3d view the app crashes with the following output:
--SNIP--
2018-07-19 10:33:54.380694+0200 qlcplus-qml[22573:4588582] Refreshing 3D view...
2018-07-19 10:33:54.380740+0200 qlcplus-qml[22573:4588582] File URL is: "/Users/chritoep/QLC+.app/Contents/Resources/Meshes/stage/truss_triangle_2m.obj"
error: mainview3d.o DWARF DW_TAG_array_type DIE at 0x00018780 has a class/union/struct element type DIE 0x0001878c that is a forward declaration, not a complete definition.
Try compiling the source file with -fno-limit-debug-info or disable -gmodule
Process 22573 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x301500004)
frame #0: 0x000000010009ccb0 qlcplus-qml`MainView3D::createGenericItem(this=0x0000000102cb7160, filename=QString @ 0x00007ffeefbfd7e0) at mainview3d.cpp:1170
1167 mesh->m_rootTransform = NULL;
1168 mesh->m_selectionBox = NULL;
1169
-> 1170 QEntity *newItem = qobject_cast<QEntity *>(m_genericComponent->create());
1171 newItem->setParent(m_sceneRootEntity);
1172
1173 newItem->setProperty("itemID", m_latestGenericID);
Target 0: (qlcplus-qml) stopped.
--SNIP--
Environment is MacPro5.1 with OSX 10.13.6 and QT 5.11.0. QLC+ direct from git with your latest commits
Top
User avatar
mcallegari
Posts: 4710
Joined: Sun Apr 12, 2015 9:09 am
Location: Italy
Real Name: Massimo Callegari
Contact:
Contact mcallegari

Chris, once again, and I hope for the last time, can you please stop reporting issues one minute after I push something on GIT ?

Also, this is the wrong place as "QLC+ 5 issue reports" is meant to be for RELEASED versions.
The "Software development" section is the one for DEVELOPMENT issues.

But again, is not nice for me to have someone chasing after you (even in the Qt tracking site) every minute after a change on Github.
PLEASE BE PATIENT

BTW. the above looks like a build issue on your end
Top
Post Reply

Return to “QLC+ 5 Issue reports”