Hi,
I'm trying to compile and run the current cvs gimp. I know I have to
expect to bug here or there, but I've seen quite a strange thing:
When I run the gimp, it always segfault with this backtrace:
#0 g_on_error_stack_trace (prg_name=0xbb78 "lt-gimp") at gerror.c:176
#1 0x4002a59c
On Sat, Feb 24, 2001 at 01:58:06AM +0100, Ernst Lippe <[EMAIL PROTECTED]> wrote:
> protocol for communication between plug-ins and Gimp that are all
> running on the same machine, you are free to choose any non standard
> protocol you like.
It's free software. You are always free to use whatever
Marc Lehmann wrote:
> I'd like to remind people that corba is not the only way to go, as there
> is also dco and especially MCOP (which was designed for realtime and
> multimedia applications). While CORBA might indeed be the best choice, it
> mustn't be choosen just because it has more letters ;-
Marc Lehmann wrote:
> I'd like to remind people that corba is not the only way to go, as there
> is also dco and especially MCOP (which was designed for realtime and
> multimedia applications). While CORBA might indeed be the best choice, it
> mustn't be choosen just because it has more letters ;-
On Fri, Feb 23, 2001 at 04:53:14PM -0500, Michael Meeks <[EMAIL PROTECTED]> wrote:
> I don't know what the gimp protocol is - clearly for _massive_
> chunks of data, shared memory is the only way to go. Vladimir has a nice
> CORBA interface for dealing with setting up shmem chunks to
Hi Nathan,
On Wed, 21 Feb 2001, Nathan C Summers wrote:
> Having plug-ins available to run on other hosts would be nice. Think
> a gimp farm. CORBA would seem to be an ideal solution to all of these
> issues. Can CORBA handle the large amounts of data transfer gimp
> requires at least
On Fri, Feb 23, 2001 at 06:30:53PM +0100, [EMAIL PROTECTED] wrote:
> Does this mean that you agree to ditching all the special code
> for the 3 and 1 byte case as well? I'd really love to see this
> changes although as already stated this might introduce a bit
> memory overhead in case the us
On 22 Feb, Sven Neumann wrote:
> We'll face one problem if we decide to make alpha the default for all
> images: A lot of fileformats do not understand alpha and you actually
> don't want to save the alpha channel with the image at all if you
> never touched it. One way to solve this would be to
The installed version of a plug-in can contain other files than just the
executable, e.g. help files and locale files.
When the user has root permissions these files can be installed on the
standard locations for the system, but where should these files be
installed when that is not the case?
The
On 22 Feb, Sven Neumann wrote:
> The file README.i18n in the gimp tree provides more information
> that might be interesting for you.
Uhoh, that reminds me that it's really needed to rewrite that file...
:)
--
Servus,
Daniel
___
Gimp-devel
10 matches
Mail list logo
