organize trip controls vs. route controls

The file mgmt and waypoints are part of the "trip"

The toggles and details are part of the route. I considered combining
the toggle section into the "route details" section but... decided
against it to delineate "input" from "output". I could be persuaded to
keep iterating on this...
This commit is contained in:
Michael Kirk 2021-10-11 15:33:46 -07:00 committed by Dustin Carlino
parent 738c4ab865
commit 5e592447b7
2 changed files with 6 additions and 3 deletions

View File

@ -133,7 +133,6 @@ impl TripManagement {
.build_widget(ctx, "next trip"),
]),
])
.section(ctx)
}
pub fn on_click(&mut self, ctx: &mut EventCtx, app: &App, action: &str) -> Option<Transition> {

View File

@ -119,7 +119,12 @@ impl TripPlanner {
fn update_input_panel(&mut self, ctx: &mut EventCtx, app: &App, main_route: Widget) {
let col = Widget::col(vec![
self.files.get_panel_widget(ctx),
Widget::col(vec![
self.files.get_panel_widget(ctx),
Widget::horiz_separator(ctx, 1.0),
self.waypoints.get_panel_widget(ctx),
])
.section(ctx),
Widget::row(vec![
Toggle::checkbox(
ctx,
@ -135,7 +140,6 @@ impl TripPlanner {
),
])
.section(ctx),
self.waypoints.get_panel_widget(ctx).section(ctx),
main_route.section(ctx),
]);