Frank Osterfeld
Frank Osterfeld
Instead of remembering locally which timesheets have been submitted (which fails when more than one installation is used), retrieve the information from lotsofcake directly, using its REST API.
For some settings, QSettings is used, some settings are stored in the Charm.db directly ("metadata"). What's where doesn't always seem to make sense. The Bill Lumbergh reminder option for example...
So far we stuck to Qt4 on Linux because Qt5 had issues on Linux desktops, especially when it comes to window management/systray integration (misplaced icon on Unity, for example). We...
Lotsofcake now has API for retrieving the timesheet upload status (see LOCA-185 in KDAB Jira). This could replace the local storing of uploaded timesheets, for the Bill Lumbergh dialog. The...
It would be nice to have a simple QtQuick example demoing QtKeychain for iOS and Android.
Nicolas: "We may want to simplify [the installation/deployment] a bit, and create a sort of Qt module, with make install putting everything in the Qt directory."
### What happened? When I create a minimal test case with a gr::flowgraph and blocks, the blocks and parts of the runtime (it seems at least the nbt_scheduler, thread_wrapper, runtime_monitor,...
source data changes, in particular for roles other than the sort role, are not forwarded (SortProxyModel::handleDataChanged), thus having a SortProxyModel in the stack makes you "lose" updates. In a customer...
Currently, Block has a `init()` function taking arguments, that is called by `addBlock/emplaceBlock`, and triggers the state machine going from IDLE to INITIALISED state. At the same time, `lifecycle::StateMachine` is...
When used with ProducerType::Multi, gr::CircularBuffer has some threading bugs that causes data to be read that has not been published yet by its writer. That's because in the current implementation,...