I've just merged the Native File Dialogs for Windows branch into the mainline. All comments, criticisms or bug reports are very welcome!
On Feb 23, 2008, at 5:00 AM, Joel Holdsworth wrote:
I've just merged the Native File Dialogs for Windows branch into the mainline. All comments, criticisms or bug reports are very welcome!
When I first launch inkscape and do File|Open, I see this:
(inkscape:5624): Gtk-CRITICAL **: gtk_file_system_unix_get_info: assertion `g_path_is_absolute (filename)' failed
-----Original Message----- From: inkscape-devel-bounces@lists.sourceforge.net [mailto:inkscape-devel-bounces@lists.sourceforge.net] On Behalf Of Jon A. Cruz Sent: zaterdag 23 februari 2008 20:10 To: Joel Holdsworth Cc: Inkscape Devel List Subject: Re: [Inkscape-devel] Native File Dialogs Now Merged
On Feb 23, 2008, at 5:00 AM, Joel Holdsworth wrote:
I've just merged the Native File Dialogs for Windows branch
into the
mainline. All comments, criticisms or bug reports are very welcome!
When I first launch inkscape and do File|Open, I see this:
(inkscape:5624): Gtk-CRITICAL **: gtk_file_system_unix_get_info: assertion `g_path_is_absolute (filename)' failed
I think this one has been around for quite a while. So not sure the new file dialogs cause it.
On Feb 23, 2008, at 11:40 AM, J.B.C.Engelen@...1578... wrote:
When I first launch inkscape and do File|Open, I see this:
(inkscape:5624): Gtk-CRITICAL **: gtk_file_system_unix_get_info: assertion `g_path_is_absolute (filename)' failed
I think this one has been around for quite a while. So not sure the new file dialogs cause it.
OK. I did a quick check and got this:
** Message: INKSCAPE_EXAMPLESDIR is currently [Contents/Resources/ examples]
Gtk-CRITICAL **: gtk_file_system_unix_get_info: assertion `g_path_is_absolute (filename)' failed
And the code involved is
g_message("INKSCAPE_EXAMPLESDIR is currently [%s]", INKSCAPE_EXAMPLESDIR);
//###### Allow easy access to our examples folder if(Inkscape::IO::file_test(INKSCAPE_EXAMPLESDIR, (GFileTest)(G_FILE_TEST_EXISTS | G_FILE_TEST_IS_DIR))) { => add_shortcut_folder(INKSCAPE_EXAMPLESDIR); }
So... It appears that I can get the warning worked-around by adding a check for absolute path.
The main question is if that is a desired end behavior. I'd expect it only shows up for people like me, running a local dev build on OS X.
participants (3)
-
unknown＠example.com -
Joel Holdsworth -
Jon A. Cruz