Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Wolfgang Mauer
Tried this, run perfect on linux, runs "better" on win                 try                 {                     var mainloop = new MainLoop();                     SourceFunc quit = ()=>                     {                     mainloop.quit ();                     return

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Wolfgang Mauer
Thank you very much Am 12.03.19 um 23:46 schrieb Al Thomas via vala-list: > On Tuesday, 12 March 2019, 22:40:17 GMT, Wolfgang Mauer wrote: Are there any sample using "GLib.Subprocess" with async stdin/stdout/stderr ? See https://stackoverflow.com/a/54391519 That one splices the

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Al Thomas via vala-list
> On Tuesday, 12 March 2019, 22:40:17 GMT, Wolfgang Mauer > wrote: > Are there any sample using "GLib.Subprocess" with async > stdin/stdout/stderr ? See https://stackoverflow.com/a/54391519 That one splices the output from one command to the input of another. So a bit more than you

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Wolfgang Mauer
I will try, but can't find any vala example... Are there any sample using "GLib.Subprocess" with async stdin/stdout/stderr ? Am 12.03.19 um 23:22 schrieb Al Thomas via vala-list: > On Tuesday, 12 March 2019, 22:03:28 GMT, Wolfgang Mauer wrote: > Well i found the "problem", it

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Al Thomas via vala-list
> On Tuesday, 12 March 2019, 22:03:28 GMT, Wolfgang Mauer wrote: > Well i found the "problem", it wasn't my code but i tried the example > from the valadoc > "https://valadoc.org/glib-2.0/GLib.Process.spawn_async_with_pipes.html; > Just let it compile himself >    string[] spawn_args

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Wolfgang Mauer
Maybe some "valac" developers around here Well i found the "problem", it wasn't my code but i tried the example from the valadoc "https://valadoc.org/glib-2.0/GLib.Process.spawn_async_with_pipes.html; Just let it compile himself     string[] spawn_args = {"valac", "--pkg", "glib-2.0",

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Wolfgang Mauer
Thank you very much! I found my problem, was a "self-made thinking error"(threading and scope) >One thing to try is compiling with debug information and then use G_DEBUG=fatal-criticals and a debugger. I use valaDevelop to debug valaDevelop, and i have an option "Break on critical" ;-)

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Al Thomas via vala-list
> On Tuesday, 12 March 2019, 15:48:59 GMT, Wolfgang Mauer wrote: > With Linux everything works like expected with no errors/warnings but on > Windows(10/MSYS64) and macOS it get lots of errors. > (valaDevelop.exe:2980): Gtk-CRITICAL **: 16:33:50.460: > gtk_text_view_get_buffer:

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Rico Tzschichholz
Imho, a suggestion to join #vala on IRC to target a wider audience for problem solving, is help. In case of a platform-specific toolkit issues, #gtk on GIMPnet will likely be even more beneficial. Cheers, Rico Am 12.03.19 um 17:20 schrieb Wolfgang Mauer: > I already find out that

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Corentin Noël
Hi Wolfgang, Debugging your software using this mailing list is going to be very painful, especially for closed-source software. Feel free to pop in #vala on IRC GIMPnet (irc.gimp.org) which is a better tailored communication system for this kind of tasks. Herzliche Grüße, Corentin Noël Le

Re: [Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Wolfgang Mauer
Of course there is a "return false;" at the end of GLib.Timeout.add(0, () => {     buildTextView.buffer.insert_at_cursor(line, -1);     var mark = buildTextView.buffer.get_insert();     buildTextView.scroll_to_mark(mark, 0, true, 1, 1);     return false; } Am 12.03.19 um 16:48 schrieb Wolfgang

[Vala] multithreading -> weird behaviour on win(msys) and macOS

2019-03-12 Thread Wolfgang Mauer
I have a strange behavior between Ubuntu/MSYS and macOS I have a output window (buildTextView) and i like to put all output from "spawn_async_with_pipes" to the end of the buffer. With Linux everything works like expected with no errors/warnings but on Windows(10/MSYS64) and macOS it get lots