--- Log opened Sat Nov 17 00:00:12 2018 00:00 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 01:05 -!- jkoan [OISjdTfIA6@hadar.uberspace.de] has quit [Ping timeout: 272 seconds] 05:08 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 05:08 -!- mode/#navit [+v xenos1984] by ChanServ 05:26 #navit: <+Navit> hello i want to debug navit code 05:26 #navit: <+Navit> Can someone help me with that 05:35 #navit: <+Navit> Hi! 05:35 #navit: <+Navit> Sure. Are you familiar with gdb? 05:35 #navit: <+Navit> Only heared about it, havent used it 05:36 #navit: <+Navit> i was trying with CDT 05:36 #navit: <+Navit> in eclipse 05:36 #navit: <+Navit> I am not familiar with cdt 05:37 #navit: <+Navit> ok yes can it be done with gdb 05:37 #navit: <+Navit> do we need some changes in make file? 05:37 #navit: <+Navit> If you want a UI you can also try ddd, it uses gdb in the background too 05:37 #navit: <+Navit> No nothing needs to be changed. The code from fit has debugging symbols enabled 05:38 #navit: <+Navit> just a min 05:39 #navit: <+Navit> i have followed 05:39 #navit: <+Navit> as per instruction given in 05:40 #navit: <+Navit> https://wiki.navit-project.org/index.php/Linux_development 05:40 #navit: <+Navit> at last step i am just running compiled binay 05:40 #navit: <+Navit> with ./navit 05:42 #navit: <+Navit> Yep 05:43 #navit: <+Navit> If you have never used gdb I would advise you to read a quick tutorial or to use it via ddd 05:43 #navit: <+Navit> Are you trying to debug something in particular? 05:44 #navit: <+Navit> Most useful gdb commands are bt (after a crash) to get a backtrace, or b to set a break point for example 05:45 #navit: <+Navit> Feel free to expand our wiki with what you’ll learn btw 😃 05:45 #navit: <+Navit> i am debugging to understand 05:45 #navit: <+Navit> navit 05:45 #navit: <+Navit> how it works 05:45 #navit: <+Navit> yes i was just looking into how to use GDB 05:48 #navit: <+Navit> "The code from fit has debugging symbols enabled" ?? what is fit-> did you mean Git? 06:00 #navit: <+Navit> Yes git 😃 06:50 #navit: <+Navit> https://cdn.discordapp.com/attachments/500190750085087235/513244406850256906/unknown.png 06:50 #navit: <+Navit> hello Kazer thanks for guiding me 06:50 #navit: <+Navit> i tried debugging a sample c hello world program, it works well 06:51 #navit: <+Navit> i explored its features 06:51 #navit: <+Navit> but when i set navit to debug it gives me this error 06:51 #navit: <+Navit> do we need to pass something in parameter , is there something more to do . Please guide 07:00 #navit: <+Navit> i can debug step wise 07:00 #navit: <+Navit> https://cdn.discordapp.com/attachments/500190750085087235/513247161622724610/unknown.png 07:01 #navit: <+Navit> but i cannot give it a go, it just dies 07:03 #navit: <+Navit> Maybe it’s because it’s late here but I don’t see the error 07:03 #navit: <+Navit> Maybe you want to step into geom_init() ? 07:04 #navit: <+Navit> I wanted to run the program from ddd and then 07:04 #navit: <+Navit> put break point 07:04 #navit: <+Navit> Hi @KaZeR and @Arya Kumar 07:05 #navit: <+Navit> but i can do step wise debugging and cannot give program freerun 07:05 #navit: <+Navit> hello jkoan 07:06 #navit: <+Navit> sorry i have debugged only controllers , discovered debugging on linux system only hour ago, thanks to Kazer 07:06 #navit: <+Navit> @KaZeR the website is really interesting. Seems that a lot of people didn't know that we switched to gizz 07:07 #navit: <+Navit> jkoan can you help me, @KaZeR seems have got offline 07:07 #navit: <+Navit> @Arya Kumar I worked with debugging in eclipse already, it's quite easy if you set up. Eclipse right 07:08 #navit: <+Navit> ok, i am doing that in parallel already 07:08 #navit: <+Navit> but there should also be no issue in debugging with gdb using ddd 07:09 #navit: <+Navit> Can you get what problem i am facing 07:09 #navit: <+Navit> ? 07:09 #navit: <+Navit> Yes, but I did use ddd for some little time and found it extremely unintuitive. 07:10 #navit: <+Navit> yes it is like living in 90's 07:11 #navit: <+Navit> But I can't really see the error in your Screenshots. Could you please explain it again? 07:12 #navit: <+Navit> when i open navit from terminal, it works fine 07:12 #navit: <+Navit> but when i open navit from ddd 07:12 #navit: <+Navit> it says this 07:13 #navit: <+Navit> https://cdn.discordapp.com/attachments/500190750085087235/513250407418560512/unknown.png 07:14 #navit: <+Navit> says xml not found 07:14 #navit: <+Navit> but it runs when i directly run from terminal 07:14 #navit: <+Navit> You didn't set the working directory right 07:15 #navit: <+Navit> ohh i dont know 07:15 #navit: <+Navit> just a min 07:16 #navit: <+Navit> It searches in its current working directory, on terminal this works. But I don't know if ddd has the option to set the working directory, if not it has probably a parameter option where you can add the xml path 07:16 #navit: <+Navit> yes there comes a paramter window 07:18 #navit: <+Navit> https://cdn.discordapp.com/attachments/500190750085087235/513251492187078657/unknown.png 07:18 #navit: <+Navit> so what would go in that parameter option 07:18 #navit: <+Navit> pwd?? 07:19 #navit: <+Navit> Or -c 07:20 #navit: <+Navit> -c should work, yes 07:20 #navit: <@KaZeR> > cannot give program freerun 07:20 #navit: <@KaZeR> you mean continue the execution? try "c" for continue 07:21 #navit: <+Navit> ok i am trying 07:31 #navit: <+Navit> still same issue , cannot find xml 07:31 #navit: <+Navit> https://cdn.discordapp.com/attachments/500190750085087235/513254729392979975/unknown.png 07:31 #navit: <+Navit> i also gave the full path 07:31 #navit: <+Navit> https://cdn.discordapp.com/attachments/500190750085087235/513254922389684234/unknown.png 07:33 #navit: <@KaZeR> the -c flag isn't passed to navit. it should say something like this : 07:34 #navit: <@KaZeR> $ ./navit -c /foo.xml 07:34 #navit: <@KaZeR> Running from source directory 07:34 #navit: <@KaZeR> config file n is set to `/foo.xml' 07:34 #navit: <@KaZeR> error:navit:main_real:No config file navit.xml, navit.xml.local found 07:34 #navit: <@KaZeR> let me try it 07:37 #navit: <@KaZeR> so in the bottom part of the window, at the gdb prompt, try "r -c " 07:38 #navit: <@KaZeR> one thing to know also is that if you run navit that hasn't been installed, you need to run it from the directory where the binary lives, otherwise it might not be able to find some plugins 07:38 #navit: <@KaZeR> so in my example, i went into the correct folder, and ran "ddd ./navit" 07:39 #navit: <@KaZeR> if you do that, it should also find the xml file in that folder directly 07:39 #navit: <+Navit> ok doing 08:32 #navit: < basilic> hello all 08:41 #navit: < basilic> KaZeR, I have find an interresting option for me "hide_impossible_next_keys" 08:42 #navit: < basilic> but the deplacement was realy strange 08:42 #navit: < basilic> for exemple the keyboard if like: 08:42 #navit: < basilic> a c g 08:42 #navit: < basilic> i l p 08:42 #navit: < basilic> r s t v x 08:42 #navit: < basilic> y 08:42 #navit: < basilic> I on "a" 08:42 #navit: < basilic> I go left to "c" 08:43 #navit: < basilic> go next I arrive to "l" 08:43 #navit: < basilic> go left again I arrive to "l" 08:43 #navit: < basilic> left again to "ABC" 08:51 #navit: <@KaZeR> uh that's weird indeed 08:51 #navit: <@KaZeR> sorry have to go 08:52 #navit: < basilic> oki no problem 08:53 #navit: < basilic> for next: https://snag.gy/gBOeqt.jpg 08:53 #navit: < basilic> this is the keybord screen 08:53 #navit: < basilic> A->C->L->ABC 08:54 #navit: < basilic> Y->R->S->T->ABC 08:54 #navit: < basilic> Y->R->S->T->ABC 08:54 #navit: < basilic> I->R-S-T.. 08:55 #navit: < basilic> I go to the nears key not in line 08:57 #navit: < basilic> with go right P<-G<-V<-ABC<-donw arrow<-S<-R<-I<-P 08:57 #navit: < basilic> realy fun to fin a key :) 11:19 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 11:38 -!- udovdh [~udovdh@2001:981:a812:0:213:3bff:fe0f:9fb1] has joined #navit 12:02 #navit: < man-x86> Hi everyone 12:02 #navit: < man-x86> I noticed a few things about the OSD 12:02 #navit: < man-x86> http://monorailc.at/private/navit/navit1.png 12:03 #navit: < man-x86> the ETA and the navigation.item is not a real issue 12:03 #navit: < man-x86> but the missing lakes are kind of odd 12:06 #navit: < man-x86> I had the same behavior with different layouts, could it be a issue in the maps or in navit itself, or most likely a configuration issue? 12:32 -!- udovdh [~udovdh@2001:981:a812:0:213:3bff:fe0f:9fb1] has quit [Remote host closed the connection] 12:48 #navit: < man-x86> the issue with the lakes is more visible here: http://monorailc.at/private/navit/navit5_vs_osm.png 14:58 #navit: < man-x86> are there any instructions to build Navit cleanly from the source? 15:08 #navit: <+Navit> thanks jutsin and kazer now i am able to debug code to quiet a bit 15:09 #navit: <+Navit> why hasnt navit moved set destination in home screen? as it is with other maps 15:10 #navit: <+Navit> i am building from source to make that change 15:12 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 15:12 -!- mode/#navit [+v xenos1984] by ChanServ 15:16 #navit: <+ilovekiruna> hi all 15:44 #navit: <+ilovekiruna> KaZeR: seems like i found an issue with sfos 15:44 #navit: <+ilovekiruna> maps seem to be only recognized in the /usr navit folder not in the home folder 16:23 #navit: <@KaZeR> man-x86: your lake issue could be two things : incomplete map data (so you need a larger map that encompass the whole lake to avoid a missing edge) or incorrect map data (where the lake contour is self intersecting) 16:24 #navit: <@KaZeR> man-x86: example of issue #2: https://github.com/navit-gps/navit/issues/398 16:25 #navit: <@KaZeR> ha i just saw your second screenshot. so likely the issue described in this ticket 16:26 #navit: <@KaZeR> ilovekiruna: interesting. maybe it doesn't compute the home folder path correctly 16:26 #navit: <@KaZeR> man-x86: the issue happens whatever the zoom level, right? 16:29 #navit: < man-x86> KaZeR: I'm trying to upgrade to the latest Navit release, hoping that most issues would be corrected 16:33 #navit: <@KaZeR> ok. have to step out soon but let us know if you have issues 16:34 #navit: <@KaZeR> https://wiki.navit-project.org/index.php/Linux_development should be what you need 16:34 #navit: < man-x86> thanks, it's fairly basic, but that should do 16:35 #navit: <@KaZeR> we can expand it if you have questions :) 16:35 #navit: <@KaZeR> you're using a rpi 3 right? 16:36 #navit: < man-x86> i'm mostly running into outdated packages issues on Debian Jessie 16:36 #navit: < man-x86> yep, Raspi3, but I'm doing all the developement on my laptop running Jessie 16:41 #navit: <+ilovekiruna> KaZeR: should I make an github issue? 16:42 #navit: <+ilovekiruna> or do you have any idea where the issue could be? in the navit.xml? 16:46 #navit: <@KaZeR> ilovekiruna: yeah you should make an issue so that i don't forget to dig. have to go now 16:46 #navit: <@KaZeR> man-x86: remind me to show you the automated packages for rpi3 16:48 #navit: < man-x86> which automated packages? 16:49 #navit: < man-x86> I just compile from the source and build a package with the apt tools (or install it the non-debian way) 16:50 #navit: < man-x86> but I'd like to see something else 17:24 #navit: <+Navit> hello , i want to change how navit looks like, how the ui is designed? is it generated from Qt Qml, Qt designer? 17:32 #navit: <+ilovekiruna> Arya Kumar: what do you exactly want to change? The look of the maps or of the menu and interactive elements? 17:33 #navit: <+Navit> i want to get set destination menu on map screen 17:33 #navit: <+ilovekiruna> what do you mean by destiniation menu 17:34 #navit: <+ilovekiruna> I suspect one could do what you want with the osd parts of navit.mxl 17:34 #navit: <+ilovekiruna> navit.xml* 17:34 #navit: <+Navit> https://cdn.discordapp.com/attachments/500190750085087235/513406659473702912/unknown.png 17:35 #navit: <+Navit> something that appear in top left of google maps 17:35 #navit: <+Navit> i want to make things easy by doing it from map screen 17:35 #navit: <+ilovekiruna> ah, the search directly with the map in the background 17:35 #navit: <+Navit> yes 17:36 #navit: <+ilovekiruna> I think this will require quite some coding 17:36 #navit: <+Navit> also i want to add my custom menu for my custom actions 17:36 #navit: <+ilovekiruna> because so far we just have the search in the menu 17:36 #navit: <+ilovekiruna> which customs menu? 17:36 #navit: <+ilovekiruna> can you show me? 17:38 #navit: <+ilovekiruna> I think it could go a bit inline with some other efforts already at navit. check here: https://github.com/navit-gps/navit/issues/677 17:38 #navit: <+Navit> i want to add calendar, trigger a cmd to linux to show camera output infront of navit screen 17:39 #navit: <+ilovekiruna> do you have a sample picture? 17:40 #navit: <+Navit> ohh no i dont have a sample picture right now, but where you have action , settings , tools, ... menu i will put one more menu to display camera output on screen 17:41 #navit: <+Navit> and we are planning to add more feature , which will require more menu at that place 17:41 #navit: <+ilovekiruna> ah, you mean just adding one more menu item 17:41 #navit: <+Navit> yes 17:41 #navit: <+ilovekiruna> ah, ok 17:42 #navit: <+ilovekiruna> I think I briefly looked into this some time ago, but would need to some to look it up again 17:42 #navit: <+Navit> how navit does all that menu, anything with qt designer? 17:44 #navit: <+ilovekiruna> the internal menu is as far as i know coded as a html page, see here: https://github.com/navit-gps/navit/blob/b0773218ab67e00e1aa7303829f342dce87c46c0/navit/navit_shipped.xml#L51 17:47 #navit: <+ilovekiruna> for the qml gui it seems to be defined in qml files: https://github.com/navit-gps/navit/tree/trunk/navit/gui/qt5_qml 17:47 #navit: <+ilovekiruna> but I am not sure how well the qt5 gui works 17:51 #navit: <+Navit> ok internal menu is by the html design 17:51 #navit: <+Navit> and map is with qml right? 17:52 #navit: < man-x86> KaZeR: I have the exact same issues with the sources from git (b077321) 17:53 #navit: < man-x86> plus other non-critical issues (oversized icons) 17:53 #navit: <+ilovekiruna> Arya Kumar: no, the map design is also in the navit.xml file under the huge "layout" sections 17:54 #navit: <+ilovekiruna> Arya Kumar: you can find the details here: https://wiki.navit-project.org/index.php/Configuration/Layout_Options 17:54 #navit: <+Navit> ohh yes i have seen , then qml is for? 17:55 #navit: <+Navit> yes i have checked and made customization also 17:55 #navit: <+Navit> in it 17:56 #navit: <+ilovekiruna> we have different guis which can be used: gtk, internal, qt5_qml, win32 17:56 #navit: <+ilovekiruna> qml is used for the qt5 gui 17:57 #navit: <+ilovekiruna> Arya Kumar: afk 1h 18:54 #navit: <+ilovekiruna> back 19:42 -!- ilovekiruna [~ilovekiru@31.18.175.119] has quit [Read error: Connection reset by peer] 20:01 -!- ilovekiruna [~ilovekiru@ip1f12af77.dynamic.kabel-deutschland.de] has joined #navit 20:01 -!- mode/#navit [+v ilovekiruna] by ChanServ 21:17 -!- jkoan [4bUnAIBYOo@2a00:d0c0:200:0:b9:1a:9c0d:480] has joined #navit 21:17 -!- mode/#navit [+v jkoan] by ChanServ 22:40 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] --- Log closed Sun Nov 18 00:00:14 2018