Q Light Controller

Ah.. sorry. There's a really simple solution to that, though.
I already put it in cvs, but haven't yet released it.

Go to around line 197 in main/src/pluginmanager.cpp and under:
        QString id;
write:
        id.setNum(KPluginID);

and then substitute this line (just a few lines lower):
        inputParent->setText(KColumnID, KPluginID);
with:
        inputParent->setText(KColumnID, id);

and (again a few lines down):
        outputParent->setText(KColumnID, KPluginID);
with:
        outputParent->setText(KColumnID, id);

And that's it. I'll modify the release in a few days, so if you feel
that these instructions are too difficult, you'll have to wait a while.

+H

----- Original Message -----
From: Andrew Stringer <andrew@...>
Date: Tuesday, November 28, 2006 14:20
Subject: [Qlc-devel] Compile time errors
To: qlc-devel@...

> Hello, I have been looking at qlight the last few days and I am 
> getting an
> error at the compile time running make. This is wwith the 
> latest, just
> released 2.6 version:-
> 
> if g++ -DHAVE_CONFIG_H -I. -I. -I.. -DQT_SHARED -DQT_NO_DEBUG
> -DQT_THREAD_SUPPORT -D_REENTRANT
> -DFIXTURES=\"/usr/local/share/fixtures\"
> -DPIXMAPS=\"/usr/local/share/pixmaps/qlc\"
> -DDOCUMENTS=\"/usr/local/share/doc/qlc\"
> -DPLUGINS=\"/usr/local/lib/qlc\" -DVERSION=\"2.6.0\" -
> I../libs    -g
> -O2 -MT pluginmanager.o -MD -MP -MF ".deps/pluginmanager.Tpo" -c 
> -o
> pluginmanager.o `test -f 'src/pluginmanager.cpp' || echo
> './'`src/pluginmanager.cpp; \
> then mv -f ".deps/pluginmanager.Tpo" ".deps/pluginmanager.Po"; else
> rm -f ".deps/pluginmanager.Tpo"; exit 1; fi
> src/pluginmanager.cpp: In member function `void
> PluginManager::fillPlugins()':
> src/pluginmanager.cpp:197: error: invalid conversion from `short
> unsigned int'
>    to `const char*'
> src/pluginmanager.cpp:197: error:   initializing 
> argument 1 of `
>    QString::QString(const char*)'
> src/pluginmanager.cpp:203: error: invalid conversion from `short
> unsigned int'
>    to `const char*'
> src/pluginmanager.cpp:203: error:   initializing 
> argument 1 of `
>    QString::QString(const char*)'
> make[2]: *** [pluginmanager.o] Error 1
> make[2]: Leaving directory `/home/qlight/qlc2/main'
> make[1]: *** [all-recursive] Error 1
> make[1]: Leaving directory `/home/qlight/qlc2'
> make: *** [all] Error 2
> [root@...] /home/qlight/qlc2 ->
> 
> As far as I can see, I have the requreid prerequisites on the 
> system, but
> my knowledge of C is not sufficient to track this error down.
> 
> I am using Slackware 10.2 on a p3 system with 256M mem.
> I have the dmx4linux v2.5 module loaded with the dummy driver at 
> present.
> Regards,
> Andrew
> 
> 
> -- 
> "If the SOFTWARE is not accompanied by HARDWARE, you may not use the
> SOFTWARE."
>  Win eXPerimental EULA.  Really....?
> 
> 
> 
> -----------------------------------------------------------------
> --------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance 
> to share your
> opinions on IT & business topics through brief surveys - and 
> earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Qlc-devel mailing list
> Qlc-devel@...
> https://lists.sourceforge.net/lists/listinfo/qlc-devel
> 

--
Heikki Junnila

Hello Heikki, thanks for the prompt reply, this has solved it. This
morning I changed plugginmanager.cpp as per you instructions and it
compiled and installed cleanly. Now I just have to learn how to use it :-)

I'm curious about what had to be done, my experience is with Perl not C,
but looking at the error again, am I right in thinking it is to do with
the type a variable has been set to and then used in an inappropriate way?

>src/pluginmanager.cpp:197: error: invalid conversion from `short
> unsigned int'
> to `const char*'


Regards,
Andrew



-- 
"If the SOFTWARE is not accompanied by HARDWARE, you may not use the
SOFTWARE."
 Win eXPerimental EULA.  Really....?

Hi, having built qlc a few days ago I have been playing with the interface
to see how to do things. The intended use for it is to control dmx dimmers
for a fairly conventional amateur dramatic group production.
So far I have defined several dimmer fixtures and allocated dmx channel
numbers to them. In a virtual console I have created faders for each
dimmer channel and a sub master with these allocated to them. According to
the monitor, these work as expected and I can see the dmx values changing
as expected.

1. I am expecting to use some showtec 4 channel dimmers in the real world,
but these are not pre defined in the fixtures. Is there a way to define a
new fixture so it appears in the add section of the device manager?

2. Maybe I am getting confused a new way to do things, but I am having
difficulty getting by head round how to create a sequence of events which
can be played back. I would have expected a scene editor where, for
example, in scene1 the lights required would fade from black up to the
preset levels. Moving to scene2, the lights would change as desired etc.
In function manager, I can add a new scene, but it only applies to one
fixture so if it is a single channel dimmer, I get only one entry in the
scene. If for example, channel 1 & 2 have "scene1", "scene2" & "scene3"
defined, but channel 3 has only  "scene1" & "scene2", how do I tie these
together?  Also in the scene

Maybe I am just missing something here.... but how do I actually play back
a programmed sequence? :-)

Sorry for all the questions, when I understand it, I should write an intro
describing what I did and where I went wrong.

Regards,
Andrew Stringer

-- 
"If the SOFTWARE is not accompanied by HARDWARE, you may not use the
SOFTWARE."
 Win eXPerimental EULA.  Really....?

----- Original Message -----
From: Andrew Stringer <andrew@...>
Date: Friday, December 1, 2006 1:05
Subject: [Qlc-devel] Configuring Scenes & defining new fixtures
To: andrew@..., Development related discussion <qlc-devel@...>
>
> 1. I am expecting to use some showtec 4 channel dimmers in the 
> real world,
> but these are not pre defined in the fixtures. Is there a way to 
> define a
> new fixture so it appears in the add section of the device manager?
> 

Two choices:
1. Since it is a dimmer, you can you any of the predefined four-channel dimmers.
2. Launch qlcfixtureeditor (formerly dce) and create a new fixture definition. Place
   it to /usr/share/fixtures/ or $datadir/fixtures.

> 2. Maybe I am getting confused a new way to do things, but I am having
> difficulty getting by head round how to create a sequence of 
> events which
> can be played back. I would have expected a scene editor where, for
>

You want chasers that contain collections. First, create the scenes you
wish, for each device. Then, create a collection for each combined scene
(i.e. a scene from dimmer one, another from dimmer 2). Then, put these
collections into a chaser and connect the chaser to a virtual console button.

Note that there is a different speed bus for scenes and chasers. Collections
have no speed setting. You can change speed buses from function manager
for each function or more at a time.

> Maybe I am just missing something here.... but how do I actually 
> play back a programmed sequence? :-)
> 

See above; you assign a chaser to a vc button.

+H


--
Heikki Junnila

----- Original Message -----
From: Andrew Stringer <andrew@...>
Date: Friday, December 1, 2006 8:11
Subject: Re: [Qlc-devel] Compile time errors - Solved
To: qlc-devel@...
> 
> I'm curious about what had to be done, my experience is with 
> Perl not C, but looking at the error again, am I right in thinking
> it is to do with the type a variable has been set to and then
> used in an inappropriate way?
> 

Older QT3 versions don't have an overloaded QString constructor
that would accept an integer, but newer versions do. So, yes, it was
a wrong way to use the variable. But don't mix the code to C as this
is C++, which is very different from C, although there are many
similarities, as well.

+H


--
Heikki Junnila