Simon Budig wrote:
Garry R. Osgood ([EMAIL PROTECTED]) wrote:
snipped... bezier basis functions associated with the first and fourth
control points
grow expotentially to unity, so manipulating Simon's path near control
^ infinity?
It waves at unity on its way
On Tue, 11 Jan 2000 00:55:10 +0800, Ian McKellar [EMAIL PROTECTED] said:
For each of the frame parts create a separate layer in the way
described above, but call each of these "PART: name" where name will
be used in the image name. To set frame part attributes append "name
= value" pairs to the
On Tue, Jan 11, 2000 at 07:25:30AM -0500, Kelly Lynn Martin wrote:
On Tue, 11 Jan 2000 00:55:10 +0800, Ian McKellar [EMAIL PROTECTED] said:
For each of the frame parts create a separate layer in the way
described above, but call each of these "PART: name" where name will
be used in the
Sven Neumann wrote:
I don't see your problem. I do get my errors in the error-console. All
that's missing IMO is a way to set the error_console as the default
error_handler in the preferences. That should be easy and is definitely worth
the effort.
Nick Lamb:
Well, I think you
I was alerted by Stanislav Brabec about a problem with menu
translations. In his translation of Logulator to czech, he properly
changed all occurences of "Logulator", but, while the gimp displays the
menus _within_ the Filters/Logulator menu correctly, the Logulator menu
itself NOT being
On Tue, Jan 11, 2000 at 07:25:30AM -0500, Kelly Lynn Martin
[EMAIL PROTECTED] wrote:
A convenient user-accessible parasite editor would make this sort of
thing MUCH friendlier -- instead of having to use magic cookie layer
names you'd just click on a button on the layer dialog and edit the
Hi,
Nobody (I mean it ;) uses the gserialize feature, for example (which has
problems of its own)
Do you know of any probelms with geserialize? I use the functions for a
project at university and would like to hear about problems I have not yet
been able to observe (the ones I found were
I don't see your problem. I do get my errors in the error-console. All
that's missing IMO is a way to set the error_console as the default
error_handler in the preferences. That should be easy and is definitely worth
the effort.
Well, I think you hit the nail right on the head, I have
On Tue, Jan 11, 2000 at 11:50:28AM +0100, Sven Neumann wrote:
As said, I can't reproduce your problem here. As soon as I open the
error_console, all errors produced with g_message () appear in that
dialog instead of popping up a message window.
Oh, I see. Somehow I expected that all my
On Sat, 8 Jan 2000, Marc Lehmann wrote:
On Fri, Jan 07, 2000 at 06:33:02PM +0100, [EMAIL PROTECTED] wrote:
I included in the packages the scripts I used to link the libraries and
the perl shared-objects, but don't ask me why it suddenly started working.
And I just wanted to ask you what
On Tue, 11 Jan 2000, Nick Lamb [EMAIL PROTECTED] wrote:
On Tue, Jan 11, 2000 at 11:50:28AM +0100, Sven Neumann wrote:
As said, I can't reproduce your problem here. As soon as I open the
error_console, all errors produced with g_message () appear in that
dialog instead of popping up a
On Tue, Jan 11, 2000 at 06:15:11PM +0100, Raphael Quinet wrote:
So maybe what we need is a new option in the gimprc, something like:
make-error-console-visible-on-first-g-message-and-leave-it-open
If you set that to true, then the error console would do what you were
expecting. Or did I
12 matches
Mail list logo
