Re: View shrink factor

2001-02-13 Thread Austin Donnelly

On Saturday, 10 Feb 2001, David Monniaux wrote:

 Exactly which functions handle the low-level actual enlargement or
 shrinking of display? I'd like to write MMX versions for them.

I modified the original code to handle non-integer scale factors.  It
lives in image_render.c

I'm not sure how much use an MMX version will be, given the large
variety of platforms GIMP runs on.  Keeping two version of the code
(ASM + C) in sync is also a bit of a nightmare.  (Just my 0.02 Euro's worth)

Austin



perl hang

2001-02-13 Thread Zachary Beane

I'm using CVS, and it's hanging the build at:

Making all in plug-ins/perl/po
make[2]: Entering directory
`/usr/local/src/gimp/obj-2001-02-13/plug-ins/perl/po'
perl ../../../../plug-ins/perl/po/pxgettext   gimp-perl.po \
 test ! -f gimp-perl.po \
   || ( rm -f ../../../../plug-ins/perl/po/gimp-perl.pot \
mv gimp-perl.po ../../../../plug-ins/perl/po/gimp-perl.pot )

Just FYI. srcdir != builddir. (my builddir is obj-2001-02-13).

Zach
-- 
[EMAIL PROTECTED] Zachary Beane http://www.xach.com/



Re: View shrink factor

2001-02-13 Thread Marc Lehmann

On Tue, Feb 13, 2001 at 04:01:00PM +, Austin Donnelly [EMAIL PROTECTED] wrote:
 I modified the original code to handle non-integer scale factors.  It
 lives in image_render.c

When Daniel and I did our profiling just after the gimpcon we found that
the bottleneck were not really the paint functions but small things like
repeatedly calling methods like drawable_bpp which were just one line and
similar cases. We commited to do a lot of profiling but I don't think anybody
did ;)

-- 
  -==- |
  ==-- _   |
  ---==---(_)__  __   __   Marc Lehmann  +--
  --==---/ / _ \/ // /\ \/ /   [EMAIL PROTECTED]  |e|
  -=/_/_//_/\_,_/ /_/\_\   XX11-RIPE --+
The choice of a GNU generation   |
 |



Re: perl hang

2001-02-13 Thread Marc Lehmann

On Tue, Feb 13, 2001 at 12:34:18PM -0500, Zachary Beane [EMAIL PROTECTED] wrote:
 I'm using CVS, and it's hanging the build at:

hmm... the only thing I can currently imagine is the regex bug in 5.005_02
and _01. (But that should be chacked). Are you using 5.004? Maybe this bug
is also present in 5.004.

If it is 5.005_03 I have no idea. Could you run the script usign the same
arguments and the -d switch (you will then get a debugger prompt). Just
enter "t" for trace and then "c" for continue. You can then see wether it
runs in circles or just freezes at a specific point.

-- 
  -==- |
  ==-- _   |
  ---==---(_)__  __   __   Marc Lehmann  +--
  --==---/ / _ \/ // /\ \/ /   [EMAIL PROTECTED]  |e|
  -=/_/_//_/\_,_/ /_/\_\   XX11-RIPE --+
The choice of a GNU generation   |
 |



Re: perl hang

2001-02-13 Thread Zachary Beane

On Tue, Feb 13, 2001 at 07:36:07PM +0100, Marc Lehmann wrote:
 On Tue, Feb 13, 2001 at 12:34:18PM -0500, Zachary Beane [EMAIL PROTECTED] wrote:
  I'm using CVS, and it's hanging the build at:
 
 hmm... the only thing I can currently imagine is the regex bug in 5.005_02
 and _01. (But that should be chacked). Are you using 5.004? Maybe this bug
 is also present in 5.004.
 
 If it is 5.005_03 I have no idea. Could you run the script usign the same
 arguments and the -d switch (you will then get a debugger prompt). Just
 enter "t" for trace and then "c" for continue. You can then see wether it
 runs in circles or just freezes at a specific point.

I am using 5.005_03.

Stops at:

35:   while () {

This had been working fine in past weeks. Sethmo recently committed
something to the perl stuff, maybe he broke it inadvertently.

Zach
-- 
[EMAIL PROTECTED] Zachary Beane http://www.xach.com/



Error messages from a plug-in

2001-02-13 Thread Ernst Lippe

What is the "official way" to display error messages from a plug-in to
the user?
Basically what I looked for was a simple window (perhaps even with some
threatening icon) that I could invoke with a single function call
(I guess that I have been spoilt by too much Delphi programming).
I could find no such thing in the standard Gtk/Gimp libraries.

Greetings,
Ernst Lippe [EMAIL PROTECTED]



Re: Error messages from a plug-in

2001-02-13 Thread Sven Neumann

Hi,

Ernst Lippe [EMAIL PROTECTED] writes:

 What is the "official way" to display error messages from a plug-in to
 the user?
 Basically what I looked for was a simple window (perhaps even with some
 threatening icon) that I could invoke with a single function call
 (I guess that I have been spoilt by too much Delphi programming).
 I could find no such thing in the standard Gtk/Gimp libraries.

Use g_message (), which is a standard glib logging mechanism that is 
configured to do the right thing from gimp plug-ins. The right thing is 
to use the console if the user specified the --console-messages option 
or if gimp is running in batch mode. If running interactively it will 
display a dialog window or use the error console.


Salut, Sven






Re: perlotine

2001-02-13 Thread Carol Spears

This is the end of a thread on the gimp-user mail.  I am constantly
amazed at what appears to be distribution related troubles to a cleanly
installed Gimp. I call this a distribution problem because it came with
perl5.4 (bought in September 2000) and this is the core of my problems.

Marc Lehmann wrote:
 
 On Tue, Feb 13, 2001 at 12:53:44PM -0500, Carol Spears [EMAIL PROTECTED] 
wrote:
  I would like to know how to install all of this without the PDL as my
  space is somewhat limited.
 
 The official answer is "just do it", i.e. perlotine does not depend on PDL
 and will be installed even when PDL is not present (however, semi-present
 PDL installations, e.g. binaries but no header files, cuase the build to
 fail of course).
 
 --
   -==- |
   ==-- _   |
   ---==---(_)__  __   __   Marc Lehmann  +--
   --==---/ / _ \/ // /\ \/ /   [EMAIL PROTECTED]  |e|
   -=/_/_//_/\_,_/ /_/\_\   XX11-RIPE --+
 The choice of a GNU generation   |
  |


It appears that you can upgrade your perl and leave some PDL binaries
without their headers.

I think that alot of almost capable LUsers like me would benefit from an
changing of the warning message.  I don't have time to reproduce it
here, but the current warning (probably in the configure) made me think
that you need to install the PDL in order to have fully functioning
gimp-perl.  And this did fix my problem.  I would have rather removed
the offending binaries to fix it, however.

Even now, I know the problem but probably need to get a book to help me
find the damn binaries!

Thanks for your time.  I really love my gimp.  I wish that the whole
world worked as well as Wilbur! And would improve as fast as he has.