| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| | |
|
| |
|
|
|
|
| |
canFetchMore returns true once the fetch is complete to allow the
incremental fetch behaviour. When we check for children we really only
want to fetch once though, otherwise we risk fetching over and over.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Instead of a single #define as debug area the new system allows for an
identifier for each debug message with the structure component.area.
The component is a dot separated identifier of the runtime component,
such as the process or the plugin.
The area is the code component, and can be as such defined at
compiletime.
The idea of this system is that it becomes possible to i.e. look at the
output of all messages in the query subsystem of a specific resource
(something that happens in the client process, but in the
resource-specific subcomponent).
The new macros are supposed to be less likely to clash with other names,
hence the new names.
|
| |
|
|
| |
Otherwise we risk calling into already destroyed models.
|
| |
|
|
|
| |
Otherwise a treeview doesn't show the expander until you click on the
item (which triggers fetchMore).
|
| |
|
|
| |
...that was a bit too optimistic, sill happening when running kube.
|
| |
|
|
|
| |
That way we avoid any unnecessary queuing for the sync API,
and enable fine-tuning in the model code at a later stage.
|
| | |
|
| | |
|
| |
|
|
| |
clang-format -i */**{.cpp,.h}
|
| |
|
|
|
|
|
|
| |
We skip values we've already seen and only retrieve the new ones.
This currently only properly works in a non-live query and we don't
give the model any feedback when we can't fetch more data anymore.
However, it generally works and we get the desired effect.
|
| | |
|
| | |
|
| |
|
|
| |
(except for documentation).
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
dummyclient
|
| |
|
|
| |
QVariant doesn't support polymorphism for non-QObject classes.
|
| | |
|
| | |
|
| |
|
|
| |
The fetch state is per parent.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
| |
The QueryRunner object lives for the duration of the query (so just
for the initial query for non-live queries, and for the lifetime of the
result model for live queries).
It's supposed to handle all the threading internally and decouple the
lifetime of the facade.
|
| | |
|
| | |
|
| |
|
|
| |
We're not doing partial fetches yet
|
|
|
I finally figured out how to do that with cpp files.
It requires instantiating the code with all expected classes,
but that's not a big problem since we know all types.
This will hopefully greatly reduce the compiletimes...
|
