the notifications are popping up almost instantly ( despite me providing time for it ).
you pass the time you want it to be triggered from now on. The API expects a time since EPOCH (as your comment in the code also states) which are the milliseconds from 1970/01/01 on.
So in your JAVA code add new Date().getTime() milliseconds to your current timeout.
So far i am able to get the notifications ( but not on Android O )
did you read this already?
Alos chekc the Qt debugger console and/or LogCat for suspicious messages regarding notifications.
I'm working with uinput to simulate a touch driver using embedded linux on sama board.
I set TSLIB_TSDEVICE=/dev/input/event0, but QT seems not working.
I can see event by cat /dev/input/event0 but application doesn't get any.
My question is: why do you have a release event?
My code is
Ok, I have a mistake, in descriptorwitten signal I checked it new value, and if it is 0000, I disconnect from device.
But I checked the 1 index byte (the second), not the 0 index byte (first), and the second is always zero.
This is my byte order mistake.
I'm a a bit late to the party, but I was having the exact same issue and just spent few hours working this out.
Running Qt Creator 4.7.1
What you probably figured out is that gdb fails to load the debug symbols. First tricky thing, Qt Creator doesn't raise any error about it, you have to dig down the gdb logs:
dINFERIOR STARTUP: BINARY NOT FOUND
sReading debug information failed:
s/home/flr03/Workspace/ethan-qt-epg-app/build-epg-ui-EPG_Android_for_armeabi_v7a_GCC_4_9_Qt_5_10_1_5_10_1_AndroidQt-Debug/app_process: No such file or directory.
So from this, I checked if the deploy step does its job properly, second surprise Qt Creator tries indeed to pull app_process but doesn't complain about anything, however the file is not pulled properly (others needed files seem to be pulled properly though).
As I can pull manually app_process from the terminal with adb, I work around the issue by adding a custom deploy step (Project/Run settings) doing that for me. Et voilà.
Hope maybe this can help someone else being blocked with the same issue.
So the only way to do that would be to modify Qt Charts.
From my point of view, this is pretty much futile as it'd mean hacking at the Qt's sources. QtCharts does not provide for means to extend or modify the behavior, drawing or even adding chart types. Everything is buried in the private classes and the only thing one could override is a couple of setters.
I meant that you would need to modify the sources directly, not by subclassing. I agree the only way is to override a couple of setters. Thinking about it, in theory, it might be possible to try and get access to the item used directly (since it likely a QGraphicsItem) so you might be able to call setBrush() on it directly. But I didn't mean that you can do this by subclassing at least, Qt Charts does not provide a means in that regard.