--- Log opened Mon Nov 12 00:00:04 2018
01:32 -!- Horwitz [~mich1@p200300EC9BEFAE00022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 252 seconds]
05:26 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
05:26 -!- mode/#navit [+v xenos1984] by ChanServ
07:00 #navit: <@KaZeR> rokm: yep. The issue with uinput is that you won't get the same behavior all the time. For example, if you're looking at a map or are in a menu, the key handling might differ. Dbus is a good way to avoid that
07:01 #navit: <@KaZeR> >  genesis | @navitNooby : don't lost your time , tomtom is unsupported.   
07:01 #navit: <@KaZeR> that's incorrect
07:01 #navit: <+Navit> <jkoan> hi @KaZeR
07:01 #navit: <@KaZeR> hi jkoan 
07:01 #navit: <@KaZeR> have you seen navitNooby's question?
07:02 #navit: <+jkoan> yes, but hasn't time to answer it yesterday
07:03 #navit: <@KaZeR> jkoan: no worries
07:11 #navit: <+jkoan> @navitNooby: tomtom is in fact supported, but not tested. But we are really willing to help with any issue because we want to support tomtom. But i am working on a new Operating System to replace the old one and use Navit with it. But this is not ready for prime time. But first it would be interesting to know which device you have
07:12 #navit: < rokm> KaZeR: the issue with uinput is that I not able to get it work on map view
07:13 #navit: < rokm> KaZeR: dbus approach requires additional modification on navit side
07:14 #navit: < rokm> KaZeR: I looked into signals and dont see actions like back or enter menu
07:15 #navit: <+jkoan> @navitNooby: but for your issue about the website it would be nice if you could send us the link where you see broken things
07:15 #navit: < rokm> KaZeR: I thought that I can use keys which are defined in navit.xml
07:16 #navit: <@KaZeR> rokm: hence my question :) @KaZeR | rokm: what event are you trying to push from your app to navit? 
07:16 #navit: <@KaZeR> you said that your app needs two buttons, right? so it's back and enter?
07:16 #navit: < rokm> enter menu screen
07:16 #navit: < rokm> back 
07:17 #navit: <@KaZeR> rokm: ok. we can easily add that together if you want
07:17 #navit: < rokm> via dbus ?
07:19 #navit: < rokm> I thin I can use the same functions like used in buttons
07:23 #navit: <@KaZeR> so "back" is implemented here : https://github.com/navit-gps/navit/blob/trunk/navit/gui/internal/gui_internal.c#L420 
07:23 #navit: <@KaZeR> and "main menu" is here : https://github.com/navit-gps/navit/blob/trunk/navit/gui/internal/gui_internal.c#L430
07:23 #navit: <@KaZeR> the potential issue with dbus is that these are gui internal private.. let me see
07:28 -!- naggety [~naggety@216.red-80-27-193.dynamicip.rima-tde.net] has joined #navit
07:37 #navit: <@KaZeR> rokm: how did you define the keys currently?
07:38 #navit: < rokm> KaZeR: In navit or uinput?
07:40 #navit: < rokm> https://github.com/torvalds/linux/blob/master/include/uapi/linux/input-event-codes.h
07:41 #navit: < rokm> on Navit I extended osd button section with accesskey like described here https://wiki.navit-project.org/index.php/OSD#Keybindings
07:42 #navit: <@KaZeR> rokm: can you share your exact osd button config?
07:53 #navit: < rokm> dont have access to my repo right now and dont want to recreate these linecfrom my mind
07:53 #navit: <@KaZeR> no worries
07:54 #navit: < rokm> but to normal button which was visible on navigation
07:54 #navit: <@KaZeR> i think that a dbus call like "/org/navit_project/navit/default_navit org.navit_project.navit.gui.command string:"menu()"" should do exactly what you want. Unfortunately there's a bug in request_command() it seems
07:54 #navit: <@KaZeR> i'm tracking it down but will have to signoff soon
07:54 #navit: < rokm> I added accesskey="&amp;#20;"
07:55 #navit: <@KaZeR> if you want to test the dbus approach, /org/navit_project/navit/default_navit org.navit_project.navit.navit.zoom int32:-2 should work right now
07:55 #navit: < rokm> + use_overlay=1
07:55 #navit: <@KaZeR> (as a test of sending a message from your app to navit)
07:55 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 268 seconds]
07:58 #navit: < rokm> KaZeR: can I back to you tommorow?
07:59 #navit: <@KaZeR> absolutely
07:59 #navit: <@KaZeR> i'm looking into the issue, seems to be in gui_get_attr()
08:01 #navit: < rokm> ok So I will check it tomorrow. thx for support
08:03 #navit: <@KaZeR> np. actually : /org/navit_project/navit/default_navit org.navit_project.navit.navit.evaluate string:"gui.menu()" works
08:03 #navit: <@KaZeR> and so does /org/navit_project/navit/default_navit org.navit_project.navit.navit.evaluate string:"gui.back()" 
08:05 #navit: <@KaZeR> you might want to use /org/navit_project/navit/default_navit org.navit_project.navit.navit.evaluate string:"gui.menu(\"#Main Menu\")" for the menu actually. Brings you back to the main menu, wherever you call it from
08:19 #navit: <@KaZeR> rokm: here are a few more examples in case you're interested : https://wiki.navit-project.org/index.php/Command_interface 
08:22 #navit: < rokm> super
08:24 #navit: < rokm> thanks again
08:24 #navit: < rokm> will let you know tomorrow
08:24 #navit: < rokm> :)
08:27 -!- basilic666 [b92ed552@gateway/web/freenode/ip.185.46.213.82] has joined #navit
08:27 #navit: < basilic666> KaZeR: are you here?
08:29 #navit: < basilic666> I try to compile navit on raspbian. But the dependencie libgtk2.0-dev can't be install.
08:39 #navit: < naggety> basilic666: look if this helps: https://www.raspberrypi.org/forums/viewtopic.php?t=123947
08:40 #navit: < naggety> most problems regarding that seems to be because not well configured source.list
08:59 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
08:59 -!- mode/#navit [+v xenos1984] by ChanServ
08:59 #navit: < basilic666> hello naggety 
08:59 #navit: < basilic666> It's a fresh install
08:59 #navit: < basilic666> I will search about source
09:03 #navit: <+jkoan> basilic666: did you have done a update before?
09:03 #navit: < basilic666> yes
09:03 #navit: < basilic666> I have done and apt-get update
09:04 #navit: < basilic666> hum... it's ok now...
09:05 #navit: < basilic666> I don't understand why lol
09:05 #navit: < basilic666> need 2 update...
09:05 #navit: <+jkoan> hm okay  ^^ 
09:06 #navit: < basilic666> I will continu to install dependencie now
09:07 #navit: <+jkoan> ilovekiruna: i try to get the reason why the xml is not split anymore in PR#559
09:08 #navit: <+jkoan> basilic666: cool :) do you build a carpc?
09:08 #navit: < basilic666> yes
09:08 #navit: < basilic666> a GPS PC lol
09:09 #navit: < basilic666> I will need GPS and MP3 only
09:09 #navit: < basilic666> no more
09:09 #navit: <+jkoan> could be cool if you could share screenshots when you are finished ;)
09:09 #navit: < basilic666> hum seems have a problem
09:10 #navit: <+jkoan> did you know about the media player functionality of navit?
09:10 #navit: <+jkoan> what problem? Log?
09:10 #navit: < basilic666> When I install libgtk2.0-dev apt-get remove libpng12
09:11 #navit: <+jkoan> hm, strange. Do you have the full output?
09:11 #navit: < basilic666> I will try to connect with the pi
09:13 -!- basilic_Pi [4d882b22@gateway/web/freenode/ip.77.136.43.34] has joined #navit
09:14 #navit: < basilic_Pi> https://pastebin.com/xdzX8HUy
09:14 #navit: < basilic666> it's in french :)
09:14 #navit: < basilic666> or frenglish 
09:14 #navit: < basilic666> one line in english other in french...
09:16 #navit: < basilic666> ENLEVES is remove
09:17 #navit: <+jkoan> hm, really strange
09:19 #navit: <+jkoan> does this help? https://stackoverflow.com/a/33284822
09:19 #navit: < basilic_Pi> I think It's too old
09:20 #navit: < basilic_Pi> 3 years
09:23 #navit: <+jkoan> but the policy command can help to find the "issue"
09:28 #navit: < basilic_Pi> install libgtk2.0-dev remove ligpng12-dev reciprocally
09:29 #navit: < basilic_Pi> I'm back later, I have a meeting now ;)
09:50 -!- basilic666 [b92ed552@gateway/web/freenode/ip.185.46.213.82] has quit [Ping timeout: 256 seconds]
09:50 #navit: < basilic_Pi> back
11:20 -!- naggety [~naggety@216.red-80-27-193.dynamicip.rima-tde.net] has quit [Ping timeout: 252 seconds]
11:20 -!- naggety [~naggety@179.red-81-47-27.dynamicip.rima-tde.net] has joined #navit
12:12 #navit: < basilic_Pi> back
15:05 -!- basilic333 [b92ed552@gateway/web/freenode/ip.185.46.213.82] has joined #navit
15:05 #navit: < basilic333> hello all?
15:06 -!- basilic_Pi [4d882b22@gateway/web/freenode/ip.77.136.43.34] has quit [Ping timeout: 256 seconds]
15:19 -!- basilic333 [b92ed552@gateway/web/freenode/ip.185.46.213.82] has left #navit []
15:25 -!- naggety [~naggety@179.red-81-47-27.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
15:49 #navit: <+jkoan> Hi all :) I am also back
16:31 #navit: <@KaZeR> rokm: very crude python2 dbus example : https://gist.github.com/pgrandin/044dd5eb326aff84c79c82bc6a9b048d
16:36 #navit: < basilic_> ltu
16:36 #navit: < basilic_> hey KaZeR 
16:38 #navit: < basilic_> KaZeR, I don't know if you have read the log, but I have try to compile navit audio branch
16:38 #navit: < basilic_> but I have some problem
16:46 #navit: <+jkoan> KaZeR: do we have support for whether conditions?
16:49 #navit: < basilic_> jkoan, my "carpc" replace an existing 7" GPS onboard
16:49 #navit: < basilic_> normaly we can't see différence except the GPS software
16:50 #navit: <+jkoan> Oh cool :)
16:50 #navit: <+jkoan> What is the OS? Linux or wince?
16:50 #navit: < basilic_> linux
16:51 #navit: <+jkoan> Nice
16:53 #navit: < basilic_> I will try to use all orignal function
16:53 #navit: < basilic_> I have a navigation control
16:53 #navit: < basilic_> with direction, zoom, menu, enter, maps, return
16:53 #navit: < basilic_> and voice
16:53 #navit: <+jkoan> This makes sense :)
16:53 #navit: < basilic_> but it's a serial data
16:54 #navit: <+jkoan> Voice output or input (voice control)
16:54 #navit: < basilic_> this not the simple way
16:54 #navit: < basilic_> I think (I not really use it) it's for change the voice
16:54 #navit: < basilic_> but I can use for other thing
16:54 #navit: < basilic_> :)
16:55 #navit: <+jkoan> Yes of course ^^
16:57 #navit: < basilic_> but for that I need to compile it :)
16:58 #navit: <+jkoan> Do you write a own plugin in c or a external software to use with the python api?
16:58 #navit: < basilic_> I do nothing for the moment
16:58 #navit: < basilic_> I will compile the audio branch
16:59 #navit: < basilic_> for play MP3 and use navit
16:59 #navit: < basilic_> for the control, I see 2 option
16:59 #navit: < basilic_> first write a script to translate serial data to key input (but seems not working realy good)
16:59 #navit: < basilic_> or make a interface
17:00 #navit: < basilic_> to translate serial input to keyboard device
17:00 #navit: < basilic_> for exemple by using and Arduino Micro pro
17:01 #navit: <+jkoan> Sounds like a cool idea
17:01 #navit: < basilic_> or juste and usb/uart interface 
17:01 #navit: < basilic_> if we can integred in software
17:01 #navit: < basilic_> I can't directly connect serial to raspberry pi, it's a 5V serial data and raspberry pi only support 3.3V on GPIO
17:02 #navit: <+jkoan> Then you could use a logic level converter
17:02 #navit: < basilic_> yes
17:02 #navit: < basilic_> but it's chipper to use an FTDI
17:03 #navit: < basilic_> like this: https://fr.aliexpress.com/item/High-Quality-FT232RL-FT232-FTDI-USB-3-3V-5-5V-to-TTL-Serial-Adapter-Module-Mini/32826575637.html
17:03 #navit: < basilic_> for 1.3€... I can try to make a PCB with connector and logical level adapter
17:03 #navit: < basilic_> but I think it's more expensive
17:05 #navit: < basilic_> or a chiness version at 0.5€
17:06 #navit: < basilic_> a CH340
17:07 #navit: < basilic_> maybe this is the best: https://fr.aliexpress.com/item/New-PL2303HX-USB-Transfer-to-TTL-RS232-Serial-Port-Adapter-Cable-Module-PL2303-Console-Recovery-Upgrade/1981712661.html
17:07 #navit: <+jkoan> Yes, don't know what would be the best version ;) only wanted to give ideas
17:07 #navit: < basilic_> 0.8€ and not need cable with 2 connector
17:07 #navit: < basilic_> best version it yours :)
17:07 #navit: < basilic_> lol
17:08 #navit: < basilic_> if god (KaZeR) would help me 
19:17 #navit: <+ilovekiruna> hi KaZer, hi jkoan, hi basilic_
19:17 #navit: <+jkoan> Hi ilovekiruna
19:18 #navit: <+ilovekiruna> jkoan: so the navit.xml in the rpm package should be already split?
19:18 #navit: <+jkoan> It is not, but it should, couldn't find the reason for now
19:19 #navit: <+ilovekiruna> so you check it, yourself?
19:19 #navit: <+ilovekiruna> or should i double-check?
19:20 #navit: <+jkoan> You can also recheck.
19:21 #navit: <+jkoan> In the rpm is only one xml, but for me it's not clear where it gets combined.
19:22 #navit: <+jkoan> My idea was that while transforming the xi:include gets included, but this doesn't seem to be the case
19:23 #navit: <+ilovekiruna> I agree
19:23 #navit: <+ilovekiruna> however, I saw at least one two xi:include statements in navit.xml
19:25 #navit: <+ilovekiruna> seems like it works in the linux build, right?
19:25 #navit: <+ilovekiruna> so maybe sth is mssing in my sailfish build script?
19:28 #navit: <+jkoan> Hm
19:41 #navit: <+ilovekiruna> do you think this could be the problem?
19:42 #navit: <+ilovekiruna> or should cmake make the split automatically?
19:48 #navit: < man-x86> basilic_: I recommend using an USB-HID interface
19:49 #navit: < man-x86> I ditched the CAN/I2C interface and replaced it with an ATMega32U4: http://www.kirikoo.net/images/7manx86-2-20180501-225519.jpg
19:54 #navit: <+Navit> <KaZeR> Basilic: I’ve glanced through the logs. Your issue is with libgtk? The audio UI is currently only in the internal GUI, for which you don’t need gtk
19:59 #navit: <+jkoan> ilovekiruna: I think the build is the problem, but don't know where
20:03 #navit: <+ilovekiruna> jkoan: build system is cmake?
20:04 #navit: <+ilovekiruna> jkoan: any way I can help your efforts?
20:04 #navit: <+jkoan> Not sure where the error is introduced, need to look into it tomorrow
20:05 #navit: <+jkoan> The Sailfish build is not really clean, so I need to dig down
20:06 #navit: <+jkoan> Oh wait, probably I found it
20:07 #navit: <+Navit> <KaZeR> man-x86: nice I would love to know more
20:07 #navit: <+jkoan> Look at the circleci conf line 58-60
20:08 #navit: <+jkoan> Hi again Kazer :)
20:08 #navit: <+jkoan> KaZeR: you got private messages on irc
20:09 #navit: <+ilovekiruna> jkoan: what is the issue there?
20:10 #navit: <+ilovekiruna> use of rpmbuild instead of cmake?
20:10 #navit: <+jkoan> Think about it, we are in a pr, so we are not on the HEAD of the repo
20:10 #navit: <+ilovekiruna> ah, now I c
20:10 #navit: <+ilovekiruna> so how to change the URL to sth more proper?
20:11 #navit: < basilic_> KaZeR, Navit : I can build without gtklib if I understant
20:11 #navit: <+jkoan> Just replace the lines with checkout step like in line 75
20:11 #navit: < basilic_> man-x86, I think it's better too
20:12 #navit: <+ilovekiruna> jkoan: will it end up in the same folder?
20:13 #navit: <+jkoan> Yes, should be, if not we need to change the workspace or something like that, but it should work directly.
20:14 #navit: <+jkoan> If not we can also update the paths to code and so on, this is not so much work
20:16 #navit: <+Navit> <KaZeR> Basilic: yes, the default GUI (internal) does not need gtk to build
20:17 #navit: < basilic_> okai I will try tomorow
20:24 #navit: <+ilovekiruna> jkoan: ok, will try in an own branch possibly
20:24 #navit: <+ilovekiruna> and report back
20:26 #navit: <+ilovekiruna> or should be integrate it in the PR of iains?
20:29 #navit: <+jkoan> On branch, pr, merge. The split xml file or can be merged separate, so the Sailfish fix can arrive earlier or later, but it should not block the split any further
21:13 #navit: <+ilovekiruna> jkoan: now i see all the files as in the linux build
21:13 #navit: <+ilovekiruna> will install that version in my phone then
21:13 #navit: <+jkoan> With the patch I suggested? ^^
21:16 #navit: <@KaZeR> 21:03   (User creation log)‎ . . [FloreneChu26‎; FQVJamel03‎; BirgitHeckman9‎; AracelisMallett‎; Janessa8269‎; JimmyAtwell9070‎; NellyKersey65‎; MuoiCapehart‎; MaePilgrim716‎; JulietSinnett88‎; RoxieMcEncroe6‎]
21:16 #navit: <@KaZeR> obviously bots. I am getting more and more pissed at our wiki
21:18 #navit: <+jkoan> Me to, that's what I had no fun at cleaning it again and again... But github wiki is not really better :/ I don't know I really solution here
21:19 #navit: <+ilovekiruna> jkoan, KaZeR: put now a PR to fix the latest sfos issue
21:20 #navit: <+jkoan> Thx
21:20 #navit: <+ilovekiruna> jkoan: thx for the suggestions :-D
21:21 #navit: <+jkoan> I am waiting for the ci to complete, but then I will merge it
21:21 #navit: <+jkoan> KaZeR: or do you have any concerns on ilovekirunas PR?
21:22 #navit: <+ilovekiruna> jkoan: would be still good if iains would integrate the patch, otherwise I will need to make my cusomts tests
21:24 #navit: <+jkoan> I am Okey with both. Because the split is not related anyhow to the Sailfish build.
21:26 #navit: <+ilovekiruna> you are right. I jsut saw I did that at first, so will try that one
21:26 #navit: <+ilovekiruna> own branch
21:31 #navit: <@KaZeR> > jkoan | Me to, that's what I had no fun at cleaning it again and again... But github wiki is not really better :/ I don't know I really solution here
21:31 #navit: <@KaZeR> https://github.com/navit-gps/navit/tree/readthedocs
21:31 #navit: <@KaZeR> and https://readthedocs.org/projects/navit/
21:32 #navit: <+jkoan> This should not ne hidden in its own branch, nobody would find where to edit things
21:32 #navit: <+ilovekiruna> jkoan: I mean in own branch is a combination of my patch and the PR of iains
21:32 #navit: <+ilovekiruna> just for me to have a proper build to test
21:32 #navit: <@KaZeR> jkoan: true. it's in a branch because it was mostly a test. But i think that we should revisit that test, and expand it a bit
21:34 #navit: <+jkoan> ilovekiruna: the last comment was for read the docs not your branch
21:34 #navit: <+jkoan> KaZeR: yes
21:38 #navit: <+ilovekiruna> jkoan: I c
21:43 #navit: <+jkoan> KaZeR: is RP#713 good to merge?
21:46 #navit: <@KaZeR> go for it
21:47 #navit: <+jkoan> thx
21:54 #navit: <+ilovekiruna> KaZeR, jkoan: any idea why there is no map download available in the menus of sfos?
21:54 #navit: <+jkoan> because its only available on android
21:56 #navit: <+ilovekiruna> really?
21:56 #navit: <+ilovekiruna> :-o
21:56 #navit: <+jkoan> yes
21:56 #navit: <+jkoan> the download is handled via java on android
21:57 #navit: <+jkoan> KaZeR already programmed one in c but we never finished it for prime time because there was no api on the mapserver
21:57 #navit: <+jkoan> and we dont want to include it directly in the source like in java
21:59 #navit: <+ilovekiruna> interesting
22:02 #navit: <+ilovekiruna> could one make it specific to guis? I could imagine should be also possible via qt5
22:03 #navit: <+jkoan> as far as i remember it was implementet for internal, but not sure anymore
22:03 #navit: <+ilovekiruna> jkoan: different topic, should we try to bring the device farm back to life?
22:04 #navit: <+jkoan> generally yes, but i dont have enought time, but i will try to keep trac of the development 
22:05 #navit: <+ilovekiruna> first I will try to finish my auxmap idea
22:05 #navit: <+ilovekiruna> would put it then next on my tasks unless sth else comes up in between
22:06 #navit: <+jkoan> (Y)
22:17 #navit: <+ilovekiruna> KaZeR: still no news from fosdem :-(
23:37 #navit: < genesis> hi
--- Log closed Tue Nov 13 00:00:06 2018