Hi,
Gene Heskett <[EMAIL PROTECTED]> writes:
> >See http://bugzilla.gnome.org/show_bug.cgi?id=110307
>
> I take it that means the next version will have that?
Did you read the report? It means that we won't see this feature
unless a new stable version of gimp-print is released that has this
fun
On Friday 07 November 2003 19:40, Sven Neumann wrote:
>Hi,
>
>Gene Heskett <[EMAIL PROTECTED]> writes:
>> >See http://bugzilla.gnome.org/show_bug.cgi?id=110307
>>
>> I take it that means the next version will have that?
>
>Did you read the report? It means that we won't see this feature
>unless a n
On Friday 07 November 2003 15:55, BandiPat wrote:
>On Friday 07 November 2003 02:13 pm, Jonathan Bartlett wrote:
>> If it's a PDF file, why not just print through lpr?
>>
>> lpr -#50 target.pdf
>>
>> On Fri, 7 Nov 2003, Joao S. O. Bueno wrote:
>> > Save it in another format, and open in staroffice
On Friday 07 November 2003 14:13, Jonathan Bartlett wrote:
>If it's a PDF file, why not just print through lpr?
>
>lpr -#50 target.pdf
Unforch, I have only two working methods to print something, and lpr
isn't one of them. I can print a test page correctly from cups
(1.1.19), and I can print ab
On Friday 07 November 2003 13:18, Sven Neumann wrote:
>Hi,
>
>Gene Heskett <[EMAIL PROTECTED]> writes:
>> Is there anything I can do about this?
>
>See http://bugzilla.gnome.org/show_bug.cgi?id=110307
I take it that means the next version will have that?
Currently, I have 1.1.19 installed.
>Sven
I'm trying to build gimp-1.3.22 within OpenBSD's ports framework.
It does a "fake install" and then builds a package from the "fake
install root". I'm having a problem with libtool relinking
libgimpmodule, and looking for libgimpbase in /usr/local instead
of the "fake install root".
Here's a tail
On Friday 07 November 2003 02:13 pm, Jonathan Bartlett wrote:
> If it's a PDF file, why not just print through lpr?
>
> lpr -#50 target.pdf
>
> On Fri, 7 Nov 2003, Joao S. O. Bueno wrote:
> > Save it in another format, and open in staroffice instead,.
> >
> > Sorry, there is as bug filed about this
If it's a PDF file, why not just print through lpr?
lpr -#50 target.pdf
On Fri, 7 Nov 2003, Joao S. O. Bueno wrote:
> Save it in another format, and open in staroffice instead,.
>
> Sorry, there is as bug filed about this in the GIMP, but there seens
> to be no developer with the time to revamp
Save it in another format, and open in staroffice instead,.
Sorry, there is as bug filed about this in the GIMP, but there seens
to be no developer with the time to revamp the printing dialog/system
as of now.
:-(
On Friday 07 November 2003 3:50 pm, Gene Heskett wrote:
> Greetings;
>
> I have
Hi,
Gene Heskett <[EMAIL PROTECTED]> writes:
> Is there anything I can do about this?
See http://bugzilla.gnome.org/show_bug.cgi?id=110307
Sven
___
Gimp-user mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Greetings;
I have a target practice target.pdf file that I'd like to print about
50 copies of. Unforch, selecting print, it takes about 6-7 minutes
to render each one, but only about 1:30 to print it once rendered.
The print selector has no box for number of copies, so its taking me
about 10 m
Hi,
Sven Neumann wrote:
> David Neary <[EMAIL PROTECTED]> writes:
> > The contents of the image window and the status bar are now
> > customisable in the preferences. The %D format string gives you
> > the dirty flag. %D* will add a * to the title if the image is
> > dirty, %D@ will add a @. This
Hi,
David Neary <[EMAIL PROTECTED]> writes:
> The contents of the image window and the status bar are now
> customisable in the preferences. The %D format string gives you
> the dirty flag. %D* will add a * to the title if the image is
> dirty, %D@ will add a @. This is not very well documented a
Hi,
Eric Pierce wrote:
> I'm going to list a few minor glitches I've noticed with recent builds of
> the Gimp (1.3.17-1.3.22), and I hope a few other people would either
> verify or counter these items before I fill out any bug reports.
The best thing to do is to search bugzilla with the keywords
Hi,
"Eric Pierce" <[EMAIL PROTECTED]> writes:
> #1 If I have 2 or more linked layers and I use the move tool to try
> to move all the layers (with mouse or arrow keys), only the
> currently selected layer moves as opposed to all the linked layers.
> In Gimp 1.2.x, all linked layers move together
Hi,
Khiraly wrote:
> ALT+'hold LeftMouseButton and move' is to move the window (in metacity).
> But it makes impossible to use gimp 1.2, since keybindings are trapped
> by metacity, it does not get through to gimp.
This is rebindable, as far as I know.
In any case, on window managers which grab
Hi,
On Fri, 2003-11-07 at 07:08, Eric Pierce wrote:
> #1 If I have 2 or more linked layers and I use the move tool to try to
> move all the layers (with mouse or arrow keys), only the currently
> selected layer moves as opposed to all the linked layers. In Gimp 1.2.x,
> all linked layers move tog
17 matches
Mail list logo
