Yes, you're right Emmanuel, nothing more is required but the QCaLabel.
Glad you like the documentation, although I'm sure you will quickly discover it is way shorter than it should be. Or was that your tongue-in-cheek point!
From: email@example.com [firstname.lastname@example.org]
Sent: Friday, 25 March 2011 12:21 PM
To: Andrew Rhyder
Cc: EPICS tech-talk
Subject: Re: epicsqt first try
On 09:31 Tue 22 Mar , Andrew Rhyder wrote:
> There is not much wrong with your code below, but I believe you always need to create widgets like QLabels (our EPICS flavor or otherwise) within a main window widget.
No need of main window
or "how to use Qt" book. ;-)
> Also, the CA connection is not established automatically, you have to call the 'activate()' method once the widget is created.
Ok, that was the missing part
int main(int argc, char *argv)
QApplication a(argc, argv);
> Calling 'activate()' is a minor overhead that I would like to avoid for simple widgets that could otherwise just 'go' but allows for widgets that take multiple PVs and then require macro substitution to be applied to those PVs.
I love the ASgui utility
The documentation is quite good to get you started (once you find and read it ;)
I would love to see more advanced widgets.
Overall this ca_framework is...
<br>This message and any attachments may contain proprietary or confidential information. If you are not the intended recipient or you received the message in error, you must not use, copy or distribute the message. Please notify the sender immediately and destroy the original message. Thank you.
- epicsqt first try emmanuel_mayssat
- RE: epicsqt first try Andrew Rhyder
- Re: epicsqt first try emmanuel_mayssat
- Navigate by Date:
Re: GPIB DCL Robert Emery
asynPortDriver Question Szalata, Zenon M.
- Navigate by Thread:
Re: epicsqt first try emmanuel_mayssat
Modbus R2-2 available Mark Rivers