--- Log opened Fri Jan 20 00:00:16 2017
02:35 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
02:49 -!- Navit` [~Navit@www.v6.navit-project.org] has joined #navit
02:51 -!- Navit [~Navit@www.v6.navit-project.org] has quit [Ping timeout: 240 seconds]
03:10 -!- jjelen [jjelen@nat/redhat/x-ssutprggykvcjrki] has joined #navit
04:07 -!- jjelen [jjelen@nat/redhat/x-ssutprggykvcjrki] has quit [Ping timeout: 255 seconds]
04:22 -!- jjelen [jjelen@nat/redhat/x-qalbkxbrqviatbax] has joined #navit
05:20 -!- jkoan [~jan@ip4d1412e1.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds]
05:33 -!- jjelen [jjelen@nat/redhat/x-qalbkxbrqviatbax] has quit [Ping timeout: 240 seconds]
05:45 -!- jjelen [jjelen@nat/redhat/x-zvmiqaffmcgkdxxn] has joined #navit
05:52 -!- jkoan [~jan@ip4d1412e1.dynamic.kabel-deutschland.de] has joined #navit
05:58 -!- jkoan [~jan@ip4d1412e1.dynamic.kabel-deutschland.de] has quit [Read error: No route to host]
06:13 -!- jkoan [~jan@ip4d1412e1.dynamic.kabel-deutschland.de] has joined #navit
06:19 -!- jjelen [jjelen@nat/redhat/x-zvmiqaffmcgkdxxn] has quit [Ping timeout: 240 seconds]
06:34 -!- jjelen [jjelen@nat/redhat/x-pcimutudwowupkzi] has joined #navit
07:15 -!- jjelen [jjelen@nat/redhat/x-pcimutudwowupkzi] has quit [Ping timeout: 240 seconds]
07:16 -!- jjelen [jjelen@nat/redhat/x-xofgxhxefqsotuai] has joined #navit
07:38 -!- jkoan [~jan@ip4d1412e1.dynamic.kabel-deutschland.de] has quit [Read error: No route to host]
07:57 -!- jkoan [~jan@ip4d1412e1.dynamic.kabel-deutschland.de] has joined #navit
09:18 -!- Jkoan2 [~jkoan@ip-109-45-0-163.web.vodafone.de] has joined #navit
09:39 -!- jjelen [jjelen@nat/redhat/x-xofgxhxefqsotuai] has quit [Quit: Leaving]
09:41 -!- jjelen [jjelen@nat/redhat/x-anccrayhcbufwnvt] has joined #navit
10:14 -!- Jkoan2 [~jkoan@ip-109-45-0-163.web.vodafone.de] has quit [Ping timeout: 240 seconds]
10:26 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
11:38 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
12:08 -!- jjelen [jjelen@nat/redhat/x-anccrayhcbufwnvt] has quit [Ping timeout: 240 seconds]
12:10 #navit: < KaZeR> hi there
12:41 -!- circleci-bot [~circleci-@ec2-54-224-138-24.compute-1.amazonaws.com] has joined #navit
12:41 #navit: < circleci-bot> Failed: pgrandin's build (#1570; retry by pgrandin) in navit-gps/navit (add_linux_tests) -- https://circleci.com/gh/navit-gps/navit/1570?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc
12:41 -!- circleci-bot [~circleci-@ec2-54-224-138-24.compute-1.amazonaws.com] has quit [Client Quit]
13:02 -!- ZeroOne [~ZeroOne@91.114.11.118] has joined #navit
13:32 -!- circleci-bot [~circleci-@ec2-54-161-8-142.compute-1.amazonaws.com] has joined #navit
13:32 #navit: < circleci-bot> Canceled: pgrandin's build (#1571; ssh by pgrandin) in navit-gps/navit (add_linux_tests) -- https://circleci.com/gh/navit-gps/navit/1571?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc
13:32 -!- circleci-bot [~circleci-@ec2-54-161-8-142.compute-1.amazonaws.com] has quit [Client Quit]
13:45 -!- jandegr [5bb34124@gateway/web/freenode/ip.91.179.65.36] has joined #navit
13:49 -!- circleci-bot [~circleci-@ec2-54-80-46-124.compute-1.amazonaws.com] has joined #navit
13:49 #navit: < circleci-bot> Success: pgrandin's build (#1572; push) in navit-gps/navit (add_linux_tests) -- https://circleci.com/gh/navit-gps/navit/1572?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc
13:49 -!- circleci-bot [~circleci-@ec2-54-80-46-124.compute-1.amazonaws.com] has quit [Client Quit]
13:53 #navit: < KaZeR> hi jandegr
13:53 #navit: < jandegr> hi kazer
13:54 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has joined #navit
13:54 #navit: < zintor> hi @all
13:56 #navit: < zintor> I uploaded an animated gif showing navit running SailfishOS
13:56 #navit: < zintor> http://wiki.navit-project.org/images/0/0d/Navit-sailfish-output320.gif
13:56 #navit: < zintor> maybe too small :(
14:00 -!- circleci-bot [~circleci-@ec2-54-211-115-127.compute-1.amazonaws.com] has joined #navit
14:00 #navit: < circleci-bot> Failed: pgrandin's build (#1573; push) in navit-gps/navit (linux-network-info) -- https://circleci.com/gh/navit-gps/navit/1573?utm_campaign=chatroom-integration&utm_medium=referral&utm_source=irc
14:00 -!- circleci-bot [~circleci-@ec2-54-211-115-127.compute-1.amazonaws.com] has quit [Client Quit]
14:10 #navit: < KaZeR> hi zintor
14:10 #navit: < zintor> hi KaZeR
14:10 #navit: < KaZeR> might be a bit small indeed :)
14:10 #navit: < KaZeR> can you please share the original video? i can give it a shot
14:11 #navit: < zintor> hmpf, I have another MOV, but I am not able to rotate!?!
14:11 #navit: < zintor> I use this command:
14:11 #navit: < zintor> avconv -i ~/git/navit-jolla-layout/P1200357.MOV -vf scale=320:-1 -r 10 -f image2pipe -vcodec ppm - | convert -delay 0 -loop 0 - gif:- | convert -layers Optimize - ~/git/navit-jolla-layout/output.gif
14:11 #navit: < zintor> but i was not able to find how to rotate
14:12 #navit: < zintor> https://libav.org/avconv.html#transpose
14:12 #navit: < zintor> it is described, but where to put?
14:12 #navit: < KaZeR> you can reduce the framerate even more, gps updates are usually 1Hz, so 1 fps makes sense
14:14 #navit: < KaZeR> jkoan is currently reworking the wiki, but i think this is a good candidate for the screenshot gallery
14:15 #navit: < zintor> after I uploaded a better one ;)
14:15 #navit: < KaZeR> sure :)
14:16 #navit: < zintor> do you know how to rotate in avconv ?
14:16 #navit: < KaZeR> if we get a good one i'd love to post it on social medias :)
14:17 #navit: < KaZeR> not familiar with avconv but i was reading the page you shared
14:17 #navit: < zintor> ffmpeg is mostly the same prog
14:20 #navit: < KaZeR> actually i don't think that you should rotate that video
14:20 #navit: < KaZeR> maybe crop the borders to hide the unused parts
14:21 #navit: < zintor> or rotate with convert md
14:21 #navit: < zintor> cmd
14:22 #navit: < KaZeR> the thing is that your phone is setup for portrait mode :)
14:22 #navit: < zintor> yes
14:24 #navit: < zintor> if i rotate my phone with running navit, it does not rotate
14:26 #navit: < zintor> well...convert did the job :)
14:26 #navit: < KaZeR> ah! link?
14:30 #navit: < jandegr> zintor I modified the qt5 graphics driver from sailfish a bit to work on desktop linux and I had the impression that rotate/resize was not implemented
14:31 #navit: < zintor> hi jandegr
14:31 #navit: < zintor> that would explain, why it diesn't rotate
14:31 #navit: < jandegr> had to add some stuff to let it work (and resize ) in a desktop window
14:31 #navit: < zintor> https://github.com/zintor/navit-jolla-layout/blob/master/screenshots/output90_2.gif
14:33 #navit: < jkoan> nice gif
14:34 #navit: < zintor> thx
14:34 #navit: < zintor> I have to questions:
14:35 #navit: < jkoan> yes? :D
14:35 #navit: < zintor> sound on/off is not working. I used button command='volume_toggle()'
14:37 #navit: < zintor> it is not working. wait a sec, I will post the message
14:37 #navit: < zintor> error:navit:command_call_function:invalid command ignored: "volume_toggle"; see http://wiki.navit-project.org/index.php/OSD#Navit_commands for valid commands.
14:38 #navit: < zintor> could it be, that it is missing in metalstrolch's fork?
14:39 -!- jandegr [5bb34124@gateway/web/freenode/ip.91.179.65.36] has quit [Quit: Page closed]
14:42 #navit: < jkoan> probably because there is no command volume_toggle ;) i dont even know enough about sound system right now, but kazer probably know an anser
14:43 #navit: < zintor> type="toggle_announcer" is also not working, when I click on it, it is the same as I click on the map
14:44 #navit: < KaZeR> zintor: yes you would need the audio_framework branch for that
14:45 #navit: < KaZeR> zintor: could you reduce the framerate and augment the resolution in the gif to make it more legible?
14:45 #navit: < zintor> will do
14:45 #navit: < KaZeR> toggle_announcer should work. the audio_framework is needed for volume_toggle
14:46 #navit: < KaZeR> also, what about enabling follow=1 and refresh=1 so that the map keeps being centered? (just a thought)
14:46 #navit: < zintor> that was my 2nd question. answered...thx
14:46 #navit: < KaZeR> :)
14:46 #navit: < zintor> I forgot refresh :(
14:47 #navit: < KaZeR> yeah we should make that toggable from the UI
14:48 #navit: < zintor> I would be happy, if I could do some tests with qml...any answer from metalstrolch?
14:49 #navit: < KaZeR> crap, i forgot. Doing it now
14:51 #navit: < KaZeR> done. Also asked him if he could ping you on IRC
14:53 #navit: < zintor> thx
14:54 #navit: < zintor> is that icon ok for "navit-sailfish-app"-icon? http://wiki.navit-project.org/images/7/79/Icon-SailfishOS.svg
14:55 #navit: < KaZeR> looks good to me
14:56 #navit: < KaZeR> i spotted this set of icons too lately : https://github.com/elementary/icons and was considering using them for a theme/skin in the future
14:57 #navit: < jkoan> probably someone can make an paper design theme (like andriod) that would be nice
14:58 #navit: < zintor> well...I am working on SailfishOS ;)
14:58 #navit: < jkoan> oh sorry i mean material design
14:59 #navit: < zintor> I like these ones: http://linea.io/ and these https://useiconic.com/open
14:59 #navit: < jkoan> https://raw.githubusercontent.com/zintor/navit-jolla-layout/master/screenshots/screenshot.png is this a prewiev?
15:00 -!- Basilic__ [~Basilic@228-221-190-109.dsl.ovh.fr] has joined #navit
15:00 #navit: < KaZeR> zintor: yep they look good. I sometimes have mixed feelings about monochrome icons, but i guess it depends how we use them
15:00 #navit: < jkoan> looks good, but this is not material design :D
15:00 #navit: < zintor> I am going to upload another one with content in the 2nd line under "Hohenzollenstraße"
15:01 #navit: < KaZeR> zintor: your icons would make perfect sense in the OSD for example
15:01 #navit: < zintor> that's right, it always depends
15:01 #navit: < KaZeR> i could definitely reuse the music icons from linea.io in my nuc OSD :)
15:02 #navit: < zintor> *thumbsup*
15:03 #navit: < KaZeR> https://github.com/navit-gps/navitosd-1 is a good example of a OSD-centric repository
15:03 -!- Basilic_ [~Basilic@228-221-190-109.dsl.ovh.fr] has quit [Ping timeout: 245 seconds]
15:07 #navit: < zintor> good
15:08 #navit: < zintor> do i understand it right:
15:08 -!- ZeroOne [~ZeroOne@91.114.11.118] has quit [Ping timeout: 255 seconds]
15:08 #navit: < zintor> this repo for all upcoming OSDs
15:09 #navit: < zintor> and the device-depentend files are in the branch
15:10 #navit: < zintor> so we have branches: Carputer, Android, SailfishOS,...
15:10 #navit: < zintor> "could have"
15:10 #navit: < KaZeR> mmm. my intent was rather to have one repo per OSD layout, it would make it easier for people to contribute maybe ?
15:11 #navit: < KaZeR> this is open for discussion of course
15:11 #navit: < KaZeR> and then we could group them as submodules in https://github.com/navit-gps/layouts
15:11 #navit: < KaZeR> and ideally, download them directly from within navit by reading the content of this repo, maybe even displaying a snapshot or something before downloading
15:17 #navit: < zintor> you know: I am new to github ;) if one repo per osd is easier: let it go.
15:17 #navit: < zintor> i do not know about submodules... ;)
15:18 #navit: < zintor> follow="1" is not possible in source="demo://"?
15:19 #navit: < zintor> error:vehicle_demo:vehicle_demo_set_attr_do:unsupported attribute follow
15:21 #navit: < KaZeR> one repo per osd makes it easier to test and generate automated captures
15:21 #navit: < KaZeR> git submodules are actually easy : you just create a 'link' between your repo and something external. this is great to manage dependencies for example
15:22 #navit: < KaZeR> i think that the demo vehicle has follow enabled by default.. we should fix that message though
15:22 #navit: < zintor> I am ok with it
15:22 #navit: < zintor> well...my uploaded gif was made with demo vehicle
15:24 #navit: < zintor> just with this:
15:24 #navit: < zintor>
15:24 #navit: < KaZeR> you probably need refresh=1 which means refresh the map every 1 updates
15:25 #navit: < KaZeR> we should probably add that as a default once you confirmed that it works. Could be your second PR :)
15:26 #navit: < zintor> refresh is also unsupported
15:26 #navit: < KaZeR> let me check
15:26 #navit: < zintor> and refresh is not an option described in the wiki
15:26 #navit: < zintor> http://wiki.navit-project.org/index.php/Configuration/Vehicle_Options#Vehicle_Options
15:30 #navit: < KaZeR> ha interesting.
15:31 #navit: < KaZeR> i did the test. navit will complain about follow=1 on the demo vehicle, but it actually works
15:31 #navit: < KaZeR> same for active
15:32 #navit: < zintor> oookay...need a PR to supress the messages?
15:32 #navit: < KaZeR> PR are intended to submit a fix, but i can walk you through it
15:33 #navit: < KaZeR> looking at the code...
15:37 #navit: < zintor> follow and refresh are working withe source demo ok here, too ;)
15:38 #navit: < KaZeR> cool
15:39 #navit: < KaZeR> it usually looks better when it's enabled. Disabling it was intended for very low-power devices which couldn't keep refreshing every second
15:39 #navit: < zintor> agreed
15:39 #navit: < KaZeR> ha, the follow fix for demo is not as easy as i expected
15:39 #navit: < zintor> well..I do not have a development environment installed. searching could be not so easy.
15:41 #navit: < zintor> to be fair, I would like to finish OSD, first.
15:42 #navit: < zintor> could you imagine, why toggle_announcer is not working?
15:43 #navit: < KaZeR> i created http://trac.navit-project.org/ticket/1347 to keep track of that issue
15:43 #navit: < KaZeR> we can have a look
15:43 #navit: < KaZeR> (that issue = follow and active on Demo vehicle)
15:44 #navit: < KaZeR> for the toggle_announcer, can you share your osd line?
15:44 #navit: < zintor> I get following message for refresh:
15:44 #navit: < zintor> error:navit:convert_to_attrs:failed to create attribute 'refresh' with value '1'
15:44 #navit: < zintor> folow:
15:44 #navit: < zintor> error:vehicle_demo:vehicle_demo_set_attr_do:unsupported attribute follow
15:45 #navit: < zintor> two different things?
15:46 #navit: < KaZeR> mmm. i'll expand the ticket with the exact messages :)
15:46 #navit: < KaZeR> actually you don't need refresh for Demo. active and follow should be enough
15:47 #navit: < zintor> givr it a try
15:48 #navit: < KaZeR> ah no you do need refresh :)
15:48 #navit: < zintor> tsts
15:49 #navit: < zintor> for toggle_announcer: i use SVGs...maybe that's why it doesn't work...give me a sec
15:50 #navit: < KaZeR> svg should not impact your ability to use a command, but we'll find what is going on :)
15:52 #navit: < zintor>
15:52 #navit: < zintor> with the files "gui_sound.svg" and "gui_sound_off.svg" in that dir
15:54 #navit: < zintor> without the icon_src, it show the default ones
15:59 #navit: < KaZeR> do the default icon switch when you click it?
15:59 #navit: < zintor> no
15:59 #navit: < zintor> PNGs are also not working
15:59 #navit: < zintor> when I click, the menu opens
16:00 #navit: < zintor> main menu
16:02 #navit: < zintor> these messages appears, but also then I click on a osd woth type "text":
16:02 #navit: < zintor> [W] QFSFileEngine::open:206 - QFSFileEngine::open: No file name specified
16:02 #navit: < zintor> [D] createImageNode:2712 - couldn't create image from ""
16:07 #navit: < KaZeR> argh the wiki is crapping out
16:10 #navit: < zintor> :(
16:15 #navit: < KaZeR> mmm, without using custom icons it works for me
16:15 #navit: < KaZeR> icons are switching, and the announcer is disabled when it should
16:20 #navit: < zintor> not for me. :( I also moved it to navit.xml
16:23 #navit: < zintor> something to do with metalstrolch's fork?
16:24 #navit: < zintor> well, found some "toggle_announcer" in file "osd_core.c"
16:25 #navit: < KaZeR> it should not be related to the fork, metalstrolch's fork should only be about gui and graphics
16:26 #navit: < KaZeR> when you have the default icons, clicking on the item just sends you to the main menu, correct?
16:26 #navit: < KaZeR> are other OSD items clickable? like zoom buttons?
16:27 #navit: < KaZeR> or are they all sending you to the main menu?
16:28 #navit: < zintor> yes, correct. default (also user-defined) icons sends me to main menu.
16:28 #navit: < zintor> zoom buttons are ok.
16:28 #navit: < zintor> they zoom
16:29 #navit: < KaZeR> mmm really odd
16:30 #navit: < zintor> agreed
16:33 #navit: < zintor> could I narrow the problem somewhere else?
16:34 #navit: < KaZeR> yep
16:34 #navit: < KaZeR> can you try to add this :
16:34 #navit: < KaZeR>
16:34 #navit: < KaZeR>
16:34 #navit: < KaZeR> after your plugins definitions, like after
16:35 #navit: < KaZeR> when clicking the icon, i get debug:navit:osd_evaluate_command:calling command 'announcer_toggle()'
16:35 #navit: < KaZeR> d
16:35 #navit: < KaZeR> it tells us that the click was processed by the OSD
16:39 #navit: < zintor> unfortunately nothing here. just:
16:39 #navit: < zintor> debug:osd_core:osd_nav_toggle_announcer_draw:gr_image=0x9a95e10
16:39 #navit: < zintor> [W] QFSFileEngine::open:206 - QFSFileEngine::open: No file name specified
16:39 #navit: < zintor> [D] createImageNode:2712 - couldn't create image from ""
16:39 #navit: < KaZeR> ok so your click event is not propagated to the OSD items
16:40 #navit: < KaZeR> if zoom buttons were not working i would have a clue.. but this one is really odd
16:40 #navit: < zintor> I will do it with zoom, just for testing
16:41 #navit: < KaZeR> ok
16:41 #navit: < KaZeR> good call
16:44 #navit: < zintor> sry. do not know, which debug info to write (i tried to find some...)
16:44 #navit: < KaZeR> navit:osd_evaluate_command should be enough i think
16:44 #navit: < KaZeR> yep
16:44 #navit: < KaZeR> debug:navit:osd_evaluate_command:calling command 'zoom_in()'
16:45 #navit: < KaZeR> almost food time here, will have to go afk a few soon
16:45 #navit: < zintor> ok
16:45 #navit: < zintor> guten appetit! :)
16:45 #navit: < KaZeR> danke :)
16:47 #navit: < zintor> click on zoom writes:
16:47 #navit: < zintor> debug:navit:osd_evaluate_command:calling command 'zoom_in()'
16:47 #navit: < zintor> that's ok
16:49 #navit: < KaZeR> ok that's helpful. We'll have to dig.. If you want to look into it, navit debug is quite powerful
16:49 #navit: < KaZeR> afk a few
17:16 #navit: * zintor have to go to bed
17:16 #navit: < zintor> gn8 all
17:16 -!- zintor [~steffen@HSI-KBW-46-223-225-142.hsi.kabel-badenwuerttemberg.de] has left #navit []
17:51 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
19:41 -!- Horwitz [~mich1@p200300800E031500022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 276 seconds]
19:54 -!- Horwitz [~mich1@p200300800E0B4100022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
19:54 -!- mode/#navit [+o Horwitz] by ChanServ
22:03 -!- noradtux [~noradtux@port-57027.pppoe.wtnet.de] has quit [Ping timeout: 255 seconds]
22:08 -!- noradtux [~noradtux@port-32560.pppoe.wtnet.de] has joined #navit
--- Log closed Sat Jan 21 00:00:18 2017