I realize this is not a bug in nativefiledialog, but this just cost me MANY hours of intense frustration and confusion, so I'll mention it in case it helps someone else.
Simply having this anywhere will cause the nativefiledialog to crash every time:
The solution is to call your variables something other than g_log.
As a side note, I thought platform libraries were supposed to namespace or prefix their variables away properly so that collisions like this are extremely unlikely. Is it really such a surprise that the application programmer might want to name a variable g_log?? Couldn't the library at least make it glib2_log or something?? </rant>
I realize this is not a bug in nativefiledialog, but this just cost me MANY hours of intense frustration and confusion, so I'll mention it in case it helps someone else.
Simply having this anywhere will cause the nativefiledialog to crash every time:
The solution is to call your variables something other than
g_log.As a side note, I thought platform libraries were supposed to namespace or prefix their variables away properly so that collisions like this are extremely unlikely. Is it really such a surprise that the application programmer might want to name a variable
g_log?? Couldn't the library at least make itglib2_logor something?? </rant>