--- Log opened Tue Apr 02 00:00:41 2019
00:11 -!- Horwitz [~mich1@p200300EC9BC15600022268FFFE64E7C4.dip0.t-ipconnect.de] has quit [Ping timeout: 268 seconds]
00:24 -!- Horwitz [~mich1@p200300EC9BC29C00022268FFFE64E7C4.dip0.t-ipconnect.de] has joined #navit
00:24 -!- mode/#navit [+o Horwitz] by ChanServ
04:58 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has joined #navit
04:58 -!- mode/#navit [+v xenos1984] by ChanServ
06:15 -!- naggety [~naggety@83.red-88-31-115.dynamicip.rima-tde.net] has joined #navit
06:16 #navit: < naggety> Hi
06:17 #navit: < naggety> KaZeR, I'm using GTK graphics with internal GUI.
06:17 #navit: < naggety> jkoan, thankyou, let me know if you find something
06:19 #navit: <+jkoan> Hi naggety, good to know that you are using the internal gui. :) how many windows do you have found?
06:21 #navit: < naggety> jkoan: 3 windows + 2 children windows
06:21 #navit: < naggety> on the "top" level, a 1x1px window, a 10x10px window and the main window
06:22 #navit: < naggety> last 2 ones have one 1x1 child window each one
06:22 #navit: < naggety> 10x10 window and the main one are called both "navit", so if I do "xdotool search --name navit" I get both of them
06:22 #navit: <+jkoan> So 5 windows in total?
06:22 #navit: < naggety> (also if I search by class or classname)
06:23 #navit: < naggety> Yes, 5 windows. However, it seems that every GTK app creates a 1x1 child window, so this is normal
06:23 #navit: < naggety> The 1x1 window in the top level, I don't know if it is normal or not
06:26 #navit: <+jkoan> For me the 10x10 window seems strange
06:27 #navit: < naggety> Yes, that one seems strange
06:28 #navit: < naggety> And it is what is confusing xdotool
06:32 #navit: <+jkoan> Okay, will look into it like I said before. Afk now a bit
06:32 #navit: < naggety> thanks! :)
09:01 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection]
09:02 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has joined #navit
09:02 -!- mode/#navit [+v Navit] by ChanServ
14:18 -!- naggety [~naggety@83.red-88-31-115.dynamicip.rima-tde.net] has quit [Quit: Konversation terminated!]
14:34 -!- xenos1984 [~xenos1984@2001:bb8:2002:200:6651:6ff:fe53:a120] has quit [Quit: Leaving.]
14:54 -!- xenos1984 [~xenos1984@20c6-2a06-57d8-cc7d-8780-87e7-07d0-2001.dyn.estpak.ee] has joined #navit
14:54 -!- mode/#navit [+v xenos1984] by ChanServ
14:58 #navit: <@KaZeR> hi there
15:42 #navit: <+jkoan> hi KaZeR
15:54 #navit: <@KaZeR> what's up jkoan ?
15:55 #navit: <+jkoan> right now looking at gtk and xdotool :D but not for long
16:08 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has quit [Remote host closed the connection]
16:08 -!- Navit [~Navit@ec2-34-214-224-248.us-west-2.compute.amazonaws.com] has joined #navit
16:08 -!- mode/#navit [+v Navit] by ChanServ
16:13 #navit: <+jkoan> KaZeR: does navit has something like saving the xml config? If not we should add it. Probably we could also make the configuration more easy
16:24 #navit: <@KaZeR> currently navit does not overwrite the xml config. It has been discussed in the past, and the aggreement at that time was to have the UI override some settings in a different file instead. That's what GTK does for example
16:25 #navit: <@KaZeR> i do agree that it would make the configuration easier. If we were to do it, i think that we should write the output to a new file, and have navit look at that file first. This would allow to easily reset the configuration if needed
16:48 #navit: <+jkoan> my idea would be a base config (for example in /etc) and a user config which overwrites paths of the configuration
16:49 #navit: <+jkoan> but definetly no gui/graphic spezific configs
16:50 #navit: <+jkoan> alternativly i thought about a executable navit-gtk, navit-sdl and so on. but i think this would be bad in many more cases
18:35 #navit: <+Navit> <mike> Hello
19:25 #navit: <@KaZeR> hi mike
20:05 #navit: <+Navit> <mike> How are you?
21:35 -!- xenos1984 [~xenos1984@20c6-2a06-57d8-cc7d-8780-87e7-07d0-2001.dyn.estpak.ee] has quit [Quit: Leaving.]
21:42 -!- ilovekiruna [~ilovekiru@253.92-221-28.customer.lyse.net] has joined #navit
21:42 -!- mode/#navit [+v ilovekiruna] by ChanServ
21:49 -!- ilovekiruna [~ilovekiru@253.92-221-28.customer.lyse.net] has quit [Quit: Konversation terminated!]
22:03 -!- ilovekiruna [~ilovekiru@253.92-221-28.customer.lyse.net] has joined #navit
22:03 -!- mode/#navit [+v ilovekiruna] by ChanServ
22:12 -!- ilovekiruna [~ilovekiru@253.92-221-28.customer.lyse.net] has quit [Ping timeout: 245 seconds]
--- Log closed Wed Apr 03 00:00:43 2019