El Tuesday 28 July 2015, Thiago Macieira escribió:
https://github.com/osxfuse/fuse/blob/06018fa9d5cee5ee3e8fb7057e568f5bc811
5f5 b/lib/mount_darwin.c#L589
Oh, yeah, that's totally broken.
My earlier recommendation stands then:
Shoot the library in the head.
:-)
Thank you for the
On Wed, Jul 29, 2015 at 8:01 PM, Edward Sutton
edward.sut...@subsite.com wrote:
My Qt widget app has Bluetooth connection that broadcasts GPS NMEA data to a
connected device.
How can I maintain this connection streaming GPS data when app is not in
foreground or device is in sleep?
Is it
On Jul 30, 2015, at 7:27 AM, Stanislav Baiduzhyi baiduzhyi.de...@gmail.com
wrote:
On Thu, Jul 30, 2015 at 2:24 PM, Edward Sutton
edward.sut...@subsite.com wrote:
I was hoping I could use the QBluetoothSocket connection.
However it sounds like a background service that does the Bluetooth
I was hoping I could use the QBluetoothSocket connection.
However it sounds like a background service that does the Bluetooth
communications must be pure java? No Qt, no C++.
-Ed
On Jul 30, 2015, at 6:53 AM, Stanislav Baiduzhyi
baiduzhyi.de...@gmail.commailto:baiduzhyi.de...@gmail.com
And my question is just theoretical: is this approach good or such
sleep() implementation not so good and why? I.e. will such sleep()
release processor's time for another thread or not?
Using sleep() will allow the processor to work on a different thread. The
issue is that sleep() will most
On Thursday 30 July 2015 13:00:57 m...@rpzdesign.com wrote:
Thiago:
I kind of messed up.
You once replied with the location on github or somewhere where the
binary build commands for configure on the product releases was located.
OSX
./configure bla-bla-bla
When I search back
On 28.07.2015 18:35, Thiago Macieira wrote:
On Tuesday 28 July 2015 10:36:11 Alejandro Exojo wrote:
I probably wasn't clear enough: this is on a Mac, so I should have written
OSXFUSE instead of FUSE. The library is still based in Linux's, but current
stable OSXFUSE uses an old libfuse. And
Hello List:
Yosemite 10.10.2 - Xcode 6.1.1 (also on Xcode 6.2) - Qt 5.5.0
Trying to run on the IOS simulator and get a big fail. The simulator
starts up but then the applicaiton output gets
the following message on a basic project.
Anybody come across this?
Debugging starts
Session could
On Friday 31 July 2015 00:45:38 Frank Mertens wrote:
One thing I'm wondering with all the SIGCHLD magic. How you make sure the
signal handlers do not mess around and spread EINTR in your third-party
components. And I'm not just worried about Qt's 3rd party libs.
You don't. You simply hope that
Hello List IOS Maintainer Tor Arne: (tor.arne.ves...@theqtcompany.com)
I would like to suggest some hard lessons learned today.
I upgraded to 5.5.0 and was primarily getting my code running on OSX to
make sure it basically worked. I could then deploy to IOS Simulator/IOS
and android to
Thiago:
You were right.
string.h - Correct
For SIGBUS exceptions, I had some structure members that did NOT
end on even 4 byte boundaries.
I had to specifically set some memory variables to pass on 4 byte
alignments.
Don't yet know why the NDK C++ compiler won't align on byte boundaries
On Thursday 30 July 2015 07:58:15 Carel Combrink wrote:
How does the Linux side know which version to link to, I am assuming this
is then a feature of gcc/make and not qmake?
No, it's really qmake. It creates symlinks.
When you pass -lXXX, the linker searches for libXXX.so and then libXXX.a.
Igor wrote:
Because in Qt 4 QThread::sleep is protected.
You can unprotect it by deriving your own class from QThread and making
whichever static methods public! As long as you are aware of the pitfalls
(don't sleep in main thread, etc.), and much easier than messing with locks
just to gain
On 29/07/2015 19:51, Nuno Santos wrote:
Hi,
I’m having a serious issue with Android deployment and this is
something recent. I’m starting to think that this was not happening on
previous versions of Qt. I’m currently using Qt 5.4.2 and when I
deploy to Google Play, on some devices the app
On 2015-07-30 01:43, Igor Mironchik wrote:
On 30.07.2015 00:06, Matthew Woehlke wrote:
Why are you doing this? If the intent is just to make the thread sleep,
why not use QThread::msleep?
Because in Qt 4 QThread::sleep is protected.
You failed to mention that you are using Qt 4.x :-).
If
Thiago:
I kind of messed up.
You once replied with the location on github or somewhere where the
binary build commands for configure on the product releases was located.
OSX
./configure bla-bla-bla
When I search back through all my past emails, I could NOT find that
kind message you
Before I had the support-screens directive, then I have changed to compatible
screens, and I think the problem started there. Before I also had the required
min dpi attribute on support-screens and now I have completely removed it. So,
I ended with this only:
supports-screens
Hi,
On 30.07.2015 11:31, Tony Rietwyk wrote:
Igor wrote:
Because in Qt 4 QThread::sleep is protected.
You can unprotect it by deriving your own class from QThread and making
whichever static methods public! As long as you are aware of the pitfalls
(don't sleep in main thread, etc.), and
Harri,
Yesterday, I have finally managed to solve the problem with the help of a user.
One of the biggest issues was the misleading information provided by Google
Play Developer support about the unsupported platforms.
The problem was actually derived from the support-screens. My last try was:
Hi Nuno,
Sorry, I didn't get what you changed to make it work.
Could you explain?
Em qui, 30 de jul de 2015 às 10:58, Nuno Santos nunosan...@imaginando.pt
escreveu:
Harri,
Yesterday, I have finally managed to solve the problem with the help of a
user.
One of the biggest issues was the
20 matches
Mail list logo
