| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
Change-Id: Icc6560f9c65e294e01439f17ff02614d6dcf7dc8
Reviewed-by: Karsten Heimrich <karsten.heimrich@nokia.com>
|
|
|
|
|
| |
Change-Id: I694171e531edd5216401dcd99ce3040a1a007604
Reviewed-by: Tim Jenssen <tim.jenssen@nokia.com>
|
|
|
|
|
| |
Change-Id: Iae8c25276707dd245bf8247bc4b71511a29901b0
Reviewed-by: Karsten Heimrich <karsten.heimrich@nokia.com>
|
|
|
|
|
| |
Change-Id: I9888074aa45b5fb4606354826ef3f62c6d7d97c6
Reviewed-by: Niels Weber <niels.2.weber@nokia.com>
|
|
|
|
|
| |
Change-Id: I143694ac2a62e3c0e2be003ffa0f7e37f00351a2
Reviewed-by: Karsten Heimrich <karsten.heimrich@nokia.com>
|
|
|
|
|
|
| |
Change-Id: I66340dbc1f2a5a38ed98d1ad406c22b594d92b6e
Reviewed-by: Alexander Lenhardt <alexander.lenhardt@nokia.com>
Reviewed-by: Karsten Heimrich <karsten.heimrich@nokia.com>
|
|
|
|
|
| |
Change-Id: I012819b8e95aa47d08576765eaeffaef01eeaabf
Reviewed-by: Tim Jenssen <tim.jenssen@nokia.com>
|
|
|
|
|
| |
Change-Id: I9f99ae71e832586432d6fc493a701c5d5d074d6a
Reviewed-by: Tim Jenssen <tim.jenssen@nokia.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The proper fix for 308dc03e would have been to check if we
run in installer mode and only than check default components
initially. Not sure how a1a130b9 could state that the code
would work as expected, as proper testing would have revealed
that the "Next" button now was enabled always enabled in
package manager mode and always disabled in updater mode...
Fixes also the problem seen by Niels that in package manager
case components would have been scheduled for uninstall even
if we just selected a new component without removing an other.
Reviewed-By: Niels Weber
|
|
|
|
| |
Reviewed-by: Maurice
|
|
|
|
| |
Review-by: Maurice Kalinowski
|
|
|
|
| |
Review-by: Maurice Kalinowski
|
|
|
|
|
|
|
|
|
|
| |
Review-by: tjenssen
Do not change the checked state of a component if the state
is already the requested one. Also supress the state if the
component is a tri state component, as the setData call will
force the selection of tri state components. Avoid expensive
setData calls in case nothing changed.
|
| |
|
| |
|
| |
|
|
|
|
| |
Fix includes as well.
|
|
|
|
|
| |
Note: Might break on any other platform than windows,
needs some more tests. No break on windows so far...
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Review-by: tjenssen
Checking/ unchecking a virtual component does not modify
the parent item. Checking/ unchecking a parent item that
owns virtual components does not modify the components
check state. Dependencies to virtual components should
get resolved later, so we do not need to handle them at all.
|
|
|
|
|
| |
We need to update the current selection list to be
able to emit the proper selection changed value.
|
|
|
|
| |
Fixes the wrongly enabled "Next" on component selection.
|
|
|
|
|
| |
Start with the offset where we did append the new root
components, so we won't mess with the initial checked list.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Fixes some strange behavior in case we depend on the
default check state changed signal. It would emit true
since it would fill the current checked list first and
later the initial checked list.
|
|
|
|
|
| |
Remove double cache since we can lookup the index
by the component name as well.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
I've had several crashes caused be by the deleting order,
so get rid of the root component at all. Now we keep a list
of root components again.
|
| |
|
| |
|
|
|