--- Log opened Mon Jul 17 00:00:45 2017 00:25 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/android_armv5te/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/osm/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/wince_386/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/wince_cmake/svn/navit-svn-.failed http://download.navit-project.org/logs/navi 00:25 #navit: < Navit> ownload.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32_cmake/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32_gtk_cmake/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n800/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.faile 00:25 #navit: < Navit> gs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/iphone/svn/navit-svn-.failed 00:25 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html 01:47 -!- noradtux [~noradtux@2a02:2028:829:b901::1] has quit [Ping timeout: 276 seconds] 01:50 -!- noradtux [~noradtux@2a02:2028:635:ac01:5e1:912c:2d05:3170] has joined #navit 04:10 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit 06:13 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has joined #navit 06:13 #navit: < jfitie> @kazer, what do you think of https://github.com/navit-gps/navit/pull/279 ? 06:36 #navit: < jfitie> -> https://user-images.githubusercontent.com/23396293/28256976-7b04e598-6ac7-11e7-8581-f5b0c4ad7e41.png 07:15 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has quit [Quit: Page closed] 08:27 -!- pmckinley [~Peter_McK@88-110-210-211.dynamic.dsl.as9105.com] has joined #navit 08:29 -!- pmckinley [~Peter_McK@88-110-210-211.dynamic.dsl.as9105.com] has left #navit [] 08:53 -christel(christel@freenode/staff/exherbo.christel)- [Global Notice] Good morning freenode! We would like to invite projects (FOSS, peer-directed and companies alike) to come exhibit at the freenode #live conference in Bristol, UK on October 28-29th this year. Please see http://freenode.net/news/freenode-live-exhibit for further details. Registration and CFP are also open! Get involved! 11:15 #navit: < jkoan> jfitie I personally like it really much! 12:16 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has joined #navit 12:28 #navit: < jfitie> thanks jkoan 13:28 -!- jfitie [1f1830d0@gateway/web/freenode/ip.31.24.48.208] has quit [Quit: Page closed] 16:03 -!- noradtux [~noradtux@2a02:2028:635:ac01:5e1:912c:2d05:3170] has quit [Quit: Bye] 16:09 -!- jfitie [5c6e9fbe@gateway/web/freenode/ip.92.110.159.190] has joined #navit 16:12 #navit: < jfitie> @kazer where can I download the apk's generated by circleci? Would like to test 8c9d060ddd4cdc5f00c18d3997e2545d189456e5 for pr #279 ( https://circleci.com/gh/navit-gps/navit/2080?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link ) 16:14 -!- noradtux [~noradtux@port-22840.pppoe.wtnet.de] has joined #navit 16:19 #navit: <@KaZeR> hi there 16:26 #navit: < jfitie> hi 16:48 -!- noradtux [~noradtux@port-22840.pppoe.wtnet.de] has quit [Quit: Bye] 16:52 #navit: <@KaZeR> jfitie: nice work 16:54 #navit: <@KaZeR> we have to be careful with settings tweaks though : see robert's comment in https://github.com/navit-gps/navit/pull/66 16:54 #navit: < jfitie> Thanks, do you like the icons? Sleske has been working on some and I've tried to make the others look the same 16:55 #navit: <@KaZeR> yeah i really do like the icons 16:55 #navit: < jfitie> Will keep tweaking them 16:55 #navit: < jfitie> It's a lot 'cleaner' now 16:55 #navit: <@KaZeR> thanks this was really needed 16:56 -!- noradtux [~noradtux@port-22840.pppoe.wtnet.de] has joined #navit 16:56 #navit: <@KaZeR> regarding the apk : do you see the artifact tab in the circleci build? https://2080-30791823-gh.circle-artifacts.com/0/tmp/circle-artifacts.l4y2Qqk/navit-8c9d060ddd4cdc5f00c18d3997e2545d189456e5-arm-debug.apk 16:57 #navit: <@KaZeR> regarding the settings, i think that we should try to generate screenshots at various resolutions before merging, this will help us double check the impact of the change 16:57 #navit: < jfitie> Nope, I don't get that. Was looking for it but couldn't find it (I'm used to AppVeyor). Thanks for the link, will test. I''l take a look at that comment you referred to. 16:58 #navit: < jfitie> I think pitch is related to aspect ratio, correct? 16:59 #navit: < jfitie> I tested this (navit.pitch=5;) on 7 Android devices, all 16:9 and 16:10 16:59 #navit: <@KaZeR> i can grant you write access to the repo if you want, and then you should be able to see the artifact tab 17:01 #navit: <@KaZeR> according to robert's comment it's more related to the resolution, but i'd like to double check before merging. We could use "Xnest -geometry wxh" to spawn a X server with a given resolution and take screenshots, then move to the next resolution 17:02 #navit: < jfitie> Would be very interesting to see if results are the same with different resolutions with the same aspect ratio; f.ex. 800x600 vs 1920x1440 17:03 #navit: <@KaZeR> would you like to give it a try? :) 17:04 #navit: <@KaZeR> the gist of it is to start a server using "Xnest -geometry 800x600 :1" and then start navit using DISPLAY=:1 17:04 #navit: <@KaZeR> take a screenshot, rince, repeat for the next resolution 17:05 #navit: <@KaZeR> jkoan: would you like to help building a page to publish the artifacts? you're quite good with python so it should be easy 17:09 #navit: < jfitie> Wouldn't know where to start with that, I'll just use the little spare time I have further improving the icons :-). But I think you agree that the default pitch of 20 looks sh**t :-) https://user-images.githubusercontent.com/23396293/28256973-782eaa70-6ac7-11e7-9883-e3eeecafe8af.png 17:10 #navit: <@KaZeR> yeah i do agree, i even wanted to changed it last year but we need to get better at assessing the impact of changes, especially when they are about cosmetics as it's a matter of taste :) 17:11 #navit: <@KaZeR> jfitie: if you have 15 mins we can try to hack it together real quick. Could be a good primer for CI contributions :) 17:12 #navit: < jfitie> sure, how do we start 17:15 #navit: <@KaZeR> ok sweet. first of all : are you using circleci with your own fork? 17:15 #navit: <@KaZeR> also would you like write access to the main repo? 17:16 #navit: < jfitie> I don't have a circleci account yet; and I already have push access to the github repo 17:18 #navit: <@KaZeR> ok great. you don't need to create an account with circleci, you can log in using github's sso 17:18 #navit: <@KaZeR> so what we need to do is to edit https://github.com/navit-gps/navit/blob/trunk/ci/run_linux_tests.sh 17:18 #navit: <@KaZeR> before starting navit, we need to start Xnest in the background and keep its pid 17:19 #navit: <@KaZeR> then export the relevant DISPLAY value 17:20 #navit: <@KaZeR> then change the screenshot path so that it reflects the resolution we used on line 15, so maybe default-800x600.png for example 17:20 #navit: <@KaZeR> and we're almost done :) 17:20 #navit: < jfitie> ok, let me create a branch so I can try something 17:21 #navit: <@KaZeR> sure. we should always work in a branch anyway :) 17:26 #navit: < jfitie> https://github.com/navit-gps/navit/blob/screenshots/ci/run_linux_tests.sh 17:26 #navit: < jfitie> need more help :-) 17:26 #navit: <@KaZeR> i would put the xnest things in the linux_test function 17:27 #navit: <@KaZeR> it will make it easier to do a loop for each resolution we want to test 17:27 #navit: < jfitie> what do we need xnest for? 17:27 #navit: <@KaZeR> instead of just "Xnest" we need to add a geometry and a display number 17:28 #navit: <@KaZeR> xnest makes it easy to start a X server at a given resolution 17:28 #navit: < jfitie> I thought that's what the w= and h= parameters are for 17:29 #navit: <@KaZeR> parameters of what? 17:29 #navit: <@KaZeR> oh in navit.xml? 17:29 #navit: < jfitie> yeah 17:30 #navit: < jfitie> https://github.com/navit-gps/navit/blob/screenshots/ci/run_linux_tests.sh#L60 17:30 #navit: <@KaZeR> they won't work in fullscreen though 17:30 #navit: < jfitie> ah 17:30 #navit: <@KaZeR> well we could try without xnest and without fullscreen sure 17:30 #navit: < jfitie> what's the max resolution? 17:31 #navit: <@KaZeR> that's what's cool with Xnest : its resolution can be larger than your actually X resolution 17:31 #navit: <@KaZeR> the CI probably provides 1920x1080 if i recall correctly 17:31 #navit: <@KaZeR> but some tablets have a higher resolution 17:32 #navit: < jfitie> most phones do :-) 17:32 #navit: < jfitie> ok well sorry, but have to take a look at this at a later time - have to run soon 17:34 #navit: <@KaZeR> no worries 17:40 #navit: < jfitie> we could then just do some loop like for x in 1024 1280 1366 1920; do for y in 768 800 1024 1080; do echo "Create screenshots at $x x $y"; done; done 17:41 #navit: <@KaZeR> yep 17:41 #navit: <@KaZeR> i was thinking of using a specific set of resolutions, but this would work just as well 17:41 #navit: <@KaZeR> though i doubt that 1920x768 is commonly used :D 17:42 #navit: < jfitie> would be interesting to see all the different aspect rations though 17:42 #navit: < jfitie> *ratios 17:42 #navit: <@KaZeR> especially useful to test OSD layouts too 17:42 #navit: <@KaZeR> which means that we also need to test portrait layouts btw 17:43 #navit: <@KaZeR> so 1080x1920 for example 17:43 #navit: <@KaZeR> that's were Xnest comes in really handy :) 17:43 #navit: < jfitie> just create 2 arrays with x and y resolutions, swap them after looping through and run again 17:44 #navit: <@KaZeR> yep 17:44 #navit: < jfitie> gotta run, later 17:45 -!- jfitie [5c6e9fbe@gateway/web/freenode/ip.92.110.159.190] has quit [Quit: Page closed] 18:02 -!- rdorsch [~rdo@2a03:4000:6:52b6::] has quit [Read error: Connection reset by peer] 18:09 #navit: < Celelibi> Is there a free service for live traffic jam notification? 18:09 #navit: < Celelibi> Something that could be integrated with navit for those with permanent internet connection. 18:13 #navit: < Celelibi> (Well, if it's a google service, it would defeat most purpose of using navit in the first place.) 18:26 #navit: <@KaZeR> Celelibi: not that i know of. https://github.com/Nimrod007/waze-api could be a candidate, but it's non official and i'm not sure it's still maintained. Would be worth trying it 18:38 #navit: <@KaZeR> regarding google services, not sure that it would really defeat the purpose. If you want to minimaze your electronic footprint for example this would still be a valid use case 18:38 #navit: <@KaZeR> i like to use the googleplaces api from time to time for example. 18:39 #navit: <@KaZeR> minimaze. nice. 18:39 #navit: < Celelibi> Driving in my city is the opposite. It's a maxi-maze. :) 18:39 #navit: <@KaZeR> haha :) 18:40 #navit: <@KaZeR> i see that you also hang out in the #gdb channel. Have you seen my question there? 18:40 #navit: < Celelibi> Not yet. 18:41 #navit: < Celelibi> But yes, if you have a quite restricted mobile data, you might want to avoid downloading the map on the fly. 18:41 #navit: <@KaZeR> ok. you might be interested in this thread : http://trac.navit-project.org/ticket/570 18:42 #navit: < Celelibi> When was your initial question on #gdb? 18:43 #navit: <@KaZeR> two days ago maybe? 18:43 #navit: <@KaZeR> in a nutshell: 18:43 #navit: <@KaZeR> consider the following source code : https://github.com/navit-gps/navit/blob/trunk/navit/gui/internal/gui_internal_command.c#L510 18:43 #navit: <@KaZeR> and the following gdb session : https://pastebin.com/Wukb0NAE 18:43 #navit: <@KaZeR> why am i not seeing the code from lines 511-519 in my gdb debugging session? 18:47 #navit: < Celelibi> The source code doesn't seem to correspond to the debug session. Line 521 is not the right one. 18:50 #navit: < Celelibi> Other than that, gcc can reorder the evaluation and inline some functions. 18:51 #navit: < Celelibi> I'd suggest compiling with -O0 or -Og for debugging. 18:51 #navit: <@KaZeR> i added two debug lines at the beginning of the function, hence the offset :) 18:51 #navit: <@KaZeR> i am currenlty building with -O2 -g, will try -O0 thanks 18:55 #navit: < Celelibi> Where is defined mapset_next? 18:56 #navit: < Celelibi> Because it's surprising you don't see a call to mapset_next, map_get_attr and strstr in your gdb session. 19:04 #navit: <@KaZeR> -O0 seems to do the trick thanks : https://pastebin.com/zsCM5RYs 19:08 #navit: <@KaZeR> so for Zintor's issue with heightlines, this check never succeed : https://github.com/navit-gps/navit/blob/trunk/navit/gui/internal/gui_internal_command.c#L514 19:33 #navit: <@KaZeR> and that's because we should read the data_attr instead of the name_attr 22:35 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.] 22:49 -!- pmckinley [~Peter_McK@88-110-219-220.dynamic.dsl.as9105.com] has joined #navit 22:49 #navit: < pmckinley> :-D 22:49 #navit: < pmckinley> hey @KaZer 22:49 #navit: < pmckinley> :) 23:25 #navit: <@KaZeR> hey pmckinley ! 23:30 -!- Horwitz [~mich1@p200300800E1FD900022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 276 seconds] 23:43 -!- Horwitz [~mich1@p200300800E5BAD00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit 23:43 -!- mode/#navit [+o Horwitz] by ChanServ 23:53 -!- pmckinley [~Peter_McK@88-110-219-220.dynamic.dsl.as9105.com] has left #navit [] --- Log closed Tue Jul 18 00:00:47 2017