--- Log opened Mon Aug 04 00:00:41 2014
01:10 #navit: < Navit> The following compiles failed: http://download.navit-project.org/logs/navit/wince_arm/svn/navit-svn-5829.failed
01:10 #navit: < Navit> See compile results history at http://download.navit-project.org/logs/navit/stats.html
07:27 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
08:49 -!- drlizau [~liz@billiau.net] has joined #navit
08:55 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
11:22 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection]
12:09 -!- [1]bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
12:12 -!- latouche_ [~Latouche@reverse-169.fdn.fr] has joined #navit
12:18 -!- Netsplit *.net <-> *.split quits: bafplus, latouche
12:18 -!- [1]bafplus is now known as bafplus
12:40 -!- woglinde [~henning@g225149096.adsl.alicedsl.de] has joined #navit
12:45 -!- woglinde [~henning@g225149096.adsl.alicedsl.de] has quit [Ping timeout: 250 seconds]
12:46 -!- woglinde [~henning@g225149096.adsl.alicedsl.de] has joined #navit
12:50 -!- woglinde_ [~henning@e179190105.adsl.alicedsl.de] has joined #navit
12:52 -!- woglinde [~henning@g225149096.adsl.alicedsl.de] has quit [Ping timeout: 244 seconds]
12:53 -!- woglinde_ is now known as woglinde
16:04 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
16:05 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 256 seconds]
16:15 -!- tryagain [~quassel@178.216.76.73] has joined #navit
16:16 #navit: < tryagain> bafplus unfortunately we have no list of phrases besides source code. So you'll have to look at http://sourceforge.net/p/navit/code/HEAD/tree/trunk/navit/navit/navigation.c
16:17 #navit: < tryagain> translated phrases look like _("some text")
16:17 #navit: < tryagain> %s will be replaced with some text, %d with some number
16:33 #navit: < tryagain> bafplus see also vocabulary_name, vocabulary_name_systematic, vocabulary_distances at wiki.navit-project.org/index.php/Configuration/Full_list_of_options
16:33 #navit: < tryagain> it will help you reduce number of words to be recorded
16:34 #navit: < tryagain> please note: a single word.wav missing from the phrase will make navit not speak the whole phrase
16:35 #navit: < tryagain> afk
16:41 -!- pini [~pini@bou-fi.pustule.org] has joined #navit
16:54 -!- tauso [4e32d551@gateway/web/freenode/ip.78.50.213.81] has joined #navit
16:55 #navit: < tauso> hi, i try to use in my navit.xml, but it doesnt work on my android device. the extra xml file is located in the subfolder osd but it seams that it doesnt get included
16:56 #navit: < tauso> i use href\sdcard\navit\osd\navitosd.xml as href
16:59 #navit: < tauso> if I put the same code from the extra file into the navit.xml file its working. there i use some grahics with src="/sdcard/navit/osd_graphics/..." which are also working
17:17 -!- Mineque [~Mineque@89-68-233-84.dynamic.chello.pl] has joined #navit
17:20 #navit: < Mineque> hi
17:21 #navit: < woglinde> hi Mineque
17:40 #navit: < Mineque> hello woglinde
17:55 -!- woglinde_ [~henning@f052014198.adsl.alicedsl.de] has joined #navit
17:58 -!- woglinde [~henning@e179190105.adsl.alicedsl.de] has quit [Ping timeout: 244 seconds]
18:02 -!- Mineque [~Mineque@89-68-233-84.dynamic.chello.pl] has quit [Ping timeout: 255 seconds]
18:04 -!- Mineque [~Mineque@89-68-233-84.dynamic.chello.pl] has joined #navit
18:18 -!- KaZeR [~KaZeR@64.201.252.132] has joined #navit
18:20 -!- mode/#navit [+o KaZeR] by ChanServ
18:28 #navit: < bafplus> hi mineque
18:41 #navit: <@KaZeR> hi folks
18:42 -!- woglinde_ is now known as woglinde
18:53 #navit: < bafplus> Does anyone know the command to "speak" the current direction? Like if you miss the spoken direction and you want to hear it again, you can press the burron...
18:54 #navit: < bafplus> button....
18:56 #navit: < bafplus> i guess it would be the say() command + the correct syntax....
19:12 #navit: <@KaZeR> bafplus: try command="announce()"
19:13 #navit: <@KaZeR> i don't remember if it's a patch on my own navit instance of if it's a real feature tho, i'd have to check
19:20 #navit: < bafplus> That command is all there is? Nothing between the brackets?
19:27 #navit: <@KaZeR> that's how it is define in my own OSD layout and it works. but maybe i added a short dirty function to do that, i don't remember ( i can check later today once i'll get access to my carputer)
19:34 #navit: < bafplus> That would be nice, now it does nothing, log says: navit:command_call_function:invalid command ignored: "announce"; see http://wiki.navit-project.org/index.php/The_Navit_Command_Interface for valid commands
19:35 #navit: < bafplus> mind that i only can manage navit.xml, i don't have coding/build/compile skills ;-)
19:37 #navit: <@KaZeR> ok so i probably did write some kind of ugly workaround for this :) i won't have access to the carputer for a couple of hours tho
19:38 #navit: < Mineque> "dirty" "ugly"? KaZeR are you creating new episode of Shrek?
19:41 #navit: <@KaZeR> haha no. that could be cool, tho
19:46 #navit: < Mineque> we should create some navit puppet
19:47 #navit: < bafplus> yeah, and call him vavit (pr: naviet)
19:47 #navit: < Mineque> Norout
19:47 #navit: < Mineque> No route have been found
19:47 #navit: < Mineque> :P
19:48 #navit: < bafplus> @KaZeR, no probs...but i'm just thinking...what command is just from the source to invoke the current spoken direction?
19:50 #navit: < bafplus> another question...are there zipcodes available in the OSM map? Would be realy nice if you can look up youre destination using zipcode+housenumber just like with Garmin
19:50 #navit: <@KaZeR> iirc without looking at the code there is a say command. so the trick was to trigger a call to say, including the maneuver
19:50 #navit: < bafplus> I'm a service technician and i use this all the time to navigate to my costumers.
19:50 #navit: <@KaZeR> there are zip codes indeed. if you try the gtk gui, i believe you can search using zip codes
19:52 #navit: < bafplus> gtk doesent work in current windows version...
19:52 #navit: < bafplus> Is it a big deal to inplement this in the internal views?
19:52 #navit: <@KaZeR> ha
19:53 #navit: <@KaZeR> probably not
19:53 #navit: <@KaZeR> let me check trac to see if we have a ticket already
19:54 #navit: < bafplus> ehm...maybe strange idea but isnt the big difference between gtk and internal only the GUI? nat the source programm?
19:54 #navit: < Mineque> bafplus, there are just two different gui engines
19:54 #navit: < Mineque> realv MVC
19:54 #navit: < bafplus> ?
19:54 #navit: < Mineque> one core multiple independent View ;P
19:55 #navit: <@KaZeR> so if it works with gtk, it can work with internal :)
19:55 #navit: <@KaZeR> only possibly related ticket is http://trac.navit-project.org/ticket/1001
19:55 #navit: < bafplus> So the core is used in both, so if zipcode is possible in one it also should be in the other right5?
19:55 #navit: <@KaZeR> exactly
19:55 #navit: <@KaZeR> i have to go afk for lunch
19:56 #navit: < Mineque> KaZeR, enjoy
19:57 #navit: < bafplus> If not alrady a ticket, would somebody open it for me? my account is still not activated :-(
19:57 #navit: < bafplus> ow..and what does afk mean? ....
20:05 #navit: < Mineque> away from keyboard
20:06 #navit: < Mineque> bafplus, send me on private what do you want to be in the ticket
20:06 #navit: < Mineque> i'll add for you
20:11 #navit: < Mineque> bafplus, /msg Mineque blah blah blah
20:11 #navit: < Mineque> what client you use?
20:11 #navit: < Mineque> irc
20:18 #navit: < Mineque> added #1225
20:23 #navit: < bafplus> What are the plans with TMC, there is an open ticket reopend 13 months ago. Is there a way to implement this or is it already?
20:49 #navit: < bafplus> I'm a bit of a noob with coding..sorry for that... How to make this togle between car an car-dark layout?
20:49 #navit: < bafplus> i guess there is double ' " after command
20:54 #navit: < Mineque> but i'll check locally
20:54 #navit: < bafplus> yeah, but this is a single action button, i want it to toggle between the car and car-dark layout....
20:55 #navit: < Mineque> but day -> night or day <-> night
20:55 #navit: < Mineque> because first works for me
20:55 #navit: < Mineque>
20:56 #navit: < bafplus> day <-> night
20:56 #navit: < Mineque> then two option, or two osd item and hide/show after press second
20:56 #navit: < Mineque> or some variables state change
20:56 #navit: < Mineque> i guess possible
20:58 #navit: < bafplus> i think the first is the easiest ti implement... But what code to use to define the layout? (sorry for the noob questions)
21:00 #navit: < Mineque> code i've pasted works
21:00 #navit: < Mineque> not sure what about youre asking
21:01 #navit: < bafplus> it only works to go from day to night, but then in night view it should go back to day when pressed
21:02 #navit: < Mineque> it is possible
21:02 #navit: < Mineque> ask KaZeR when he'll back
21:02 #navit: < bafplus> i understand what you say to make 2 buttons, one for dayview, one for nightview. But how to display the button ONLY in nightview and vise versa?.
21:03 #navit: < bafplus> same thing like "osd_configuration="1"" but then targeting the layout
21:04 #navit: <@KaZeR> i'm back
21:04 #navit: < Mineque> bafplus, you need variables and/or command interface
21:04 #navit: < Mineque> KaZeR, help ^
21:05 #navit: <@KaZeR> actually bafplus you can have a button depending of a context ( depending of some kind of variable )
21:05 #navit: <@KaZeR> bafplus: please PM me the details of your wiki account i'll have a look
21:15 #navit: < bafplus> @KaZeR PM send
21:20 #navit: < bafplus> so how to define the variable for the layout? (simular to osd_configuration="1" or use_overlay="1" to define in wich layout each button is visable?))
21:29 #navit: < bafplus> next is copy/pested for log reference:
21:29 #navit: < bafplus> I want this button to do the same thing as the fullscreen button. Thw ico stays the same but pressed when in day(car) ->night(car-dark) and when in night(car-dark)->day(car)
21:29 #navit: < bafplus> i'v looked at the code for the fullscreen (or simular button) but i can't figure out the toggle command-string (mind that i'm not a coder by trade, i know what things do when i read it, but to write it myself is another thing)
21:29 #navit: < bafplus>
21:29 #navit: < bafplus> does what it is supposed to do, but only one-way.
21:29 #navit: < bafplus>
21:29 #navit: < bafplus> same thing...but how to "combine" these to by eather show only when in day or night view or by making it one "toggle" button simmular to the fullscreen button?
21:29 #navit: < bafplus> end copy-past....
21:42 #navit: <@KaZeR> actually i'm not sure that there is a toggle function for this as of now, because even if you can pair a night layout to a given layout ( eg. car and car-dark ) you could also choose to switch to a different night layout from the gui
21:42 #navit: <@KaZeR> i mean that we usually have more than two layouts available ( and more than two available by default )
21:42 #navit: <@KaZeR> i'm checking
21:43 #navit: <@KaZeR> e.g., if you use setting_layout() it will show you directly the layout selection menu, but not toggle to the night layout
21:44 #navit: <@KaZeR> one option would be to use gui variables tho
21:45 #navit: <@KaZeR> set_int_var(variable_name,int_value) could work in your use case
21:45 #navit: <@KaZeR> mmm
21:46 #navit: < bafplus> to make it "simple"...you can use osd_configuration="1" to only show the button when in navigation mode. i would guess that would also be possible to only show in one or the other layout
21:46 #navit: <@KaZeR> actually writing a osd script to switch from a mode to another could be even more painful than writing a function to do that directly from the code
21:46 #navit: < bafplus> @KaZeR...hu...don't forget im a coding noob...
21:47 #navit: <@KaZeR> bafplus: i was thinking out loud :) i can probably give this a shot
21:49 -!- drlizau [~liz@billiau.net] has joined #navit
21:50 #navit: < bafplus> If all else fails i can always make 2 buttons, one for day and one for night...but that would take up double space and a "zwitch to day" button when already in day-view would be a bit usseless ;-)
22:00 #navit: < Mineque> bafplus, there is another solution
22:00 #navit: < Mineque> i used to use years ago ;p
22:00 #navit: < Mineque> invisible button
22:00 #navit: < Mineque> create button above text layer
22:00 #navit: < Mineque> with transparent bg
22:01 #navit: < Mineque> you'll know where to press
22:01 #navit: < Mineque> and zero icons
22:01 #navit: < bafplus> i know, but my users don't ;-)
22:01 #navit: < Mineque> readme?
22:02 #navit: < bafplus> Yes Mineque, i see what you did with "hiding" the button, but like i said, i would know that, but my "end-users" don't.
22:03 #navit: < Mineque> who are your end users?
22:03 #navit: < Mineque> bafplus, tomtom has the same functionality
22:03 #navit: < Mineque> press where are time, km's, eta -> you'll see route map
22:03 #navit: < Mineque> press on firmware version
22:03 #navit: < Mineque> you'll get gps info
22:03 #navit: < Mineque> its typical
22:05 #navit: < bafplus> i work as a fiels-technicien, i'm using navit to direct all our engineers to the costumers...
22:06 #navit: < Mineque> impressive
22:06 #navit: <@KaZeR> nah let's fix that in the code
22:07 #navit: <@KaZeR> hidden features are fun, but easily usable software is better :)
22:07 #navit: < Mineque> KaZeR, so no dirty workarouand, even tiny one
22:08 #navit: < Mineque> KaZeR, even if you're allowed to have 100 icons it doesnt mean you have to have them
22:08 #navit: <@KaZeR> Mineque: hu?
22:08 #navit: < Mineque> i mean you cannot have icon for everything
22:08 #navit: < bafplus> does it have to be dirty? it seems to me that if it works with "full-screen" or "2D-3D" commands it would also work with this command or am i thinking to simple ...
22:09 #navit: < Mineque> btw wouldnt be better to just have timer to change automatic layouts?
22:09 #navit: < Mineque> like all commercial apps
22:09 #navit: < Mineque> bafplus, and why do you want to have button at all?
22:09 #navit: < Mineque> if there is option in mnu
22:10 #navit: < bafplus> thats just the thing...say its daytime but you're surrounding are dark, it would be nice to switch to darker view and vice versa...in short...its to OVERRIDE the timed-switch
22:12 #navit: < Mineque> ok
22:12 #navit: < Mineque> gn guys
22:13 #navit: <@KaZeR> bafplus: it does not have to be dirty. each layout can specify its counterpart ( ) so switching between two of them should be easy
22:13 #navit: < bafplus> if its easy...why can't i do it? ;-)
22:14 #navit: <@KaZeR> bafplus: because 1) our doc sucks (help / clarifications welcome ;) ) and 2) this is probably not implemented yet ( at least to my own knowledge )
22:15 #navit: < bafplus> to keep in coding language: if: car, then go car-dark, else: go dark
22:15 #navit: <@KaZeR> exactly. maybe s/go/use/ but that's the idea :)
22:17 #navit: < bafplus> I already have some nice additions/changes but as you know my account wassent verified yet...
22:17 -!- Mineque [~Mineque@89-68-233-84.dynamic.chello.pl] has quit [Ping timeout: 250 seconds]
22:18 #navit: < bafplus> i tried this, but possible made an error somewhere:
22:18 #navit: < bafplus>
22:19 #navit: < bafplus> if the above code would work correctly then you even can have corresponding icons
22:42 -!- woglinde [~henning@f052014198.adsl.alicedsl.de] has quit [Ping timeout: 245 seconds]
23:06 -!- tryagain [~quassel@178.216.76.73] has quit [Remote host closed the connection]
23:09 #navit: < bafplus> KaZeR , any luck yet?
23:11 #navit: <@KaZeR> sorry got caught into something else
23:11 #navit: <@KaZeR> actually a quick glance at your code example give me the feeling that it should work
23:13 #navit: < bafplus> but it doesent...maybe (just a thought) because it can't "check" the current status?
23:20 #navit: <@KaZeR> mmm actually your code does not contain an instruction to switch from a state to another
23:21 #navit: <@KaZeR> the layout_name part isn't dynamic. the button icon is dynamic but always set to daynight.png
23:22 #navit: < bafplus> The image part i'm not concerned about...that doesent involve with the actual command code
23:26 #navit: < bafplus> I got it partly working: it ONLY works when in day mode and switches to night, but not the other way around....
23:26 #navit: < bafplus>
23:29 #navit: < bafplus> It has to "read" the current status (i think) and doesent know if its day or night and switch to the corresponding layout...but thats a guess
23:35 #navit: <@KaZeR> so with this code you can switch from day to night, but then you're stuck in night, correct ?
23:38 #navit: < bafplus> no, sorry, its the other way around...when in night it goes to day, when in day it DOES NOT go to night
23:39 #navit: <@KaZeR> ha that makes more sense :)
23:39 #navit: <@KaZeR> because for the layout_name part you only set the "Car" value
23:40 #navit: <@KaZeR> btw : the car layout is an old layout you might want to try an alternative. I for example like to have the route on top of the layout, not underneath
23:40 #navit: < bafplus> one big diffenence is with fullscreen or 2d/3d that it can READ the current status ("1" or "0" i guess) depending on that it will switch. I guess it can not read the current status of the active layout
23:41 #navit: <@KaZeR> stab in the dark : layout_name="layout_name="Car-dark"==0?"Car":"Car-dark""
23:48 #navit: < bafplus> could you be so nice to paste that in the complete string?
23:50 #navit: <@KaZeR> sure. it's actually only to replace your layout_name="Car" line
23:50 #navit: <@KaZeR> but i'm installing navit on this host, to see if i can give it a try
23:54 #navit: < bafplus> This is going to be the last try for today...its alrady 1:50 AM...
--- Log closed Tue Aug 05 00:00:41 2014