- 02 May, 2016 1 commit
-
-
dogmaphobic authored
-
- 26 Apr, 2016 3 commits
-
-
Tomaz Canabrava authored
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
Gus Grubba authored
Actually, changed so showDialog figures out on its own if it should use available height or full parent height. The variable is now set by the main window, which controls which view is being shown. I commented off some code in ParameterEditorDialog.qml as it is not properly handling the dialog and causing it to get "stuck".
-
dogmaphobic authored
Actually, changed so showDialog figures out on its own if it should use available height or full parent height. The variable is now set by the main window, which controls which view is being shown. I commented off some code in ParameterEditorDialog.qml as it is not properly handling the dialog and causing it to get "stuck".
-
- 25 Apr, 2016 1 commit
-
-
Tomaz Canabrava authored
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
- 24 Apr, 2016 1 commit
-
-
Jimmy Johnson authored
-
- 22 Apr, 2016 1 commit
-
-
dogmaphobic authored
-
- 21 Apr, 2016 1 commit
-
-
dogmaphobic authored
-
- 14 Apr, 2016 1 commit
-
-
Don Gagne authored
-
- 13 Apr, 2016 6 commits
-
-
Tomaz Canabrava authored
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
Tomaz Canabrava authored
instead of onEntered: { __forceHoverOff = false; hoverTimer.start() } Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
Tomaz Canabrava authored
without a check this code should be a bit faster, and thus the check was really uneeded. Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
Tomaz Canabrava authored
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
Tomaz Canabrava authored
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
Tomaz Canabrava authored
Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
- 11 Apr, 2016 1 commit
-
-
Tomaz Canabrava authored
This makes it possible to select more than one value to be used in the parameter configuration, and since the parameter is actually a bitfield - this is the correct thing to do. one of the drawbacks is that in the parameter listing the value of the Fact will not be displayed as string anymore, but with 'undefined: numerical-value', that is the OR combination of the applied values. Signed-off-by: Tomaz Canabrava <tomaz.canabrava@intel.com>
-
- 10 Apr, 2016 2 commits
- 06 Apr, 2016 2 commits
-
-
Nate Weibley authored
-
Nate Weibley authored
-
- 05 Apr, 2016 2 commits
-
-
Nate Weibley authored
-
Nate Weibley authored
-
- 29 Mar, 2016 1 commit
-
-
Don Gagne authored
-
- 28 Mar, 2016 1 commit
-
-
Don Gagne authored
Map control use different border color based on map type
-
- 23 Mar, 2016 2 commits
- 16 Mar, 2016 2 commits
-
-
Nate Weibley authored
-
dogmaphobic authored
-
- 14 Mar, 2016 3 commits
- 13 Mar, 2016 3 commits
- 11 Mar, 2016 1 commit
-
-
Don Gagne authored
-
- 10 Mar, 2016 1 commit
-
-
Helmut Wolf authored
Note that a change in zoom signals a `zoomLevelChanged` event; this in turn triggers `FlightDisplayViewMap` which sets the property changed in this commit to ``` onZoomLevelChanged: QGroundControl.flightMapZoom = zoomLevel ``` This triggers the following message in Application Output: `onZoomLevelChanged: QGroundControl.flightMapZoom = zoomLevel`. This was the case before and after this fix, I don't know if that's a real issue though
-
- 07 Mar, 2016 1 commit
-
-
Don Gagne authored
- Convert mission load/save to it - Allow parameter load/save on mobile
-
- 06 Mar, 2016 3 commits