https://bugs.kde.org/show_bug.cgi?id=473172
--- Comment #2 from reportthebug <chris.seife...@onenetbeyond.org> --- (In reply to Volker Krause from comment #1) > This makes sense in general, but also lets me suspect that the existing > features to avoid the need for any of that aren't working. The search form > is supposed to be pre-filled with the location and date of the current > timeline position. So the idea is that you usually would only need to adjust > the time and destination. > > If that's not happening we need to fix it. If however your usage pattern or > usecase isn't covered by that it would be interesting to learn more about > how you use this feature to better understand how to support that best. My use case would be to search for the same direction several times after searching for another connection. When I search for a connection from point A to B, for example in the Öffi app, this is saved in a kind of history at the bottom of the search field, where I can then simply click on a last search route. See the picture: https://my.adminforge.de/apps/files_sharing/publicpreview/MgnaBNMSFxqMoSD?file=/&fileId=1576156&x=1366&y=768&a=true&etag=f96025a514e7938066b8003724eabbcc -- You are receiving this mail because: You are watching all bug changes.
