Re: [Interest] QtDBus Example to read files from USB
Thanks for your inputs. Is there any way to determine whether dbus service is running or not as the below code doesn't works in the latest Qt5.3 on Yocto? Thanks and Regards, Ramakanth -Original Message- From: interest-bounces+ramakanthreddy.kesireddy=techmahindra@qt-project.org [mailto:interest-bounces+ramakanthreddy.kesireddy=techmahindra@qt-project.org] On Behalf Of Thiago Macieira Sent: Thursday, August 21, 2014 7:59 PM To: interest@qt-project.org Subject: Re: [Interest] QtDBus Example to read files from USB On Thursday 21 August 2014 10:51:45 Ramakanthreddy Kesireddy wrote: Is it recommened to fetch the file system paths like below once device is connected or any other API to fetch the filesystem path? Here path is device mounted path like /org/freedesktop/UDisks/devices/sda1. QDBusMessage message = QDBusMessage::createMethodCall(org.freedesktop.UDisks, path, org.freedesktop.DBus.Properties, Get); QDBusMessage response = QDBusConnection::systemBus().call(message); The QtDBus call sequence looks correct. There are other ways to do it, but this is the simplest and most efficient way possible. Whether the call itself is correct, I wouldn't know. Please ask that of the UDisks developers and community. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Android activities navigation.
Hi, I just starting to develop android apps with Qt and I face a problem. In the android way an application could containt several activities representing content allowing us to give the correct structure to an application. Each activity can switch to another using a stack and the back button( hardware/software) of the device pop from the activities stack. When we make a Qt application and prepare it for run in android it creates only one activity and no matters how much overlaped widgets have my application if I press the back button hides the entire application. I thinking on decompose the application on several activities but I don't know how to do that. Sory for my english, Im' spanish speaking. Thanks. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QtDBus Example to read files from USB
On Wednesday 29 October 2014 11:02:30 Ramakanthreddy Kesireddy wrote: Is there any way to determine whether dbus service is running or not as the below code doesn't works in the latest Qt5.3 on Yocto? Make the call and check if the reply was an error one indicating that the service doesn't exist. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Syntax error compiling 5.3.2
It doesn’t.. My customers, to say the least, are EXTREMELY reluctant to change the gcc. Since any other applications that depend on it, would also need to be updated. Shipped in their words, means “default shipped” or updated automatically. Not a “optional, kind of required package”. Scott From: Keith Gardner [mailto:kreios4...@gmail.com] Sent: Wednesday, October 29, 2014 10:27 AM To: Scott Aron Bloom Cc: interest@qt-project.org Subject: Re: [Interest] Syntax error compiling 5.3.2 I know that gcc 4.4 is also available for CentOS 5.8 through yum. Could you update to this version? It still fulfills the requirement of being shipped with the OS. On Wed, Oct 29, 2014 at 12:22 PM, Scott Aron Bloom scott.bl...@onshorecs.commailto:scott.bl...@onshorecs.com wrote: fontdatabases/fontconfig/qtfontconfigdatabase.cpp:94: error: ‘FC_WEIGHT_ULTRABLACK’ was not declared in this scope I cant find anything on this on google. Compiling for centos 5.8 64bit, gcc 4.1.2 Im somewhat stuck by customer demands, that I stick with the GCC version that the OS ships with… Any help would be appreciated. Scott ___ Interest mailing list Interest@qt-project.orgmailto:Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Syntax error compiling 5.3.2
On Wednesday 29 October 2014 17:22:22 Scott Aron Bloom wrote: fontdatabases/fontconfig/qtfontconfigdatabase.cpp:94: error: 'FC_WEIGHT_ULTRABLACK' was not declared in this scope I cant find anything on this on google. Compiling for centos 5.8 64bit, gcc 4.1.2 Im somewhat stuck by customer demands, that I stick with the GCC version that the OS ships with... The problem is not GCC, even though that's going to be a problem later. Update your FontConfig packages. FC_WEIGHT_ULTRABLACK was added to FontConfig 2.5, which was released almost 7 years ago. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Syntax error compiling 5.3.2
Thanks... -Original Message- From: interest-bounces+scott.bloom=onshorecs@qt-project.org [mailto:interest-bounces+scott.bloom=onshorecs@qt-project.org] On Behalf Of Thiago Macieira Sent: Wednesday, October 29, 2014 11:18 AM To: interest@qt-project.org Subject: Re: [Interest] Syntax error compiling 5.3.2 On Wednesday 29 October 2014 17:22:22 Scott Aron Bloom wrote: fontdatabases/fontconfig/qtfontconfigdatabase.cpp:94: error: 'FC_WEIGHT_ULTRABLACK' was not declared in this scope I cant find anything on this on google. Compiling for centos 5.8 64bit, gcc 4.1.2 Im somewhat stuck by customer demands, that I stick with the GCC version that the OS ships with... The problem is not GCC, even though that's going to be a problem later. Update your FontConfig packages. FC_WEIGHT_ULTRABLACK was added to FontConfig 2.5, which was released almost 7 years ago. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
[Interest] Crash in QSerialPort when closing?
I'm getting a weird issue where I can repeatedly cause a crash to happen in QSerialPort if I attempt to close the serial port when I'm in a slot connected to the readyRead() signal, and I'm just wondering if I'm doing something weird. I've got a class that inherits from QSerialPort. I instantiate this object in the UI thread but immediately move it to a separate thread. This object has a slot, disconnectFromDevice(), that sends a reset command to the serial device. So the way I intended the software to work is the user clicks the disconnect button in the UI thread, which sends a signal to the serial port object. That object sends the reset command to the serial device and the serial device responds with an acknowledge response. The acknowledge response triggers the QSerialPort::readyRead() signal, which triggers my readyRead() slot. I parse the acknowledge, then emit a signal back to the UI thread letting the UI know that the disconnect was successful, and then call QSerialPort::close() in the serial port object (still inside of my readyRead() slot). When I execute setup in a debug build, at this point the application crashes with a SIGSEV. For some reason it kicks me into the disassembler instead of breaking in my code. If I comment out the close() call, the segfault doesn't happen. Below is what's shown in the call stack, but since none of my code is shown in the call stack, I don't know if I'm crashing on the close() call itself, or if I crash sometime later because I'm doing something when the port isn't open. If I set a breakpoint anywhere in my readyRead() slot the crash DOESN'T occur. I only know that removing the close() call removes the crash. Any ideas? Specifically, why am I not seeing any of my calls in the call stack? Sean 0 ReadOverlappedCompletionNotifier::processCompletionRoutine qserialport_win.cpp 188 0x6704e8ed 1 AbstractOverlappedEventNotifier::event qserialport_win.cpp 119 0x6704e6d2 2 QApplicationPrivate::notify_helper qapplication.cpp 3467 0xa9ede0f 3 QApplication::notify qapplication.cpp 2888 0xa9eb72b 4 QCoreApplication::notifyInternal qcoreapplication.cpp 878 0x6b91b572 5 QCoreApplication::sendEventqcoreapplication.h 232 0x6b9bee2b 6 QEventDispatcherWin32Private::activateEventNotifier qeventdispatcher_win.cpp 335 0x6b9646e8 7 QEventDispatcherWin32::processEvents qeventdispatcher_win.cpp 759 0x6b965de7 8 QEventLoop::processEvents qeventloop.cpp 136 0x6b919650 9 QEventLoop::exec qeventloop.cpp212 0x6b9198eb 10 QThread::exec qthread.cpp 509 0x6b794f85 11 QThread::run qthread.cpp 576 0x6b7950ed 12 QThreadPrivate::startqthread_win.cpp 347 0x6b797ac2 13 msvcrt!_itow_sC:\windows\syswow64\msvcrt.dll 0x775d1287 14 msvcrt!_endthreadex C:\windows\syswow64\msvcrt.dll 0x775d1328 15 KERNEL32!BaseCleanupAppcompatCacheSupport C:\windows\syswow64\kernel32.dll 0x7594338a 16 ?? 0x16d0ffd4 17 ntdll!RtlpNtSetValueKey C:\windows\system32\ntdll.dll 0x77c19f72 18 ?? 0x166b7660 19 ntdll!RtlpNtSetValueKey C:\windows\system32\ntdll.dll 0x77c19f45 20 msvcrt!_endthreadex C:\windows\syswow64\msvcrt.dll 0x775d12e5 21 ?? ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Position y() of widget inside Layout
Hi.
Look at this small example. It’s not fully functional but as example it’s good
enough, I hope...
From: Jean Richard Lima
Sent: Wednesday, October 29, 2014 8:34 PM
To: Interest@qt-project.org
Subject: [Interest] Position y() of widget inside Layout
Hello!
How can I get the y () position of a widget inside another?
I have 3 widgets within another widget when and try: geometry()-y() it returns
me is always 0 when applied to the layout, if he gives me shot, but I need the
layout and position, as I am dragging one over the other to switch places.
Thank you.
Jean Richard Lima
Consultor de Gestão e TIC
Software House de Projetos Específicos
___
Interest mailing list
Interest@qt-project.org
http://lists.qt-project.org/mailman/listinfo/interest
#include QWidget
#include QPainter
#include QHBoxLayout
#include QApplication
#include QMouseEvent
class Widget
: public QWidget
{
public:
explicit Widget( const QColor color, QWidget * parent = 0 )
: QWidget( parent )
, m_color( color )
{}
QSize sizeHint() const
{
return QSize( 100, 75 );
}
protected:
void paintEvent( QPaintEvent * )
{
QPainter p( this );
p.setBrush( m_color );
p.drawRect( rect() );
}
private:
QColor m_color;
};
class Stack
: public QWidget
{
public:
Stack()
: m_layout( 0 )
, m_clicked( false )
, m_deltaX( 0 )
, m_deltaY( 0 )
{
m_layout = new QHBoxLayout( this );
Widget * w1 = new Widget( Qt::red, this );
m_layout-addWidget( w1 );
Widget * w2 = new Widget( Qt::green, this );
m_layout-addWidget( w2 );
Widget * w3 = new Widget( Qt::blue, this );
m_layout-addWidget( w3 );
setLayout( m_layout );
resize( 350, 100 );
}
protected:
void mousePressEvent( QMouseEvent * e )
{
if( e-button() == Qt::LeftButton )
{
m_clicked = true;
m_pos = e-pos();
}
e-accept();
}
void mouseMoveEvent( QMouseEvent * e )
{
if( m_clicked )
{
const QPoint pos = e-pos();
int index = -1;
QLayoutItem * item = findLayoutItem( pos, index );
if( item index = 0 )
{
const QRect r = item-geometry();
if( item-widget() )
item-widget()-raise();
const int deltaX = pos.x() - m_pos.x();
const int deltaY = pos.y() - m_pos.y();
m_deltaX += deltaX;
m_deltaY += deltaY;
if( qAbs( m_deltaX ) = r.width() / 2 )
{
if( m_deltaX 0 )
{
if( index m_layout-count() -
1 )
{
item =
m_layout-takeAt( index );
m_layout-insertItem(
index + 1, item );
m_deltaX = 0;
m_deltaY = 0;
}
}
else
{
if( index 0 )
{
item =
m_layout-takeAt( index );
m_layout-insertItem(
index - 1, item );
m_deltaX = 0;
m_deltaY = 0;
}
}
}
else
item-setGeometry( QRect( r.x() +
deltaX,
r.y() + deltaY, r.width(),
r.height() ) );
}
m_pos = pos;
Re: [Interest] Crash in QSerialPort when closing?
Your version of QtSerialPort is too very old (according to call-stack). Please update to latest (e.g. to 5.3.2/5.3.3). I'll try to upgrade then. If that's all it is, that'd be great! Sean I’m getting a weird issue where I can repeatedly cause a crash to happen in QSerialPort if I attempt to close the serial port when I’m in a slot connected to the readyRead() signal, and I’m just wondering if I’m doing something weird. I’ve got a class that inherits from QSerialPort. I instantiate this object in the UI thread but immediately move it to a separate thread. This object has a slot, disconnectFromDevice(), that sends a reset command to the serial device. So the way I intended the software to work is the user clicks the disconnect button in the UI thread, which sends a signal to the serial port object. That object sends the reset command to the serial device and the serial device responds with an acknowledge response. The acknowledge response triggers the QSerialPort::readyRead() signal, which triggers my readyRead() slot. I parse the acknowledge, then emit a signal back to the UI thread letting the UI know that the disconnect was successful, and then call QSerialPort::close() in the serial port object (still inside of my readyRead() slot). When I execute setup in a debug build, at this point the application crashes with a SIGSEV. For some reason it kicks me into the disassembler instead of breaking in my code. If I comment out the close() call, the segfault doesn’t happen. Below is what’s shown in the call stack, but since none of my code is shown in the call stack, I don’t know if I’m crashing on the close() call itself, or if I crash sometime later because I’m doing something when the port isn’t open. If I set a breakpoint anywhere in my readyRead() slot the crash DOESN’T occur. I only know that removing the close() call removes the crash. Any ideas? Specifically, why am I not seeing any of my calls in the call stack? Sean 0 ReadOverlappedCompletionNotifier::processCompletionRoutine qserialport_win.cpp 188 0x6704e8ed 1 AbstractOverlappedEventNotifier::event qserialport_win.cpp 119 2 QApplicationPrivate::notify_helper qapplication.cpp 3467 0xa9ede0f 3 QApplication::notify qapplication.cpp 2888 0xa9eb72b 4 QCoreApplication::notifyInternal qcoreapplication.cpp 878 0x6b91b572 5 QCoreApplication::sendEvent qcoreapplication.h 232 0x6b9bee2b 6 QEventDispatcherWin32Private::activateEventNotifier qeventdispatcher_win.cpp 335 0x6b9646e8 7 QEventDispatcherWin32::processEvents qeventdispatcher_win.cpp 759 8 QEventLoop::processEvents qeventloop.cpp 136 9 QEventLoop::exec qeventloop.cpp 212 10 QThread::exec qthread.cpp 509 11 QThread::run qthread.cpp 576 12 QThreadPrivate::start qthread_win.cpp 347 13 msvcrt!_itow_s C:\windows\syswow64\msvcrt.dll 14 msvcrt!_endthreadex C:\windows\syswow64\msvcrt.dll 15 KERNEL32!BaseCleanupAppcompatCacheSupport C:\windows\syswow64\kernel32.dll 0x7594338a 16 ?? 17 ntdll!RtlpNtSetValueKey C:\windows\system32\ntdll.dll 18 ?? 19 ntdll!RtlpNtSetValueKey C:\windows\system32\ntdll.dll 20 msvcrt!_endthreadex C:\windows\syswow64\msvcrt.dll 21 ?? ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Crash in QSerialPort when closing?
Your version of QtSerialPort is too very old (according to call-stack). Please update to latest (e.g. to 5.3.2/5.3.3). I'll try to upgrade then. If that's all it is, that'd be great! Looks like that has fixed the problem. Thanks for the help! Sean ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] Crash in QSerialPort when closing?
Hi Sean, Closing a device within a read slot sounds dodgy anyway. In these cases, I usually do QTimer::singleShot(0, ...) and do the close in that slot. Regards, Tony From: interest-bounces+tony=rightsoft.com...@qt-project.org [mailto:interest-bounces+tony=rightsoft.com...@qt-project.org] On Behalf Of Murphy, Sean Sent: Thursday, 30 October 2014 5:36 AM To: interest@qt-project.org Subject: [Interest] Crash in QSerialPort when closing? I'm getting a weird issue where I can repeatedly cause a crash to happen in QSerialPort if I attempt to close the serial port when I'm in a slot connected to the readyRead() signal, and I'm just wondering if I'm doing something weird. I've got a class that inherits from QSerialPort. I instantiate this object in the UI thread but immediately move it to a separate thread. This object has a slot, disconnectFromDevice(), that sends a reset command to the serial device. So the way I intended the software to work is the user clicks the disconnect button in the UI thread, which sends a signal to the serial port object. That object sends the reset command to the serial device and the serial device responds with an acknowledge response. The acknowledge response triggers the QSerialPort::readyRead() signal, which triggers my readyRead() slot. I parse the acknowledge, then emit a signal back to the UI thread letting the UI know that the disconnect was successful, and then call QSerialPort::close() in the serial port object (still inside of my readyRead() slot). When I execute setup in a debug build, at this point the application crashes with a SIGSEV. For some reason it kicks me into the disassembler instead of breaking in my code. If I comment out the close() call, the segfault doesn't happen. Below is what's shown in the call stack, but since none of my code is shown in the call stack, I don't know if I'm crashing on the close() call itself, or if I crash sometime later because I'm doing something when the port isn't open. If I set a breakpoint anywhere in my readyRead() slot the crash DOESN'T occur. I only know that removing the close() call removes the crash. Any ideas? Specifically, why am I not seeing any of my calls in the call stack? Sean 0 ReadOverlappedCompletionNotifier::processCompletionRoutine qserialport_win.cpp 188 0x6704e8ed 1 AbstractOverlappedEventNotifier::event qserialport_win.cpp 119 0x6704e6d2 2 QApplicationPrivate::notify_helper qapplication.cpp 3467 0xa9ede0f 3 QApplication::notify qapplication.cpp 2888 0xa9eb72b 4 QCoreApplication::notifyInternal qcoreapplication.cpp 878 0x6b91b572 5 QCoreApplication::sendEventqcoreapplication.h 232 0x6b9bee2b 6 QEventDispatcherWin32Private::activateEventNotifier qeventdispatcher_win.cpp 335 0x6b9646e8 7 QEventDispatcherWin32::processEvents qeventdispatcher_win.cpp 759 0x6b965de7 8 QEventLoop::processEvents qeventloop.cpp 136 0x6b919650 9 QEventLoop::exec qeventloop.cpp212 0x6b9198eb 10 QThread::exec qthread.cpp 509 0x6b794f85 11 QThread::run qthread.cpp 576 0x6b7950ed 12 QThreadPrivate::startqthread_win.cpp 347 0x6b797ac2 13 msvcrt!_itow_sC:\windows\syswow64\msvcrt.dll 0x775d1287 14 msvcrt!_endthreadex C:\windows\syswow64\msvcrt.dll 0x775d1328 15 KERNEL32!BaseCleanupAppcompatCacheSupport C:\windows\syswow64\kernel32.dll 0x7594338a 16 ?? 0x16d0ffd4 17 ntdll!RtlpNtSetValueKey C:\windows\system32\ntdll.dll 0x77c19f72 18 ?? 0x166b7660 19 ntdll!RtlpNtSetValueKey C:\windows\system32\ntdll.dll 0x77c19f45 20 msvcrt!_endthreadex C:\windows\syswow64\msvcrt.dll 0x775d12e5 21 ?? ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QtDBus Example to read files from USB
Yes there is an error to indicate service doesn't exist. response is: QDBusMessage(type=Error, service=, error name=org.freedesktop.DBus.Error.ServiceUnknown, error message=The name org.freedesktop.UDisks was not provided by any .service files, signature=, contents=() ) Please let me know how can we ensure that service exists and is running. Do we need to install any package? Thanks and Regards, Ramakanth -Original Message- From: interest-bounces+ramakanthreddy_kesireddy=mahindrasatyam@qt-project.org [mailto:interest-bounces+ramakanthreddy_kesireddy=mahindrasatyam@qt-project.org] On Behalf Of Thiago Macieira Sent: Wednesday, October 29, 2014 9:49 PM To: interest@qt-project.org Subject: Re: [Interest] QtDBus Example to read files from USB On Wednesday 29 October 2014 11:02:30 Ramakanthreddy Kesireddy wrote: Is there any way to determine whether dbus service is running or not as the below code doesn't works in the latest Qt5.3 on Yocto? Make the call and check if the reply was an error one indicating that the service doesn't exist. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest Disclaimer: This message and the information contained herein is proprietary and confidential and subject to the Tech Mahindra policy statement, you may review the policy at http://www.techmahindra.com/Disclaimer.html externally http://tim.techmahindra.com/tim/disclaimer.html internally within TechMahindra. ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
Re: [Interest] QtDBus Example to read files from USB
On Thursday 30 October 2014 04:55:19 Ramakanthreddy Kesireddy wrote: Yes there is an error to indicate service doesn't exist. response is: QDBusMessage(type=Error, service=, error name=org.freedesktop.DBus.Error.ServiceUnknown, error message=The name org.freedesktop.UDisks was not provided by any .service files, signature=, contents=() ) Please let me know how can we ensure that service exists and is running. Do we need to install any package? Yes, install the package that provides UDisks and ensure that your system starts it. How to do that, exactly, is not a Qt question. Please consult the documentation of your Linux distribution. Since you said you're using Yocto, make sure that you included udisks in your recipe. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Interest mailing list Interest@qt-project.org http://lists.qt-project.org/mailman/listinfo/interest
