[00:25:03] *** Quits: Horwitz (~mich1@p200300EC9BFDD900022268FFFE64E7C4.dip0.t-ipconnect.de) (Ping timeout: 250 seconds)
[00:38:03] *** Joins: Horwitz (~mich1@p200300EC9BC31800022268FFFE64E7C4.dip0.t-ipconnect.de)
[00:38:03] *** ChanServ sets mode: +o Horwitz
[01:17:59] *** Quits: Mineque (5305a181@83.5.161.129.ipv4.supernova.orange.pl) (Ping timeout: 260 seconds)
[01:18:43] *** Joins: Mineque (~mineque@62-210-136-72.rev.poneytelecom.eu)
[01:18:43] *** ChanServ sets mode: +v Mineque
[04:04:23] *** Joins: xenos1984 (~xenos1984@a6a8-5521-afd9-ac03-d480-87c4-07d0-2001.dyn.estpak.ee)
[04:04:23] *** ChanServ sets mode: +v xenos1984
[06:50:28] *** Quits: xenos1984 (~xenos1984@a6a8-5521-afd9-ac03-d480-87c4-07d0-2001.dyn.estpak.ee) (*.net *.split)
[07:16:36] *** Joins: xenos1984 (~xenos1984@a6a8-5521-afd9-ac03-d480-87c4-07d0-2001.dyn.estpak.ee)
[07:16:36] *** adams.freenode.net sets mode: +v xenos1984   
[08:27:06] *** Quits: xenos1984 (~xenos1984@a6a8-5521-afd9-ac03-d480-87c4-07d0-2001.dyn.estpak.ee) (*.net *.split)
[09:38:04] *** Joins: xenos1984 (~xenos1984@a6a8-5521-afd9-ac03-d480-87c4-07d0-2001.dyn.estpak.ee)
[09:38:04] *** ChanServ sets mode: +v xenos1984
[11:45:53] <Navit> <07viktorgino> Hi All, had a busy week last week, but managed to get started on the QML GUI
[11:46:33] <Navit> <07viktorgino> just pushed my WIP to the navit-gui-qt5 repo, you can find it here :https://github.com/navit-gps/navit-gui-qt5
[11:46:58] <Navit> <07viktorgino> you can build it with qmake then make
[11:47:35] <Navit> <07viktorgino> the executable will be called navit-qml
[11:50:30] <Navit> <07viktorgino> https://cdn.discordapp.com/attachments/500190750085087235/600293108466581504/Hello_World_15_07_2019_12_49_19.mp4
[11:50:37] <Navit> <07viktorgino> this is where i'm at with ut
[11:50:39] <Navit> <07viktorgino> *it
[15:33:41] <kazer> hi there
[15:33:50] <Navit> <05jkoan> Hi Kazer
[15:34:49] <kazer> @viktorgino i am really excited about this! nice!
[15:48:37] <Navit> <07viktorgino> Hi @KaZeR
[15:49:03] <Navit> <07viktorgino> I think its coming along nicely so far
[15:49:45] <Navit> <07viktorgino> I had one thought: how easy it is to change settings once Navit is loaded?
[15:51:00] <Navit> <07viktorgino> Ideally I could add a lot of the settings to the GUI that's set through XML currently
[15:52:01] <Navit> <07viktorgino> if not through the built in functions, then we could use the XML module in Qt and reload the config file once changed
[15:52:01] <Navit> <07viktorgino> https://doc.qt.io/qt-5/qtxml-module.html
[15:58:05] <kazer> @viktorgino technically it's not complicated, although we never had a consensus about the best way to do it
[15:58:36] <kazer> navit core will write `center.txt` for example with the last position your view was centered on when you exit the application
[15:58:53] <kazer> the GTK UI saves some session related settings in a different file too
[15:59:34] <kazer> i think that it would make sense to consolidate this and generate an xml file that we would read after reading the current configuration file and which would override the relevant settings
[16:00:26] <kazer> i think that overwriting the config file probably isn't the best option. if we use a "session" file then we could also add a flag to navit to clear it and revert to the pristine config file if needed
[16:00:31] <kazer> what do you think?
[16:14:50] <Navit> <07viktorgino> for the navit specific config it makes sense to keep using XML and parsing is fairly straight forward from Qt.
[16:17:11] <Navit> <07viktorgino> For the OSD/GUI specific settings it would make sense to use Qt's settings system, that uses either the registry on Windows, property list files on mac and .ini files on *nix systems
[16:17:18] <Navit> <07viktorgino> https://doc.qt.io/qt-5/qsettings.html#details
[16:17:51] <Navit> <07viktorgino> I think it would be a nice addition to have the ability to change the colors etc of the map from the GUI
[16:17:59] <Navit> <07viktorgino> how viable would that be?
[16:20:42] <Navit> <07viktorgino> is there a loading order for config files? ie look in the install folder first then look in the ~/.navit folder etc?
[16:22:46] <kazer> this sounds like a good idea, although i am wondering if it wouldn't be better to have one common place to look into if we need to troubleshoot
[16:23:05] <kazer> i.e., one file that's always the same regarless of the platform
[16:23:42] <kazer> changing colors on the fly would be easy. we just need to throw a menu that would allow us to do it
[16:33:29] <Navit> <07viktorgino> its possible to register a custom backend with QSettings, so it is possible to create a custom handler that reads Navit's config files, so we can store the UI setting in the same file as Navit's
[16:35:00] <Navit> <07viktorgino> basically when loading the UI we just need to get the current config file from Navit, make sure its editable etc
[16:35:28] <Navit> <07viktorgino> if not copy it to ~/.navit and use/edit that
[16:53:43] <kazer> > make sure its editable etc   
[16:54:03] <kazer> so you suggest editing a copy of the original file, instead of managing some type of config overlay?
[17:35:27] *** Joins: gernot2 (5b257862@p5B257862.dip0.t-ipconnect.de)
[17:35:32] <gernot2> Hi
[17:39:10] <gernot2> back in 20 minutes
[17:48:29] *** Joins: tryagain (~quassel@217.107.194.27)
[17:48:29] *** ChanServ sets mode: +o tryagain
[17:50:17] <tryagain> hey all
[17:58:35] <tryagain> it looks like we miss an issue regarding upcoming Google Play requirement to support 64 bit architectures. Or do we already support Android ARM 64?
[17:58:39] <tryagain> https://developer.android.com/distribute/best-practices/develop/64-bit
[17:59:57] <gernot2> ilovekiruna i have no success with the speedwarner problem. Every thing i try has some side effects.
[18:12:00] <ilovekiruna> hi gernot2
[18:12:03] <ilovekiruna> sorry to hear that
[18:15:27] <gernot2> Now think i know where things are done, but not the time when they done.
[18:15:36] <kazer> tryagain: i think that you are right, we might not be fully compliant ye
[18:15:38] <kazer> *yet
[18:15:55] <gernot2> Now i try to get the log 
[18:16:53] <tryagain> kazer I guess it should be almost as simple as just adding a key to build arm64 version of libnavit
[18:43:33] <gernot2> ilovekiruna Now i have a solution. its not perfekt, but the "freezing" is gone. 
[18:44:17] <gernot2> Not perfect means that the solution is also in navit.c and that wiping from the speedwarner toggle its status.
[18:44:25] <gernot2> What now?
[18:48:27] <ilovekiruna> what about moving idea you had?
[18:50:10] <gernot2> I check "this_->motion_timeout" to NULL. 
[18:50:37] <gernot2> if a motion is going on I exit the speedarner callback
[18:51:08] <gernot2> i show a diff
[18:56:55] <gernot2> ilovekiruna https://pastebin.com/PN8cQ1sk
[18:57:17] <gernot2> I also added a prototype in navit.h
[19:08:22] <ilovekiruna> gernot2: right now, I honestly, have not much of suggestions left :(
[19:11:10] <gernot2> But now all buttons behavior is equal. The problem ist the possible big impact. A solution in the java files would be much better.
[19:12:10] <ilovekiruna> I have on more idea, wondering if we did it before
[19:33:45] <ilovekiruna> I wonder how to call a redraw in android
[19:38:15] <gernot2> We also need a "screen recenter" it looks like scrolling the card is not a real scroll. Its more a "move the visible window away". Then finger up->update+recenter 
[19:39:41] <gernot2> card=map
[19:40:26] <gernot2> This way work only the android port
[19:40:43] <ilovekiruna> where did you find screen recenter?
[19:46:39] <gernot2> check the function navit_motion_timeout in navit.c
[19:47:00] <gernot2> I dont find it the jave files
[20:04:02] <gernot2> i make some tests tomorrow
[20:04:06] <gernot2> by
[20:05:12] <ilovekiruna> ok
[20:05:15] <ilovekiruna> by
[20:07:21] *** Quits: gernot2 (5b257862@p5B257862.dip0.t-ipconnect.de) (Quit: gernot2)
[22:00:26] *** Quits: xenos1984 (~xenos1984@a6a8-5521-afd9-ac03-d480-87c4-07d0-2001.dyn.estpak.ee) (Quit: Leaving.)
[23:33:17] <Navit> <07viktorgino> @KaZeR I'm a bit split between having overlays vs having a copy of the default settings in the user folder.
[23:36:08] <Navit> <07viktorgino> the problem with having a copy is that if the installed config file ever changes it wont be reflected in the copied one
[23:38:20] <Navit> <07viktorgino> so its probably better to implement some kind of config overlay
[23:39:08] <Navit> <07KaZeR> @viktorgino exactly
[23:48:23] <Navit> <07viktorgino> I will be able to use a lot of the OSD settings from here : http://wiki.navit-project.org/index.php/OSD
[23:48:36] <Navit> <07viktorgino> but how easy is it to add new ones?
[23:49:34] <Navit> <07KaZeR> It is quite easy. There is a simple example in the j1850 plugin for example. I am on mobile right now but can share code later
[23:50:12] <Navit> <07viktorgino> sure, just trying to understand the internals a little better
[23:50:22] <Navit> <07viktorgino> and understand what needs to be done etc
[23:51:12] <Navit> <07viktorgino> would it make sense to add a separate xml tag for the qml gui or extend the ones under the osd tag?
[23:51:51] <Navit> <07KaZeR> OSD are more meant to be reusable between UIs
[23:52:41] <Navit> <07KaZeR> currently we don’t really have a way to say “this OSD only works with QT” because the intent was for them to use abstracted drawing primitives
[23:53:19] <Navit> <07KaZeR> We can build QT/QML specific OSD (and they could look really nice ) but in that case maybe we should couple them with the GUI
[23:55:17] <Navit> <07viktorgino> i think that would make sense
[23:55:47] <Navit> <07viktorgino> ie most of the stuff is draw using qml
[23:58:15] <Navit> <07viktorgino> only the most necessary stuff is drawn with the navit backend, ie : all the map objects, waypoints etc
[23:58:35] <Navit> <07viktorgino> all the menus, buttons and on screen stuff with qml