Bug 333991

Summary: Boolean setting in order to allow/disallow the dragging of the routing path
Product: [Applications] marble Reporter: Renato <rfringuello>
Component: generalAssignee: Dennis Nienhüser <nienhueser>
Status: RESOLVED FIXED    
Severity: wishlist CC: nienhueser
Priority: NOR    
Version: 1.7 (KDE 4.12)   
Target Milestone: ---   
Platform: Slackware   
OS: All   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Renato 2014-04-28 07:34:49 UTC
I want to disable the dragging of the route path because the user of my service should not be able to edit the path by input (mouse or touch). Once the path is calculated from Monav the user must not edit it.
To keep it simple, it could be OK have a boolean setting, a new method in the routingLayer and a flag (in the routingLayer too) that should be verified in the handleMouseButtonPress method.

Reproducible: Always
Comment 1 Renato 2014-04-28 07:46:52 UTC
Obviously same thing can be obtained editing the eventFilter method.
Comment 2 Dennis Nienhüser 2014-05-01 20:53:26 UTC
Git commit a17828023963b7ff0a4ab405402e8fc2ba7cf306 by Dennis Nienhüser.
Committed on 01/05/2014 at 20:48.
Pushed by nienhueser into branch 'master'.

Add RoutingLayer::setInteractive(bool) and bool isInteractive()

Can be used to disable interaction with the current route (i.e. the
user cannot add/change/delete routing via points including start
and destination), typically to be called on
MarbleWidget::routingLayer().

M  +11   -4    src/lib/marble/MarbleWidgetPopupMenu.cpp
M  +27   -5    src/lib/marble/routing/RoutingLayer.cpp
M  +12   -0    src/lib/marble/routing/RoutingLayer.h

http://commits.kde.org/marble/a17828023963b7ff0a4ab405402e8fc2ba7cf306
Comment 3 Renato 2014-05-02 06:58:31 UTC
Thank you Dennis!

On Monday I will merge this commit in my code ;)


2014-05-01 22:53 GMT+02:00 Dennis Nienhüser <earthwings@gentoo.org>:

> https://bugs.kde.org/show_bug.cgi?id=333991
>
> Dennis Nienhüser <earthwings@gentoo.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>              Status|ASSIGNED                    |RESOLVED
>          Resolution|---                         |FIXED
>       Latest Commit|                            |
> http://commits.kde.org/marb
>                    |
>  |le/a17828023963b7ff0a4ab405
>                    |                            |402e8fc2ba7cf306
>
> --- Comment #2 from Dennis Nienhüser <earthwings@gentoo.org> ---
> Git commit a17828023963b7ff0a4ab405402e8fc2ba7cf306 by Dennis Nienhüser.
> Committed on 01/05/2014 at 20:48.
> Pushed by nienhueser into branch 'master'.
>
> Add RoutingLayer::setInteractive(bool) and bool isInteractive()
>
> Can be used to disable interaction with the current route (i.e. the
> user cannot add/change/delete routing via points including start
> and destination), typically to be called on
> MarbleWidget::routingLayer().
>
> M  +11   -4    src/lib/marble/MarbleWidgetPopupMenu.cpp
> M  +27   -5    src/lib/marble/routing/RoutingLayer.cpp
> M  +12   -0    src/lib/marble/routing/RoutingLayer.h
>
> http://commits.kde.org/marble/a17828023963b7ff0a4ab405402e8fc2ba7cf306
>
> --
> You are receiving this mail because:
> You reported the bug.
>