Re: libegg/recentchooser

2005-11-30 Thread Emmanuele Bassi
Hi James, On Wed, 2005-11-30 at 11:23 +0800, James Henstridge wrote: > Emmanuele Bassi wrote: > > >Uhm, I'll put that code under #idef G_OS_UNIX/#endif guards for the time > >being, but the getenv("TZ")/setenv("TZ") timezone trick should work on > >any sufficiently recent POSIX-like system; users

Re: Make g_rename() replace existing files on Win32?

2005-11-30 Thread J. Ali Harlow
On 30/11/05 00:54:22, Tor Lillqvist wrote: The rename() function in the Microsoft C library calls the Win32 API MoveFile(), which does not replace existing files. I now notice there is also a function MoveFileEx(), to which one can specify the flag MOVEFILE_REPLACE_EXISTING, which enables atomic

Re: comments on g_list_slice / g_list_splice

2005-11-30 Thread Paul LeoNerd Evans
On Wed, 30 Nov 2005 00:57:42 -0500 "ANDREW PAPROCKI, BLOOMBERG/ 731 LEXIN" <[EMAIL PROTECTED]> wrote: > GList * g_list_slice(GList *list, GList *link, gint n_links); > GList * g_list_remove_slice(GList *list, GList *link, gint n_links); > > GList * g_list_splice(GList *list, GList *splice_list, g

Fwd: Re: comments on g_list_slice / g_list_splice

2005-11-30 Thread ANDREW PAPROCKI, BLOOMBERG/ 731 LEXIN
I just realized that all of the APIs need to return the original list because it can be modified. The way I'm playing with it now, the slice calls would simply unlink 'link' and it is up to the caller to reuse the same 'link' pointer as the newly separated list.. - Original Message - F

RE: g_list_first()

2005-11-30 Thread Mathieu LUGIEZ
Hello, What did you need to do exactly If you need to test all elements in a single list and delete elements you whish you can use this type of code, it isn't optimised but it work's, else you can use g_list_foreach to apply a personnal function at each element of your GSList but it doesn'

Re: Call-return interface for file choosers? (and: security using powerboxes)

2005-11-30 Thread Mark Seaborn
David Malcolm <[EMAIL PROTECTED]> wrote: > How about a slightly different interface where you work with > buffers/memory mapped files/file handles/something other than filenames? > This way the application doesn't need to be able to open the user's > files for reading/writing; the trusted executab

GLib Bug: IO Channel cannot work with files larger that 2GB

2005-11-30 Thread Chris Morrison
Hi all, There seems to be a bug with the IO Channel functions in Glib version 2.8.4 for Windows. This bug prevents seeking in files greater than 2GB in size, i.e. where a 64-bit file pointer would be required. The following snip of code will work if 'file_channel' refers to a file of less than 2G

GLib Bug: IO Channel cannot work with files larger that 2GB

2005-11-30 Thread Tor Lillqvist
Chris Morrison writes: > Is this a known bug/issue or am I missing something? Yes. Large file support is missing from the Win32 port. Sorry. It might be possible to do some fixes here and there without needing any new API or breaking ABI, like using _lseeki64() instead of lseek() in giowin32.c. (

Re: libegg/recentchooser

2005-11-30 Thread Morten Welinder
> Uhm, I'll put that code under #idef G_OS_UNIX/#endif guards for the time > being, but the getenv("TZ")/setenv("TZ") timezone trick should work on > any sufficiently recent POSIX-like system; users of other operating > systems might just drop me an email. setenv isn't POSIX. You can probably ju