--- Log opened Thu Jul 03 00:00:09 2014 03:30 -!- KaZeR [~kazer@64.201.252.132] has quit [Remote host closed the connection] 06:49 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has joined #navit 06:52 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit 09:10 -!- drlizau [~liz@billiau.net] has joined #navit 10:33 -!- tauso [~TAugustin@195.81.221.4] has joined #navit 10:40 #navit: < tauso> Hello, i've just installed the latest svn version of navit on my android device and made a look at the shipped navit.xml and noticed some OSD types I've never recognized so far: 10:40 #navit: < tauso> 10:40 #navit: < tauso> 10:40 #navit: < tauso> 10:40 #navit: < tauso> Are they new and is there a documentation somewhere in the wiki? 12:10 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection] 12:20 -!- tauso1 [~TAugustin@195.81.221.4] has joined #navit 12:22 -!- tauso [~TAugustin@195.81.221.4] has quit [Ping timeout: 260 seconds] 13:07 -!- tauso1 [~TAugustin@195.81.221.4] has left #navit [] 13:07 -!- tauso1 [~TAugustin@195.81.221.4] has joined #navit 15:08 -!- KaZeR [~kazer@64.201.252.132] has joined #navit 15:08 -!- mode/#navit [+o KaZeR] by ChanServ 15:15 -!- tauso1 is now known as tauso 15:28 -!- tauso [~TAugustin@195.81.221.4] has left #navit [] 15:54 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Quit: Page closed] 17:08 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has quit [Ping timeout: 272 seconds] 17:32 -!- tauso [~thomas@g226234248.adsl.alicedsl.de] has joined #navit 17:40 -!- tauso [~thomas@g226234248.adsl.alicedsl.de] has left #navit [] 17:41 -!- tauso [~thomas@g226234248.adsl.alicedsl.de] has joined #navit 18:07 #navit: < tauso> Hello, does the "Demo" vehicle work in the current svn version? For me it crashes everytime i try to set a route (set as position an set a destination) 18:09 #navit: < tauso> ok, have found the problem: osd type="compass" is enabled it crashes. 18:19 #navit: <@KaZeR> hi tauso 18:19 #navit: < tauso> hi 18:20 #navit: <@KaZeR> weird. can you please share a backtrace ? 18:24 #navit: < tauso> hm, debug log is empty? what do i have to add in the navit.xml? 18:26 #navit: <@KaZeR> you won't really see it in the debug log, rather in the console output in case of a segfault. do you have gdb installed ? 18:27 #navit: < tauso> http://pastebin.com/jvBPgjij 18:28 #navit: < tauso> seems so: 18:28 #navit: < tauso> ii gdb 7.7-0ubuntu3.1 amd64 GNU Debugger 18:29 #navit: <@KaZeR> yeah the BT seems complete. what is your graphic card? on my laptop, with an intel card, sometimes a bug is triggered that completely kills my X session. but that's a bug in the driver i believe 18:29 -!- Celelibi [~celelibi@2a02-8426-50a1-9d00-021b-2fff-fe35-963d.rev.sfr.net] has quit [Ping timeout: 245 seconds] 18:29 #navit: <@KaZeR> #6 0x00007fe1fa50bc59 in draw_text (gr=0x12c1ec0, fg=0x15a6710, bg=0x0, font=0x12bf6e0, text=0x16fbec0 "1400m", p=0x7fff76cb5680, dx=65536, dy=0) 18:29 #navit: <@KaZeR> at /home/thomas/svnworks/navit-code/navit/navit/graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:421 18:30 #navit: <@KaZeR> do you have issues with other OSD components or only the compass ? what other OSDs do you have enabled ? 18:30 #navit: <@KaZeR> either there is a bug in the rendering, or maybe the text which the compass is trying to render is garbage and it could lead to this crash 18:30 #navit: < tauso> its an ATI HD5670 with the proprietary fglrx driver 18:31 -!- Celelibi [~celelibi@2a02-8426-50a1-9d00-021b-2fff-fe35-963d.rev.sfr.net] has joined #navit 18:31 #navit: < tauso> i've only used the shipped navit.xml and enabled compass 18:32 #navit: < tauso> navigation_next_turn works 18:33 #navit: < tauso> i've enabled the other navigation types too and (without compass) it doesn't crash but it also doesn't show anything other than the next turn image (arrow...) 18:33 #navit: < tauso> map and route rendering seems ok, too 18:33 #navit: <@KaZeR> odd 18:34 #navit: <@KaZeR> actually the BT shows that the text is not garbage : text=0x16fbec0 "1400m" 18:35 #navit: < tauso> than maybe i've forget something to add in the xml. do I need a width attribute for these types? 18:35 #navit: < tauso> actually, i only wanted to try these (for me) new OSD types, as there is nothing about them in the wiki 18:37 #navit: < tauso> for me, the compass bug is not a big deal, cause I never use it in my "real" navit.xml on my android device. 18:37 #navit: <@KaZeR> i just tried on my laptop, osd compass + gui_internal + gtk_drawing area + demo vehicle, does not crash, compass works as expected 18:38 #navit: <@KaZeR> graphics/gtk_drawing_area/graphics_gtk_drawing_area.c:421 is a blank line for me. what do you have exactly at this position in the code ? 18:39 #navit: <@KaZeR> what do you call the new OSD types ? 18:43 #navit: < tauso> "navigation_distance_to_target", "navigation_distance_to_target" and "navigation" as types are new - for me. I've never looked at the shipped navit.xml for a long time. 18:43 #navit: < tauso> "navigation_distance_to_next" 18:45 #navit: <@KaZeR> oh ok. the navigation item is quite powerful as you can access a lot of sub-items 18:45 #navit: <@KaZeR> ${navigation.item[1].length[named]} for example 18:45 #navit: < tauso> ok, that I've used for a long time 18:45 #navit: <@KaZeR> yeah this one is quite handy :) 18:46 #navit: < tauso> but i think in my xml it is a type"text" 18:46 #navit: < tauso> 421 if (!bg->c.a) 18:46 #navit: < tauso> 422 bg=NULL; 18:48 #navit: < tauso> and i thought eventually type="navigation_distance_to_next" will replace something like ${navigation.item[1].length[named]} 18:50 #navit: <@KaZeR> have to go afk 18:50 #navit: <@KaZeR> i think this bug might be triggered by a recent change 18:50 #navit: < tauso> thanks for debugging 18:50 #navit: < tauso> bye 18:50 #navit: <@KaZeR> if you want to dig, have a look at cp15's commit in the two last weeks ( there aren't so many of them 18:51 #navit: < tauso> i think i've read something about background color 18:51 #navit: <@KaZeR> or try r5792 that's the one i have here 18:51 #navit: < tauso> and bg sounds like it 18:51 #navit: <@KaZeR> (it's from before cp15's last change) 18:51 #navit: <@KaZeR> i'll be back in ~2 h 19:13 -!- Celelibi [~celelibi@2a02-8426-50a1-9d00-021b-2fff-fe35-963d.rev.sfr.net] has quit [Ping timeout: 240 seconds] 19:17 -!- Celelibi [~celelibi@2a02-8426-50a1-9d00-021b-2fff-fe35-963d.rev.sfr.net] has joined #navit 19:24 -!- tryagain [~quassel@178.216.76.34] has joined #navit 20:14 #navit: < tryagain> tauso i guess 421 if (!bg->c.a) should be 421 if (bg && !bg->c.a) 20:20 #navit: < tryagain> tauso svn revision 5799 has the fix 20:20 -!- tryagain [~quassel@178.216.76.34] has quit [Remote host closed the connection] 20:33 #navit: <@KaZeR> i'm back 20:34 #navit: <@KaZeR> good catch from tryagin 20:34 #navit: <@KaZeR> s/gin/gain 20:39 -!- j_f-f [~quassel@orion2589.server4you.de] has quit [Remote host closed the connection] 20:39 -!- drlizau [~liz@billiau.net] has joined #navit 20:42 -!- j_f-f [~quassel@orion2589.server4you.de] has joined #navit 21:13 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection] 21:32 #navit: < tauso> wo, that was a quick fix :-D 21:50 -!- woglinde [~henning@e179037170.adsl.alicedsl.de] has joined #navit 22:00 -!- tg [~x@unaffiliated/tg] has quit [Ping timeout: 255 seconds] 22:02 -!- tg [~x@unaffiliated/tg] has joined #navit 22:05 #navit: < tauso> For me the osd types i mentioned earlier (which are in the shipped navit.xml) don't work. And when I grep for "navigation_distance" over the whole navit code, i can only find it in the navit.xml file and not in the "/navit/osd/core/osd_core.c" 22:08 #navit: <@KaZeR> the example in the xml might be a leftover indeed. does ${navigation.item[1].length[named]} fits your need ? iirc, the point was that switching to the navigation item would allow even more configuration when the navigation_distance was quite static 22:08 #navit: <@KaZeR> tauso, can you confirm that tryagain's fix fixed your issue ? 22:10 #navit: < tauso> yes, as i mentioned earlier, I have used this syntax for a long time and i thought the navigation types where a just a new form of that syntax, thats what confused me. 22:10 #navit: < tauso> Yes the fix works. 22:12 #navit: < tauso> but i didn't check out the new svn version, but rather edited the .c file and did a new "make" 22:12 #navit: <@KaZeR> yeah that'll do the job 22:12 #navit: < tauso> should be the same, as he only changed this :-D 22:16 #navit: < tauso> KaZeR could you explain me Commit [r5796]? whats the difference between attribute "text_background" and the old "background_color"? 22:22 #navit: <@KaZeR> i think that the difference is to be able to cast some kind of shadow behind your text, where the background color would put a solid background color for the whole text box 22:22 #navit: <@KaZeR> somehow like this : http://www.divine-project.com/wp-content/uploads/post_images/simple-shadow.jpg 22:22 #navit: <@KaZeR> and hence enhance readability over any kind of background 22:29 #navit: < tauso> that sounds good, but it isn't implemented yet, as only the header file is changed in the commit, am i right? 22:49 -!- tauso [~thomas@g226234248.adsl.alicedsl.de] has quit [Ping timeout: 260 seconds] 23:08 -!- tauso [~thomas@g225197250.adsl.alicedsl.de] has joined #navit 23:23 -!- KaZeR [~kazer@64.201.252.132] has quit [Ping timeout: 272 seconds] 23:31 -!- woglinde [~henning@e179037170.adsl.alicedsl.de] has quit [Ping timeout: 248 seconds] 23:35 -!- KaZeR [~kazer@c-67-161-64-186.hsd1.ca.comcast.net] has joined #navit 23:35 -!- mode/#navit [+o KaZeR] by ChanServ 23:47 -!- tauso [~thomas@g225197250.adsl.alicedsl.de] has left #navit [] --- Log closed Fri Jul 04 00:00:09 2014