--- Log opened Wed Jun 13 00:00:15 2018
00:20 -!- naggety [~naggety@39.red-2-142-55.dynamicip.rima-tde.net] has quit [Ping timeout: 265 seconds]
01:17 -!- naggety [~naggety@129.red-81-47-50.dynamicip.rima-tde.net] has joined #navit
03:57 -!- naggety [~naggety@129.red-81-47-50.dynamicip.rima-tde.net] has quit [Remote host closed the connection]
03:57 -!- naggety [~naggety@129.red-81-47-50.dynamicip.rima-tde.net] has joined #navit
04:47 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
04:47 -!- mode/#navit [+v xenos1984] by ChanServ
05:03 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
05:20 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
05:20 -!- mode/#navit [+v xenos1984] by ChanServ
05:37 -!- Horwitz [~mich1@p200300800E33B200022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
05:37 -!- mode/#navit [+o Horwitz] by ChanServ
06:15 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
06:15 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
06:15 -!- mode/#navit [+v xenos1984] by ChanServ
08:03 -!- Horwitz [~mich1@p200300800E33B200022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 276 seconds]
10:11 -!- naggety [~naggety@129.red-81-47-50.dynamicip.rima-tde.net] has quit [Ping timeout: 248 seconds]
10:19 -!- naggety [~naggety@129.red-81-47-50.dynamicip.rima-tde.net] has joined #navit
10:52 -!- Horwitz [~mich1@p200300800E4AD300022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
10:52 -!- mode/#navit [+o Horwitz] by ChanServ
11:06 -!- lains [55733cca@gateway/web/freenode/ip.85.115.60.202] has joined #navit
12:35 -!- Horwitz [~mich1@p200300800E4AD300022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds]
12:44 -!- lains [55733cca@gateway/web/freenode/ip.85.115.60.202] has quit [Ping timeout: 260 seconds]
14:31 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
14:47 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has joined #navit
14:47 -!- mode/#navit [+v xenos1984] by ChanServ
16:07 #navit: <@KaZeR> hi there
17:07 -!- lains [55733cca@gateway/web/freenode/ip.85.115.60.202] has joined #navit
17:08 #navit: < lains> Hello
17:10 #navit: < lains> I have a question on a feature that I would like to get in navit...
17:10 #navit: < lains> and I can't manage to find a way to implement it.
17:44 #navit: <@KaZeR> hi lains 
17:44 #navit: <@KaZeR> sure, ask away!
17:52 #navit: < lains> Hi KaZeR
17:52 #navit: < lains> I would like to add a pointer on the map.
17:53 #navit: < lains> Pointing to the location selected when using "Show on map feature".
17:53 #navit: < lains> Usually, it is at the center of the screen but this is not that obvious.
17:54 #navit: < lains> The problem I'm facing is that I can't find a way to get an object drawn on the map at a specific location.
17:54 #navit: < lains> I tried to copy the route_end itemgra element (by creating a new itemgra element)
17:55 #navit: < lains> but I don't know where in the code I should set its position and how to enable/disable drawing of this element.
17:59 #navit: < lains> There seem to be something similar in gui_internal_cmd_view_on_map() with a type called "selected_point"
17:59 #navit: < lains> maybe it aims to achieve the same result, but I am not sure...
18:03 #navit: <@KaZeR> a pointer like the destination flag?
18:04 #navit: < lains> Yes, for example
18:45 #navit: <+ilovekiruna> hi KaZeR, hi Iains
18:52 #navit: < lains> Hello
19:05 #navit: <@KaZeR> lains: i think that a good approach could be to insert your item in an existing map_rect (or create and activate a map_rect on the fly)
19:05 #navit: <@KaZeR> like here : https://github.com/navit-gps/navit/blob/trunk/navit/map/textfile/textfile.c#L161 
19:06 #navit: <@KaZeR> you would insert your item in this map_rect, providing its coordinates and type, and if the map_rect is active then its content should be drawn
19:06 #navit: <+ilovekiruna> KaZeR: are the two locations for calling an issue for our idea?
19:06 #navit: <@KaZeR> ilovekiruna: no, we just need to change the current calls slightly
19:07 #navit: < lains> KaZeR: I am going to have a look at it. I am not practical with map_rect at all.
19:07 #navit: < lains> From my research, this feature was maybe already there in the past.
19:08 #navit: < lains> There is the evidence of a time_selected_point that may have been drawn at the location where we device to "Show on map" on the GUI
19:09 #navit: < lains> The way it is processed has been changed at commit https://github.com/navit-gps/navit/commit/8f46c1b336fa91a3094bc920215f1f68501745da
19:09 #navit: < lains> So I'm going to check if it was not actually working just before that commit...
19:10 #navit: < lains> In the code at that point in the history, I don't know if there is a map_rect
19:11 #navit: < lains> but there is a call to graphics_add_selection()
19:12 -!- Celelibi [celelibi@par69-9-88-166-81-29.fbx.proxad.net] has joined #navit
19:16 -!- noradtux [~noradtux@port-57006.pppoe.wtnet.de] has quit [Ping timeout: 240 seconds]
19:20 -!- noradtux [~noradtux@134.101.194.87] has joined #navit
20:06 #navit: < lains> If I understand well the concept behind map_rect...
20:06 #navit: < lains> a map_rect is a tile in a larger map
20:06 #navit: < lains> If I use a map_rect to draw a pointer/cursor, I need to create a map_rect
20:07 #navit: < lains> This map_rect must be linked to a map, but the map is handled by various plugins, depending on the type of map in use.
20:08 #navit: < lains> So I have to find a way to get the current map in use, get the map_rect displayed on the screen and insert my pointer/cursor as a new item in this map_rect.
20:09 #navit: < lains> I'm not sure I know how to do this... we'll see.
20:17 #navit: < lains> Probably the code in gui_internal_cmd_results_to_map() is a good starting point...
20:36 #navit: <@KaZeR> lains: you're probably on the right track. Although you should be able to create and activate a map_rect on the file and add it to a new or an existing map
20:37 #navit: <@KaZeR> i'll dig in the commit you link, maybe there's an easier solution
20:50 #navit: < lains> I'm not really sure about what the current type_select_point is trying to achieve, nor if it is actually really in use.
20:52 #navit: < lains> When trying to debug, I actually see item.type always set to type_none, so the code in gui_internal_cmd_view_on_map() merely centers the map to the selected location.
20:53 #navit: < lains> I think I can actually reuse the code in gui_internal_cmd_results_to_map() to make the work of highlighting the selected point on the map.
20:54 #navit: < lains> The code is already in there, and itemgra is defined to highlight a group of points on the map, so why not reuse it all to hightlight one point on the map?
20:54 #navit: < lains> I just have to create a list of only one point to highlight and get gui_internal_cmd_results_to_map() to do the work for me.
21:23 #navit: <@KaZeR> sounds good!
21:56 -!- lains [55733cca@gateway/web/freenode/ip.85.115.60.202] has quit [Quit: Page closed]
23:00 -!- xenos1984 [~xenos1984@22-164-191-90.dyn.estpak.ee] has quit [Quit: Leaving.]
--- Log closed Thu Jun 14 00:00:17 2018