Page 1 of 2
Web Output Issue
Posted: Tue Feb 18, 2014 9:48 am
by Chris Moses
Hi Massimo,
There seems to be a CSS/styling issue in the output of the web interface in QLC+. The frames don't have "position: absolute;" applied to them in CSS, so they all appear on top of one another in the top-left of the browser window. I use many frames in my virtual console, with buttons and sliders inside each.
"position: absolute;" should be on all the elements really except the parent one, which correctly has "position: relative;" on it. Can this be updated for the next release?
Which source code file would I need to change to affect the web output, if I wanted to build from source?
Cheers,
Chris
Web Output Issue
Posted: Tue Feb 18, 2014 10:08 am
by Massimo Callegari
Hi Chris, can you please share your workspace ?
Maybe a screenshot would help too
Web Output Issue
Posted: Tue Feb 18, 2014 10:28 am
by Chris Moses
Sure. Here are two screen shots - one showing the layout in QLC+ and one showing the layout in the browser. You can see how all the elements sit on top of one another in the top-left.
Cheers,
Chris
Web Output Issue
Posted: Tue Feb 18, 2014 10:29 am
by Chris Moses
Sure. Here are two screen shots - one showing the layout in QLC+ and one showing the layout in the browser. You can see how all the elements sit on top of one another in the top-left.
Cheers,
Chris
Web Output Issue
Posted: Tue Feb 18, 2014 1:46 pm
by Massimo Callegari
Hi, thanks.
Would you mind to share the project too ?
I am pretty sure I tested multiple frames. The only thing I see in your VC is that you don't enable frames headers. Maybe that's the problem
Web Output Issue
Posted: Tue Feb 18, 2014 8:21 pm
by Massimo Callegari
Nevermind, found and fixed !
Thanks for spotting it out
Web Output Issue
Posted: Tue Feb 18, 2014 8:27 pm
by Massimo Callegari
Hey, would you mind if I use your VC screenshot in the QLC+ website ?
I like how it looks and it can give to new users a solid impression of what is possible to achieve
Web Output Issue
Posted: Tue Feb 18, 2014 10:50 pm
by Chris Moses
Sure yep, you can use the screenshot of the workspace
How do I get the updated/fixed release? I tried building the source on my Mac but it won't compile. I just keep getting..
Project ERROR: portaudio-2.0 development package not found
...but it is installed...
pkg-config --list-all | grep portaudio
portaudiocpp PortAudioCpp - Portable audio I/O C++ bindings
portaudio-2.0 PortAudio - Portable audio I/O
Any ideas?
Web Output Issue
Posted: Tue Feb 18, 2014 10:51 pm
by Chris Moses
I have followed your instructions for building on a Mac - the only package that won't install or build is OLA.
Web Output Issue
Posted: Tue Feb 18, 2014 11:05 pm
by Massimo Callegari
Hi, have you tried today to compile or before yesterday ?
Cause last night I've done some changes to build on Qt5 (still broken though) and portaudio is one of those things I touched
Web Output Issue
Posted: Tue Feb 18, 2014 11:25 pm
by Chris Moses
OK, I just tried it again and made sure the PKG_CONFIG_PATH was set and now it doesn't mention "portaudio" but I do get this error...
Undefined symbols for architecture x86_64:
"ola::StringTrim(std::string*)", referenced from:
ola::QLCLogDestination::Write(ola::log_level, std::string const&) in qlclogdestination.o
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
...I downloaded your latest source from GIT.
Web Output Issue
Posted: Tue Feb 18, 2014 11:44 pm
by Massimo Callegari
Yesterday I built QLC+ after updating macports and got no error. I think OLA version is 0.8.33 now.
In case you can disable the OLA plugin by commenting (#) it in plugins/plugins.pro
Web Output Issue
Posted: Tue Feb 18, 2014 11:57 pm
by Chris Moses
I built the latest version of OLA this evening from GIT...
http://www.opendmx.net/index.php/OLA_Ma ... l_From_Git
...it built OK. OLA failed to install completely using macports, I forget the error message now, but it was quite convoluted
I'll try and disable OLA now in plugins.pro and see what happens.
Web Output Issue
Posted: Tue Feb 18, 2014 11:58 pm
by Chris Moses
Just to add, I am using Qt 5.2.1 - maybe it's that?
Web Output Issue
Posted: Wed Feb 19, 2014 12:04 am
by Chris Moses
OK, disabling OLA has worked, but now I get...
install_name_tool -id @executable_path/../Frameworks/QtGui.framework/Versions/5/QtGui ~/QLC+.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/install_name_tool: can't open file: /Users/Chris/QLC+.app/Contents/Frameworks/QtGui.framework/Versions/5/QtGui (No such file or directory)
make[1]: *** [install_LIBQTGUI_ID] Error 1
make: *** [sub-macx-install_subtargets-ordered] Error 2
...when I 'make install'.
Web Output Issue
Posted: Wed Feb 19, 2014 12:11 am
by Chris Moses
Well, if I run the QLC.app that I built (even with the error above), it seems to ruin my lovely workspace
See the screenshot below.
Web Output Issue
Posted: Wed Feb 19, 2014 12:11 am
by Massimo Callegari
Yeah, as I said before the qt5 build is still broken on osx.
Please use qt 4.8.5 for now.
Just if you want to try, do
export QTDIR=/path/to/qt5
Before building with qt5
Web Output Issue
Posted: Wed Feb 19, 2014 12:17 am
by Massimo Callegari
I believe that. The Qt5 porting is not complete yet.
I'm afraid it will take a while to find out every thing that is not working there
Web Output Issue
Posted: Wed Feb 19, 2014 5:33 pm
by Chris Moses
Argh! Just tried Qt 4.8.5 and I get this error...
/Library/Frameworks/QtCore.framework/Headers/qglobal.h:331:6: error: "This
version of Mac OS X is unsupported" [-Werror,-W#warnings]
...I am using Mavericks (10.9.1). I guess I'll just have to wait until Qt5 is supported
Web Output Issue
Posted: Wed Feb 19, 2014 6:39 pm
by Chris Moses
OK I managed to hack Qt 4.8.5 to work on Mavericks and I have successfully built the latest version of QLC+
You have "almost" fixed the frame positioning in web output... it seems "solo" frames have the wrong positioning still (see screen shot below). Would you be able to fix those too? Then it would be perfect