Jean-Marc Lasgouttes wrote:
> It applied flawlessly. I am currently compiling, and will commit it
> afterwards.
Phew... thanks.
Jürgen
> JMarc
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Jean-Marc Lasgouttes wrote:
>> Use directly cvs diff -uR >patch.diff
Juergen> Thank you all very much for your patient instructions. I
Juergen> didn't know this indeed %-| Here's the (unmodified) patch
Juergen> against
> You can indeed delete such things, but patch should be able to cope. As for
> the POTFILES.in, it's fine but does look a little perverse. My box does
> something similar. Generally speaking, I delete it too, or at a pinch edit it
> by hand.
>
To make a clean patch, I do:
rm po/*.po po/POTF
Am Mittwoch, 21. November 2001 13:16 schrieb Angus Leeming:
> You can indeed delete such things, but patch should be able to cope.
> As for the POTFILES.in, it's fine but does look a little perverse. My
> box does something similar. Generally speaking, I delete it too, or
> at a pinch edit it by h
On Wednesday 21 November 2001 11:47 am, Juergen Spitzmueller wrote:
> Jean-Marc Lasgouttes wrote:
> > Use directly
> > cvs diff -uR >patch.diff
>
> Thank you all very much for your patient instructions. I didn't know
> this indeed %-|
> Here's the (unmodified) patch against recent cvs. Note that
Jean-Marc Lasgouttes wrote:
> Use directly
> cvs diff -uR >patch.diff
Thank you all very much for your patient instructions. I didn't know
this indeed %-|
Here's the (unmodified) patch against recent cvs. Note that the changes
to po/POTFILES.in and the first lines beginning with '?' look
suspi
On Wednesday 21 November 2001 9:51 am, Juergen Spitzmueller wrote:
> Jean-Marc Lasgouttes wrote:
> > Does not work:
>
> Arghh!!!
>
> > patch: malformed patch at line 266: @@ -632,7 +648,7 @@
> >
> > Do you really have to hand-edit your patches before sending them?
>
> Well, I used to creat
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> I have to admit that I don't like this kind of work, but I
Juergen> have no idea how to do it better. Maybe I'm just too stupid,
Juergen> so hints are *very* welcome.
Use directly
cvs diff -uR >patch.diff
Note that a .
Jean-Marc Lasgouttes wrote:
> Does not work:
Arghh!!!
> patch: malformed patch at line 266: @@ -632,7 +648,7 @@
>
> Do you really have to hand-edit your patches before sending them?
Well, I used to create patches with a cvs-frontend tool (Cervisia)
which was very comfortable and never cau
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Please try this one (including all my changes from today
Juergen> since my first patch seems not to be committed). I really
Juergen> hope it works. Please tell me, if not!
Does not work:
patch: malformed patch at l
Jean-Marc Lasgouttes wrote:
> You patch does not work here: I have rejects on form_graphics.fd,
> form_preferences.fd and form_print.fd. Since I spent quite a bit of
> time trying to apply by hand the previous one (which had such
> problems), I'd appreciate a working one for a change :)
Please tr
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> OK, here's a patch that unifies and enlarges all browse
Juergen> buttons (and contains my previous changes, too). Because it's
Juergen> 2:1 currently, I changed them to "Browse...". If you change
Juergen> your mind, just
Juergen Vigna wrote:
> we really should stay compact. It is standard that a button inside a
> dialog will open something else otherwise it would be a radio/check
> button or sit in the below row where "OK/Cancel" etc are. Or do you
> know of a button inside a dialog which is used otherwise?
Have
On 20-Nov-2001 Jean-Marc Lasgouttes wrote:
> The idea is to give a hint to the user that this command does not have
> a immediate effect. It is like 'File>Open...'.
I know what the idea is but IMO on Buttons we should not put the dots.
Is is different for menus as there we have space enough to
Juergen Vigna wrote:
> On 20-Nov-2001 Andre Poenitz wrote:
> > I think "Browse..." is better if there is another dialog hidden
> > behind this button
>
> Well but "Browse" almost always opens a "Browse-Dialog" so why
> enlarge the button by ... if it's not needed. IMO we should leave it
> to "
> "Juergen" == Juergen Vigna <[EMAIL PROTECTED]> writes:
Juergen> Well but "Browse" almost always opens a "Browse-Dialog" so
Juergen> why enlarge the button by ... if it's not needed. IMO we
Juergen> should leave it to "Browse"!
The idea is to give a hint to the user that this command does n
Jean-Marc Lasgouttes wrote:
> Juergen> Concerning the "Browse" button, I noticed that it is named
> Juergen> "Browse" in all dialogs except in External and Bibtex where
> Juergen> it is called "Browse...". I don't see a reason for this, so
> I Juergen> unified it to "Browse", which solves the prob
On 20-Nov-2001 Andre Poenitz wrote:
> On Tue, Nov 20, 2001 at 01:47:14PM +0100, Jürgen Spitzmüller wrote:
>> And I just noticed that I didn't detect all Browse buttons. In the
>> preferences dialog, there is a bunch of "Browse..." buttons left.
>> So I have to prepare a new patch for this anyway
On Tue, Nov 20, 2001 at 01:47:14PM +0100, Jürgen Spitzmüller wrote:
> And I just noticed that I didn't detect all Browse buttons. In the
> preferences dialog, there is a bunch of "Browse..." buttons left.
> So I have to prepare a new patch for this anyway. As I said, I don't
> care, so I will un
Juergen Spitzmueller wrote:
> We just have to agree on one version for /all/ buttons, otherwise it
> doesn't make sense.
And I just noticed that I didn't detect all Browse buttons. In the
preferences dialog, there is a bunch of "Browse..." buttons left.
So I have to prepare a new patch for this
> "Juergen" == Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
Juergen> Anyway, here is a first and simple patch that enlarges the
Juergen> Restore button in some dialogs. It was wide enough (100p) in
Juergen> other ones, so this patch just unifies the overall design ;-)
Good.
Juergen> Con
Jean-Marc Lasgouttes wrote:
> There is the function
> double fl_adjust_form_size(FL_FORM *form)
> which is automatically emitted by fdesign with the -compensate flag,
> but when I took a look at it a long time ago, I was not able to make
> it work. You should probably take a look at it and see w
22 matches
Mail list logo