--- Log opened Wed Nov 01 00:00:02 2017
00:00 #navit: < MarcR> so guys, see you later! have a good sleep!
00:00 #navit: < KaZeR> thanks MarcR you too!
00:00 #navit: < charles__> Later.
00:01 -!- MarcR [~MarcR@p5DD901E7.dip0.t-ipconnect.de] has quit []
00:01 #navit: < KaZeR> woopsie. /root/project/navit/gui/gtk/gui_gtk_statusbar.c:25:87: fatal error: gps.h: No such file or directory 
00:02 #navit: < KaZeR> visible from the CI test : https://circleci.com/gh/navit-gps/navit/3700 
00:02 #navit: < KaZeR> we should fix that but i need to step out for an hour or so
00:06 #navit: < charles__> OK, one failure. I #included gps.h to get a conversion factor. The linux build didn't like it.
00:06 #navit: < charles__> Let me see if I need it....
00:06 #navit: < KaZeR> i think that using navigation.h should have what we need for that
00:06 #navit: < KaZeR> yep
00:07 #navit: < KaZeR> and it's already included, so we probably just need to remove the gps.h include
00:07 #navit: < KaZeR> while we are at it, line 105 has the wrong indentation (4 instead of 8)
00:09 #navit: < KaZeR> i need to step out but i'll be back in a few. the PR will be updated automatically once you'll push a fix, we can resume from there
00:09 #navit: < charles__> Nope. Compile fails w/o gps.h. I use it in two places.
00:10 #navit: < charles__> METERS_TO_FEET is what killed it.
00:11 #navit: < charles__> Odd. Since navit uses gpsd on Linux, why does the test build not have it?
00:11 #navit: < charles__> Let me see what is in navigation.h.....
00:14 #navit: < KaZeR> well gpsd is a 'nice to have' but not a requirement
00:14 #navit: < KaZeR> afk back asap
00:16 #navit: < charles__> Ah. It should be a requirement. Get rid of all the reciever-specific cruft & all the NEMA crud.
00:16 #navit: < charles__> But that probably doesn't help on iOS or other OSs.
00:33 -!- Horwitz [~mich1@p200300800E000600022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 246 seconds]
00:38 #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-exp/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/src/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/openmoko/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/win32/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/n
00:38 #navit: < Navit> oad.navit-project.org/logs/navit/android_armv4t/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/android_x86/svn/navit-svn-.failed http://download.navit-project.org/logs/navit/tomtom/svn/navit-svn-.failed
00:39 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
00:42 #navit: < charles__> I just pushed a fix for the Linux build failure. I have not looked at the android one, but suspect it may be the same error.
00:43 #navit: < charles__> Nope. It's not due to calling gps.h. Anyone else want to look at that one?
00:46 #navit: < charles__> Time I got some dinner here.
00:47 -!- Horwitz [~mich1@p200300800E548300022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:47 -!- mode/#navit [+o Horwitz] by ChanServ
00:49 -!- ilovekiruna [~ilovekiru@h131n8-ll-a31.ias.bredband.telia.com] has quit [Ping timeout: 240 seconds]
00:56 #navit: < KaZeR> But that probably doesn't help on iOS or other OSs. -> exactly
00:57 #navit: < KaZeR> the android_x86 build fails from time to time for another reason. let's see
00:59 #navit: < KaZeR> also we should remove the include line instead of commenting it
01:08 #navit: < KaZeR> oh actually this ticket is still valid : http://trac.navit-project.org/ticket/780 just double checked
01:08 #navit: < KaZeR> so we have a bit more to fix regarding imperial in GTK
01:27 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 248 seconds]
01:34 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
02:09 #navit: < charles__> OK, deleted the #include line & pushed.
02:16 #navit: < charles__> I see the problem. Select a destination. Open the roadbook window (Display -> Roadbook). The first column (Command) is good for both feet and miles. The 4th column (Destination Length) is metric, m and km.
02:17 #navit: < charles__> (I'd have said, "destination distance".)
02:18 #navit: < charles__> I'll look into that later.
02:19 #navit: < charles__> Add column 2 (Length) to that.
02:48 -!- noradtux [~noradtux@2a04:4540:8c01:1c01:ec4:7aff:fe33:3dc1] has quit [Ping timeout: 264 seconds]
02:53 -!- noradtux [~noradtux@port-18613.pppoe.wtnet.de] has joined #navit
04:06 #navit: < KaZeR> thanks charles__ 
04:06 #navit: < KaZeR> remember that most of navit was written by non native english speakers, so maybe there's some oddities :)
04:07 #navit: < KaZeR> corrections are definitely welcome!
04:09 #navit: < KaZeR> PR merged, your code is now in the trunk!
05:05 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
05:46 #navit: < KaZeR> actually this code introduced an issue : http://trac.navit-project.org/ticket/1355#ticket we'll have to look into it.
06:24 #navit: < jkoan> For the icons in the wiki we can probably do some magic with circleci and the montage command. The only question is how to connect the wiki to circleci
06:25 #navit: < jkoan> Also again I need the Fdroid url, is it already finished? (and auto updating)
07:09 #navit: < KaZeR> for the wiki we can probably push a wiki update from circleci
07:09 #navit: < KaZeR> more work is required on fdroid, let's discuss it in a few hours
07:10 #navit: < KaZeR> last session on lambda was about versioning the work and making it reproducible via terraform : https://github.com/navit-gps/infrastructure/blob/master/terraform/lambda/fdroid.py and the other files in the same repo
08:08 -!- noradtux [~noradtux@port-18613.pppoe.wtnet.de] has quit [Ping timeout: 260 seconds]
08:12 -!- noradtux [~noradtux@2a04:4540:8c09:7d01:ec4:7aff:fe33:3dc1] has joined #navit
09:42 -!- ilovekiruna [~ilovekiru@h131n8-ll-a31.ias.bredband.telia.com] has joined #navit
11:30 -!- ilovekiruna [~ilovekiru@h131n8-ll-a31.ias.bredband.telia.com] has quit [Ping timeout: 240 seconds]
12:17 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Ping timeout: 248 seconds]
12:32 -!- jjardon_ [sid723@gateway/web/irccloud.com/x-jkitlrifgzmvqqsg] has joined #navit
12:42 -!- jjardon_ is now known as jjardon
12:52 -!- jjardon [sid723@gateway/web/irccloud.com/x-jkitlrifgzmvqqsg] has quit []
15:27 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
15:30 #navit: < charles__> KaZeR: Is it worth it to have the status bar initialization code (gui_gtk_statusbar_new) respect imperial? This shows up when the program launches, until the GPS receiver shows a fix (2d or 3d). So worst case, it could sit there for 20+ minutes while the receiver awaits an ephemeris from the satellites. The fix looks straightforward enough.
16:22 #navit: < KaZeR> charles__: good point!
16:23 #navit: < KaZeR> jkoan: for the fdroid url, we should test the current setup by hardcoding a new version. do you know what the next tag should look like? 
16:26 #navit: < jkoan> The next or the current? I would suggest put the current code from fdroid into, then wait for there merge and update the tag after it was released on GitHub
16:27 #navit: < KaZeR> but if we put the current we won't really know if it works, as it won't build, no?
16:29 #navit: < jkoan> Right, the other solution would be a temporary tag just for Fdroid
16:37 #navit: < KaZeR> do we have to use semver tags for fdroid? i was thinking of using tags like the ones we use for android
16:37 #navit: < KaZeR> and be able to update the builds between releases
16:50 -!- MarcR [~MarcR@p5DD903B2.dip0.t-ipconnect.de] has joined #navit
17:03 #navit: < KaZeR> jkoan: do you have access to the playstore console? a long time ago i registered us for the device labs automated tests, we have access now
17:04 #navit: < jkoan> I have access but don't know if also for devices labs, I will test later
17:04 #navit: < KaZeR> it means that when we upload a new apk some random actions will be tested. This generates screenshots, and it looks like on some devices we don't have the first use wizard
17:04 #navit: < KaZeR> ok
17:05 #navit: < jkoan> We even don't have a first use wizard. Or do you mean the dialog
17:07 #navit: < jkoan> I could not say if we really need semver for Fdroid, but in my opinion it would be better
17:08 #navit: < KaZeR> yeah i mean the first use dialog
17:08 #navit: < KaZeR> jkoan: how about 0.5.0-<timecode> then for fdroid?
17:08 #navit: < KaZeR> (that's the exact release tag that we use for android)
17:10 #navit: < jkoan> As tag inside the repo?
17:11 #navit: < charles__> OK, you should have branch roadbook.imperial.fix, which should fix bug #780.
17:12 #navit: < KaZeR> jkoan: we don't really need to store the tags anymore. unless i'm confused?
17:12 #navit: < KaZeR> thanks charles__ having a look
17:13 #navit: < jkoan> Probably I am also false, I must look again into it
17:14 #navit: < KaZeR> jkoan: if you give me one tag to test i can make it work right now :)
17:15 #navit: < jkoan> New Tag or old?
17:15 #navit: < KaZeR> charles__: would you mind fixing the indentation? https://github.com/navit-gps/navit/compare/roadbook.imperial.fix...trunk otherwise sometimes it gets confusing to read the code
17:15 #navit: < KaZeR> jkoan: new, otherwise, no build :)
17:15 #navit: < jkoan> Version name 0.5.0
17:16 #navit: < jkoan> And Version code current date in YYMMDDHHMM format
17:16 #navit: < KaZeR> charles__: otherwise the fix looks good, thanks!
17:19 #navit: < KaZeR> jkoan: https://epu5hjnir7.execute-api.us-west-2.amazonaws.com/prod/fdroid 
17:19 #navit: < jkoan> But have to do another change in the future. Right now the current system time is taken. In future we should use the last commit time instead.
17:21 #navit: < jkoan> But this should not break anything since in the moment where the change gets active a new commit is generated and this is newer than all before
17:23 -!- eto [~eto@unaffiliated/eto] has quit [Read error: Connection reset by peer]
17:25 -!- eto [~eto@unaffiliated/eto] has joined #navit
17:38 #navit: < charles__> I set Emacs to use K&R for C, and indent 8 spaces. That should fix that issue. I did not check for C95 correctness. commit 9de44afdd8c77ce668adea1c6ccb0340b51f73ef
17:38 #navit: < KaZeR> jkoan: exact
17:39 #navit: < KaZeR> thanks charles__ . we are probably going to drop C95 soon anyway as the wince build is broken
17:39 #navit: < KaZeR> unless Number6 manages to fix it. poke! poke! :)
17:41 #navit: < charles__> Does anyone still use Wince?
17:41 #navit: < KaZeR> we actually had someone who asked us to fix the build just a couple of weeks ago
17:41 #navit: < KaZeR> but yeah i wonder how long we can actually maintain it. the toolchain hasn't been updated since 2009
17:42 #navit: < KaZeR> sorry to be a pain but i still see a couple of indentation issues, line 2015 and 2022 for example
17:46 #navit: < charles__> OK, that *should* fix it.
17:47 #navit: < Number6> KaZeR: Spent the weekend and most of this week trying to get it working... no luck :-(
17:59 #navit: < KaZeR> charles__: thanks
17:59 #navit: < KaZeR> Number6: :(
18:02 #navit: < KaZeR> Number6: is all hope lost? 
18:02 #navit: < KaZeR> charles__: looking good! want to submit the PR for review? https://github.com/navit-gps/navit/compare/roadbook.imperial.fix...trunk
18:05 #navit: < Number6> KaZeR: I dunno, it would take a fair bit of work to recompile mingw32ce to work on a more modern system (I'm an ops guy, not a dev guy, so my coding isn't great). It might be possible, though
18:08 #navit: < KaZeR> yeah the question is, is it worth it...
18:18 #navit: < charles__> PR submitted. The Linux build failed while building the VM.
18:20 #navit: < KaZeR> Too long with no output (exceeded 10m0s) : looks like a circleci issue
18:20 -!- ilovekiruna [~ilovekiru@h131n8-ll-a31.ias.bredband.telia.com] has joined #navit
18:20 #navit: < KaZeR> hey ilovekiruna 
18:20 #navit: < KaZeR> ilovekiruna: https://firebase.google.com/pricing/ might be worth checking too
18:20 #navit: < ilovekiruna> hej KaZeR
18:21 #navit: < Number6> KaZeR: That's the question. Even most of the external GPC units on AliExpress / DX are android now - at least the ones that I have seen recently
18:21 #navit: < ilovekiruna> KaZeR: yes, sounds really pretty useful
18:21 #navit: < ilovekiruna> have you seen my additions to the old odp?
18:23 #navit: < KaZeR> Number6: yeah exactly. On the other hand, dropping support for our old time users with old times devices isn't what we do usually. Tough choice
18:23 #navit: < KaZeR> ilovekiruna: i haven't! i'll check in a minute
18:24 #navit: < KaZeR> Number6: are you aware of the fosdem discussion btw?
18:24 #navit: < Number6> KaZeR: WRT dropping support, indeed. Never a nice thing
18:24 #navit: < Number6> KaZeR: No, what's going on at FOSDEM?
18:25 #navit: < ilovekiruna> Number6: I thought of us submitting a main track session
18:25 #navit: < ilovekiruna> about navit testing
18:25 #navit: < Number6> ilovekiruna: Ohh, interesting! 
18:25 #navit: < ilovekiruna> KaZeR would also add sth on continious integration and build system
18:26 #navit: < ilovekiruna> Number6: maybe you also have some ideas or suggestions
18:26 #navit: < Number6> ilovekiruna: Lemmie have a think about it :-)
18:27 #navit: < ilovekiruna> Number6: there is a bit time pressure ;-) Deadline for submission is Friday
18:29 #navit: < Number6> ilovekiruna: Ah. I won't have anything ready by then - work has stolen every waking minute of my day for the last few months
18:31 #navit: < ilovekiruna> Number6: no problem
18:31 #navit: < ilovekiruna> hope we can repeat this now yearly
18:32 #navit: < KaZeR> Number6: maybe you can just share topics you'd talk about? just the big headline, we'll fill the content
18:32 #navit: < KaZeR> stuffs you liked working on, cool things we've done
18:33 #navit: < ilovekiruna> actually this is what i have done so far :(
18:36 #navit: < KaZeR> ilovekiruna: don't forget that we don't need the full deck by Friday, only a general idea :)
18:37 #navit: < ilovekiruna> KaZeR: why do you think so? Are you sure?
18:37 #navit: < ilovekiruna> KaZeR: i would like to have it in written form somehow
18:41 #navit: < KaZeR> ilovekiruna: that's based on the other confs i've submitted to. i might be wrong. I often am :)
18:42 #navit: < ilovekiruna> KaZeR: my experience from conferences i submitted to was, that the "paper" needs to be ready at submission time
18:42 #navit: < ilovekiruna> as we have no paper as such, i think it is important to have the presentation ready
18:42 #navit: < ilovekiruna> how could people at FOSDEM else judge if our work is worth presenting?
18:46 #navit: < KaZeR> then FOSDEM is doing a better selection than many "pro" conferences :)
18:47 #navit: < KaZeR> but i'll have some time to expand your slides today
18:48 #navit: < ilovekiruna> ok, nice
18:48 #navit: < ilovekiruna> I will also try to expand them now more in the evening
18:49 #navit: < ilovekiruna> just wanted to know your idea of my current notes
18:49 #navit: < ilovekiruna> in best case we can still change sth later on 
18:49 #navit: < ilovekiruna> in worst case i want to have at least i pretty content-wise complete draft
18:49 #navit: < ilovekiruna> design can wait ;-)
18:51 #navit: < KaZeR> do you want to restrict the scope to android? 
18:52 #navit: < ilovekiruna> that was rather a suggestion from jkoan
18:52 #navit: < KaZeR> we could talk also about how we test for other platforms. I think that it's important to emphasize that we are multi platform
18:52 #navit: < KaZeR> ha ok
18:52 #navit: < ilovekiruna> I can also live with a wider scope
18:52 #navit: < ilovekiruna> appium is more for mobile, so there i would say, we lack a bit of platform support ;-)
18:52 #navit: < ilovekiruna> u said iOS not working
18:53 #navit: < ilovekiruna> any news from xenos1984?
18:54 #navit: < KaZeR> no news yet from xenos1984 no
18:55 #navit: < KaZeR> my concern with focusing too much on android is that people might think that we are android only. we could also talk about our routing tests for example
18:55 #navit: < KaZeR> it needs some update but there's some cool features there : http://navit-gps.github.io/routing-qa/
18:56 #navit: < MarcR> KaZeR: Oh man. Found my mistake. the enable_expression does not support graphic files - only text labels.
18:59 -!- KaZeR [~kazer@ec2-54-70-178-135.us-west-2.compute.amazonaws.com] has quit [Quit: #purism]
18:59 #navit: < ilovekiruna> otherwise I would just re-create the slides for us
18:59 #navit: < ilovekiruna> I think it think i just make the slides new
18:59 #navit: < ilovekiruna> can you send me the link again?
18:59 -!- kazer [~kazer@ec2-54-70-178-135.us-west-2.compute.amazonaws.com] has joined #navit
18:59 #navit: < kazer> #mythtv-fr
19:00 #navit: < kazer> MarcR: oh good to know. Might be worth a note in the wiki maybe?
19:00 #navit: < MarcR> yeah. I have to find this out for myself. has cost me around 1h :P 
19:05 #navit: < kazer> ugh sorry :( 
19:06 #navit: < MarcR> not your fault, i hope ;-) no worries 
19:07 #navit: < MarcR> unix and own projects is always try and error . so ;-) 
19:08 #navit: < MarcR> kazer: how can i set a text break in a label? 
19:08 #navit: < kazer> I believe that \n should work no?
19:09 #navit: < MarcR> yeap
19:11 #navit: < kazer> cool. maybe a note in the wiki too? :D
19:11 #navit: < MarcR> :D
19:12 #navit: < MarcR> sweet - only navigation info if route is calculated. :-D 
19:14 #navit: < kazer> btw : we love screenshots / videos of users's setups!
19:14 #navit: < kazer> charles__: woopsie, it looks like your commits from today were pushed to trunk instead of a branch : https://github.com/navit-gps/navit/commits/trunk 
19:34 #navit: < charles__> Ouch. I thought I created a branch & told git to push all commits to it.
19:34 #navit: < charles__> Is that catastropic?
19:36 #navit: < kazer> not catastrophic, but we are trying to move away from doing this :)
19:37 #navit: < charles__> Yeah, good idea. Would you write up the work flow, w/ git commands, & add them to the programming wiki page? Thx
19:38 #navit: < kazer> yeah i'll do that sure!
19:38 #navit: < charles__> Thx
19:50 #navit: < ilovekiruna> youte: I wonder if you made a small mistake in your latest commit
19:51 #navit: < youte> ?
20:05 #navit: < MarcR> does anyone has the offical raspberry pi touchscreen casing where the pi is included? 
20:06 #navit: < ilovekiruna> youte: cant really tell now. It was strange that the mail i got about your merging mentioned weight instead of height
20:06 #navit: < ilovekiruna> but didnt find anything on it on github
20:09 #navit: < youte> in begining is error
20:10 #navit: < youte> the icons is height ...
20:10 #navit: < youte> no weight
20:10 #navit: < ilovekiruna> oh, ok, so you fixed it already :)
20:11 #navit: < youte> ^^
20:15 #navit: < kazer> MarcR: nop
20:15 #navit: < MarcR> kazer: hm ok. 
20:16 #navit: < MarcR> kazer: would be nice to know, how much extra space is in the case. 
20:16 #navit: < ilovekiruna> kazer: which other platforms would u like in the title? or strap just android?
20:40 #navit: < ilovekiruna> do we have some more uptodate screenshots compared to slide 5 in http://sotm-baltics.org/slides/sun_1100_hohmann.pdf ?
21:14 #navit: < MarcR> I think, my navit is ready for some action :) 
21:24 #navit: < kazer> ilovekiruna: yeah i'd just remove android from the title. Also, maybe we should use a doc to bounce off ideas, and then build the presentation from there? Slides don't make it easy to write up content
21:24 #navit: < kazer> MarcR: nice! don't forget the pictures/videos!
21:24 #navit: < ilovekiruna> kazer: I worked on the presentation quite a bit. Added the slides by xenos1984
21:25 #navit: < ilovekiruna> maybe u can have a look
21:25 #navit: < ilovekiruna> slowly it looks like sth
21:25 #navit: < ilovekiruna> if you want to doc ideas, sure, go ahaed
21:25 #navit: < kazer> ilovekiruna: ok checking. I can take picture of navit on a few devices too
21:25 #navit: < ilovekiruna> potential better than the pics i "stole" from the old presentation
21:27 #navit: < kazer> i have a nexus 5 and a sony tablet, at least it'll look more modern :)
21:29 #navit: < MarcR> kazer: will do
21:29 #navit: < ilovekiruna> great :)
21:30 #navit: < ilovekiruna> kazer: great
21:30 #navit: < ilovekiruna> kazer: do you see the latest version already? or do i need to close the file?
21:31 #navit: < kazer> i see it, and am making minor changes
21:32 #navit: < ilovekiruna> kazer: can we edit simultaneously??
21:34 #navit: < kazer> i don't think that we can. It'll probably create version files. Let me drop my changes, i'll have a look again once you'll be done
21:34 #navit: < kazer> done
21:35 #navit: < MarcR> kazer: my own touch interface like kodi - qt5 ? 
21:39 #navit: < kazer> MarcR: what do you mean?
21:40 #navit: < MarcR> I would like to have my own touch interface to control my carpi - switch to navi - turn radio on - answer calls 
21:40 #navit: < MarcR> etc
21:40 #navit: < kazer> ah! are you asking about qtdesigner and qt5 ?
21:40 #navit: < MarcR> got it
21:41 #navit: < kazer> ok. so, if you look into this folder : https://github.com/navit-gps/navit/tree/trunk/navit/gui/qt5_qml/editor 
21:42 #navit: < kazer> you should be able to open that project with qtcreator / qtdesigner
21:42 #navit: < MarcR> ok 
21:43 #navit: < kazer> i'd recommend reading a bit about qml (we use qml2, but it doesn't matter much) to understand the ideas, but in short this is for example how we define the address search dialog :
21:43 #navit: < kazer> https://github.com/navit-gps/navit/blob/trunk/navit/gui/qt5_qml/skins/modern/destination_address.qml
21:43 #navit: < kazer> 3 buttons (city, street, country) inside a grid layout
21:46 #navit: < MarcR> Ok. I will take a look at it 
21:46 #navit: < kazer> this is what defines the look when we start the app : https://github.com/navit-gps/navit/blob/trunk/navit/gui/qt5_qml/skins/modern/main.qml 
21:46 #navit: < kazer> currently we start by showing the map by default but you can change that by editing this file for example
21:46 #navit: < kazer> or add any button that you want to be visible on top of the map, etc
21:50 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
21:50 #navit: < MarcR> sounds interesting, I will install qtdesigner and start designing 
21:51 #navit: < kazer> awesome. ask away if you have any question
21:57 #navit: < MarcR> ok qt creator is to much for the pi :-P 
21:57 #navit: < MarcR> but no problem, I'm installing it on my main pc atm
21:58 #navit: < kazer> haha yeah no it's going to be painful on the pi :)
21:58 #navit: < MarcR> it is ;) 
22:07 #navit: < ilovekiruna> kazer: was away a bit, didnt see your message, will save under new name now
22:08 #navit: < kazer> no need to user a different name ilovekiruna 
22:08 #navit: < ilovekiruna> i had the file open the whole time
22:09 #navit: < ilovekiruna> i think i will continue tomorrow
22:09 #navit: < ilovekiruna> close the file now
22:11 #navit: < kazer> ok, will get back to it in a moment, thanks
23:11 -!- ilovekiruna [~ilovekiru@h131n8-ll-a31.ias.bredband.telia.com] has quit [Ping timeout: 248 seconds]
23:22 #navit: < MarcR> guys have a good sleep
23:22 #navit: < MarcR> see you later 
23:23 #navit: < kazer> ++ MarcR 
23:24 -!- MarcR [~MarcR@p5DD903B2.dip0.t-ipconnect.de] has quit []
23:26 #navit: < charles__> kazer: Re http://trac.navit-project.org/ticket/1355: Would this solve it: "imperial == TRUE ? speed / (METERS_PER_MILE / 1000.0) : speed,"
23:33 #navit: < kazer> charles__: i think it should yeah
23:34 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has quit [Ping timeout: 246 seconds]
23:36 #navit: < charles__> It depends on the compiler promoting METERS_PER_MILE to a float, and carrying out the resulting arithmetic all as floats.
23:37 #navit: < charles__> OK, I'm out of here for the night.
23:38 #navit: < kazer> i believe that it should be the expected behavior yeah
23:38 #navit: < kazer> bye charles__ !
23:42 -!- j_f-f [~quassel@rs-7.jff-webhosting.net] has joined #navit
--- Log closed Thu Nov 02 00:00:04 2017