Allan Rae wrote:
On Fri, 27 Sep 2002, Rob Lahaye wrote:
[...]
Why does this function only work on check and button widgets?
When I do, for example:
bc().addReadOnly(dialog_-choice_width_unit)
the choice widget is not disabled for a readonly document!
Does this function only apply to
Angus Leeming wrote:
On Friday 27 September 2002 4:13 am, R. Lahaye wrote:
Jürgen and others,
Some time ago I posted my desire to remove the text_warning
areas in the Xforms
dialogs. You (Jürgen) replied then that:
I have spent a lot of time in implementing this power user
stuff (ability
Juergen Spitzmueller wrote:
R. Lahaye wrote:
The space is always occupied by the (mostly void) text widget; and
all it says (to the power user!) that the input is invalid.
No, it's a hint to the unexperienced user. We have disabled the input filter
for the power users, which might
Allan Rae wrote:
> On Fri, 27 Sep 2002, Rob Lahaye wrote:
> [...]
>
>>Why does this function only work on check and button widgets?
>>When I do, for example:
>>
>> bc().addReadOnly(dialog_->choice_width_unit)
>>
>>the choice widget is not disabled for a readonly document!
>>
>>Does this
Angus Leeming wrote:
> On Friday 27 September 2002 4:13 am, R. Lahaye wrote:
>
>>Jürgen and others,
>>
>>Some time ago I posted my desire to remove the text_warning
>>areas in the Xforms
>>
>>dialogs. You (Jürgen) replied then that:
>>
>>&
Juergen Spitzmueller wrote:
> R. Lahaye wrote:
>
>>The space is always occupied by the (mostly void) text widget; and
>>all it says (to the power user!) that the input is invalid.
>
>
> No, it's a hint to the unexperienced user. We have disabled the input filter
&
Edwin,
Angus told me you're working on the controller-view split of some
Xforms dialogs (in particular the FormDocument dialog).
Since I am currently redesigning/improving the Xforms dialogs and
also modifying the corresponding code, we should avoid clashes between
what you're doing and my
Edwin Leuven wrote:
Well, I don't intend to touch the xforms frontend since I think it's a waste
of my time (no offense).
What I've done is the following.
I have written the document controller:
controllers/ControlDocument.C
controllers/ControlDocument.h
and am nearly done
Jürgen and others,
Some time ago I posted my desire to remove the text_warning areas in the Xforms
dialogs. You (Jürgen) replied then that:
I have spent a lot of time in implementing this power user stuff (ability to
enter length directly without the choices). Please think twice before
Edwin,
Angus told me you're working on the controller-view split of some
Xforms dialogs (in particular the FormDocument dialog).
Since I am currently redesigning/improving the Xforms dialogs and
also modifying the corresponding code, we should avoid clashes between
what you're doing and my
Edwin Leuven wrote:
>
> Well, I don't intend to touch the xforms frontend since I think it's a waste
> of my time (no offense).
>
> What I've done is the following.
>
> I have written the document controller:
>
> controllers/ControlDocument.C
> controllers/ControlDocument.h
>
> and am
Jürgen and others,
Some time ago I posted my desire to remove the text_warning areas in the Xforms
dialogs. You (Jürgen) replied then that:
> I have spent a lot of time in implementing this "power user" stuff (ability to
> enter length directly without the choices). Please think twice before
Dekel,
Today you've committed a patch to forms/form_wrap.fd and FormWrap.C.
You replaced inner by Outer, but now the dialog interface has lost
its logic, because the Default also says outer:
o Left
o Right
o Outer
o Default (outer)
Maybe the last entry should be o Inner
Dekel Tsur wrote:
On Wed, Sep 25, 2002 at 09:29:16PM +0900, R. Lahaye wrote:
Today you've committed a patch to forms/form_wrap.fd and FormWrap.C.
You replaced inner by Outer, but now the dialog interface has lost
its logic, because the Default also says outer:
o Left
o Right
o Outer
Dr. Richard E. Hawkins wrote:
This is fresh cvs from today. I created a new document, and ran the
spellchecker on one word. Still not sure, I put in a misspelling, and
ran again. I'm pretty sure I moved the cursor back to the beginning,
and that it took (I might have just assumed).
I
Hi,
In most Xforms (and Qt dialogs as well), I find this function:
bc().addReadOnly(FL_OBJECT * ob)
I don't see any effect when commenting it out in the Xforms dialog code.
What is it supposed to do? Is it still useful and/or relevant?
Thanks,
Rob.
R. Lahaye wrote:
Hi,
In most Xforms (and Qt dialogs as well), I find this function:
bc().addReadOnly(FL_OBJECT * ob)
I don't see any effect when commenting it out in the Xforms dialog code.
What is it supposed to do? Is it still useful and/or relevant?
Another, possibly related
Dekel,
Today you've committed a patch to "forms/form_wrap.fd" and "FormWrap.C".
You replaced inner by Outer, but now the dialog interface has lost
its logic, because the Default also says "outer":
o Left
o Right
o Outer
o Default (outer)
Maybe the last entry should be "o Inner
Dekel Tsur wrote:
> On Wed, Sep 25, 2002 at 09:29:16PM +0900, R. Lahaye wrote:
>
>>Today you've committed a patch to "forms/form_wrap.fd" and "FormWrap.C".
>>You replaced inner by Outer, but now the dialog interface has lost
>>its logic, because t
Dr. Richard E. Hawkins wrote:
> This is fresh cvs from today. I created a new document, and ran the
> spellchecker on one word. Still not sure, I put in a misspelling, and
> ran again. I'm pretty sure I moved the cursor back to the beginning,
> and that it took (I might have just assumed).
I
Hi,
In most Xforms (and Qt dialogs as well), I find this function:
bc().addReadOnly(FL_OBJECT * ob)
I don't see any effect when commenting it out in the Xforms dialog code.
What is it supposed to do? Is it still useful and/or relevant?
Thanks,
Rob.
R. Lahaye wrote:
>
> Hi,
>
> In most Xforms (and Qt dialogs as well), I find this function:
>
> bc().addReadOnly(FL_OBJECT * ob)
>
> I don't see any effect when commenting it out in the Xforms dialog code.
> What is it supposed to do? Is it still useful and/or r
Hi,
I started working on form_wrap.fd dialog, and saw it was related to
this fairly new entry in Insert-Floats menu. What does this do?
I can't see much difference between selecting Outer|Inner|Right|Left,
or enter a value for Width.
Interesting bug: A fresh created wrapfigure, with Outer
Hi,
Would it be sensible to merge Floatflt figure into the Float figure inset,
the same as normal and wide figure now share.
A placement dialog could then look as attached (just rough idea; naming may
need improvement).
The problem is when wanting to switch a float from normal/wide to
Hi,
I started working on form_wrap.fd dialog, and saw it was related to
this fairly new entry in Insert->Floats menu. What does this do?
I can't see much difference between selecting "Outer|Inner|Right|Left",
or enter a value for Width.
"Interesting" bug: A fresh created wrapfigure, with
Hi,
Would it be sensible to merge Floatflt figure into the Float figure inset,
the same as normal and wide figure now share.
A placement dialog could then look as attached (just rough idea; naming may
need improvement).
The problem is when wanting to switch a float from normal/wide to
Lars Gullik Bjønnes wrote:
R. Lahaye [EMAIL PROTECTED] writes:
| Hi,
| In the preferences dialog, Outputs-Misc-Papersize has a choice default, which
| I only can see as a nonsense option.
| 1) This so called default merely refers to the hard coded choice by LyX:
| src/lyxrc.C line
Lars Gullik Bjønnes wrote:
R. Lahaye [EMAIL PROTECTED] writes:
| Hi,
| There are still problems with the layout files and templates.
Yes, I know...
This is the patch that I began on, but never finished:
You don't want to commit this and see how well it works for others
Lars Gullik Bjønnes wrote:
> "R. Lahaye" <[EMAIL PROTECTED]> writes:
>
> | Hi,
>
> | In the preferences dialog, Outputs->Misc->Papersize has a choice "default", which
> | I only can see as a nonsense option.
>
> | 1) This so called
Lars Gullik Bjønnes wrote:
> "R. Lahaye" <[EMAIL PROTECTED]> writes:
>
> | Hi,
>
> | There are still problems with the layout files and templates.
>
> Yes, I know...
>
> This is the patch that I began on, but never finished:
You don't want to commi
Hi,
There are still problems with the layout files and templates.
The layout files need to be fixed with respect to the new .inc files.
I myself am using revtex4.layout, and LyX gets completely muddled up
without the appropriate .inc inclusions in the layout.
I'm afraid (but I'm not sure) that
Hi,
There are still problems with the layout files and templates.
The layout files need to be fixed with respect to the new .inc files.
I myself am using revtex4.layout, and LyX gets completely muddled up
without the appropriate .inc inclusions in the layout.
I'm afraid (but I'm not sure) that
Jean-Marc Lasgouttes wrote:
R == R Lahaye [EMAIL PROTECTED] writes:
R Jean-Marc Lasgouttes wrote:
R == R Lahaye [EMAIL PROTECTED] writes:
R Also, I still don't see how the dialog can find out about the
R paragraph's original default. Or am I missing something here?
It has to find out
Hi,
In the preferences dialog, Outputs-Misc-Papersize has a choice default, which
I only can see as a nonsense option.
1) This so called default merely refers to the hard coded choice by LyX:
src/lyxrc.C line 191
default_papersize = BufferParams::PAPER_USLETTER;
This seems
Jean-Marc Lasgouttes wrote:
>>>>>>"R" == R Lahaye <[EMAIL PROTECTED]> writes:
>>>>>
>
> R> Jean-Marc Lasgouttes wrote:
>
>>>>>>>>"R" == R Lahaye <[EMAIL PROTECTED]> writes:
>>>>
Hi,
In the preferences dialog, Outputs->Misc->Papersize has a choice "default", which
I only can see as a nonsense option.
1) This so called "default" merely refers to the hard coded choice by LyX:
src/lyxrc.C line 191
default_papersize = BufferParams::PAPER_USLETTER;
This
Andre Poenitz wrote:
On Fri, Sep 20, 2002 at 08:06:37AM +0200, Andre' Poenitz wrote:
Why do I need a login to file bugs on bugzilla? If I were just using LyX
I'd certainly not create an account there just to file a bug report.
What do I do if I forgot my username? [Well, I don't think I
John Levon wrote:
On Fri, Sep 20, 2002 at 05:02:02PM +0200, Andre Poenitz wrote:
Oh come on, it takes two seconds
It's not a matter of time, it's about putting private information in a
public place. _We_ are interested in getting bug reports after all.
Or perhaps you have some mega
Andre Poenitz wrote:
New Doc, Layout-Doceument-Save as Document Defaults, Yes. Boom.
Does anybody else see this?
This is how far I can trace this bug:
The offending action goes as follows:
FormDocument.C: saveParamsAsDefault(BufferParams const params)
its last statement is return
Andre Poenitz wrote:
> On Fri, Sep 20, 2002 at 08:06:37AM +0200, Andre' Poenitz wrote:
>
>>Why do I need a login to file bugs on bugzilla? If I were just using LyX
>>I'd certainly not create an account there just to file a bug report.
>>
>>What do I do if I forgot my username? [Well, I don't
John Levon wrote:
> On Fri, Sep 20, 2002 at 05:02:02PM +0200, Andre Poenitz wrote:
>
>
>>>Oh come on, it takes two seconds
>>
>>It's not a matter of time, it's about putting private information in a
>>public place. _We_ are interested in getting bug reports after all.
>
>
> Or perhaps you
Andre Poenitz wrote:
> New Doc, Layout->Doceument->Save as Document Defaults, Yes. Boom.
>
> Does anybody else see this?
This is how far I can trace this bug:
The offending action goes as follows:
FormDocument.C: saveParamsAsDefault(BufferParams const )
its last statement is "return
Lars Gullik Bjønnes wrote:
Garst R. Reese [EMAIL PROTECTED] writes:
| Lars Gullik Bjønnes wrote:
| real Default button could be added, besides it is nice to know what
| the default is as well.
| This is a problem with many of the Default buttons. I keep asking
| myself what's that mean?
Lars Gullik Bjønnes wrote:
R. Lahaye [EMAIL PROTECTED] writes:
|
| I'd say: call it Default and let the tooltip explain further; instead
| of using asterisk with a tooltip that says Default.
Using a tooltip for this is about the worst solution ever...
If you are so afraid of special
Jean-Marc Lasgouttes wrote:
R == R Lahaye [EMAIL PROTECTED] writes:
R Also, I still don't see how the dialog can find out about the
R paragraph's original default. Or am I missing something here?
It has to find out the layout of the paragraph and find it there.
Yes, I figured
Hi,
In xforms_helpers.C, there is the following in function formatted():
string::size_type const nxtpos1 = sin.find(' ', curpos);
string::size_type const nxtpos2 = sin.find('\n', curpos);
string::size_type const nxtpos = std::min(nxtpos1, nxtpos1);
The last line
Lars Gullik Bjønnes wrote:
> "Garst R. Reese" <[EMAIL PROTECTED]> writes:
>
> | Lars Gullik Bjønnes wrote:
> | > real "Default" button could be added, besides it is nice to know what
> | > the default is as well.
> | This is a problem with many of the "Default" buttons. I keep asking
> | myself
Lars Gullik Bjønnes wrote:
> "R. Lahaye" <[EMAIL PROTECTED]> writes:
> |
> | I'd say: call it "Default" and let the tooltip explain further; instead
> | of using asterisk with a tooltip that says "Default".
>
> Using a tooltip for this
Jean-Marc Lasgouttes wrote:
>>>>>>"R" == R Lahaye <[EMAIL PROTECTED]> writes:
>>>>>
>
> R> Also, I still don't see how the dialog can find out about the
> R> paragraph's original default. Or am I missing something here?
>
>
Hi,
In xforms_helpers.C, there is the following in function formatted():
string::size_type const nxtpos1 = sin.find(' ', curpos);
string::size_type const nxtpos2 = sin.find('\n', curpos);
string::size_type const nxtpos = std::min(nxtpos1, nxtpos1);
The last line
Hi,
I'm continuing reworking the xforms dialogs, for after the freeze, that is :).
Attached is a screenshot of my new Paragraph Layout.
I think this reflects much better the way one uses this dialog:
widgets are grouped together according to Above/Text/Below.
Some ideas are copied from Qt,
Christian Ridderström wrote:
How about a dialog like this:
--
Paragraph body
No indent Alignment
[] (left) (centre) (right) (block)
Line spacing:[Default][]
John Levon wrote:
On Wed, Sep 18, 2002 at 05:20:09PM +0900, Rob Lahaye wrote:
Would be cute to replace these words by small icons; you know, the ones
used by any wordprocessor: 5 stacked lines that show what sort of
alignment it does. Would that be a way to go?
Sounds like a bad idea to
Lars Gullik Bjønnes wrote:
Dekel Tsur [EMAIL PROTECTED] writes:
| On Wed, Sep 18, 2002 at 09:59:56AM +0200, Lars Gullik Bj?nnes wrote:
| Should Block alignment be better named Justified (as in Qt) ?
Left justified or Right justfied? or perhaps Block justified.
As I learned it Justified
Hi,
I'm continuing reworking the xforms dialogs, for after the freeze, that is :).
Attached is a screenshot of my new "Paragraph Layout".
I think this reflects much better the way one uses this dialog:
widgets are grouped together according to Above/Text/Below.
Some ideas are copied from Qt,
Christian Ridderström wrote:
>
> How about a dialog like this:
>
> --
> Paragraph body
>
> No indent Alignment
> [] (left) (centre) (right) (block)
>
> Line spacing:
John Levon wrote:
> On Wed, Sep 18, 2002 at 05:20:09PM +0900, Rob Lahaye wrote:
>
>>Would be cute to replace these words by small icons; you know, the ones
>>used by any wordprocessor: 5 stacked lines that show what sort of
>>alignment it does. Would that be a way to go?
>
>
> Sounds like a
Lars Gullik Bjønnes wrote:
> Dekel Tsur <[EMAIL PROTECTED]> writes:
>
> | On Wed, Sep 18, 2002 at 09:59:56AM +0200, Lars Gullik Bj?nnes wrote:
>
>>>| Should "Block" alignment be better named "Justified" (as in Qt) ?
>>>
>>>Left justified or Right justfied? or perhaps Block justified.
>>>
>>>As
Dr. Richard E. Hawkins wrote:
On Tue, Sep 17, 2002 at 04:57:31PM +0200, Lars Gullik Bj?nnes wrote:
Dr. Richard E. Hawkins [EMAIL PROTECTED] writes:
| This is the lyx display, not the rendered latex.
| The Author is overwritten by Abstract in article class.
Same here, but with RevTeX4
R. Lahaye wrote:
Dr. Richard E. Hawkins wrote:
On Tue, Sep 17, 2002 at 04:57:31PM +0200, Lars Gullik Bj?nnes wrote:
Dr. Richard E. Hawkins [EMAIL PROTECTED] writes:
| This is the lyx display, not the rendered latex.
| The Author is overwritten by Abstract in article class.
Same
Dr. Richard E. Hawkins wrote:
> On Tue, Sep 17, 2002 at 04:57:31PM +0200, Lars Gullik Bj?nnes wrote:
>
>>"Dr. Richard E. Hawkins" <[EMAIL PROTECTED]> writes:
>
>
>>| This is the lyx display, not the rendered latex.
>
>
>>| The Author is overwritten by "Abstract" in article class.
Same here,
R. Lahaye wrote:
> Dr. Richard E. Hawkins wrote:
>
>> On Tue, Sep 17, 2002 at 04:57:31PM +0200, Lars Gullik Bj?nnes wrote:
>>
>>> "Dr. Richard E. Hawkins" <[EMAIL PROTECTED]> writes:
>>
>>
>>
>>> | This is the lyx dis
Andre Poenitz wrote:
As I have been the only person who found it sensible to have { and \{ act
as they do in LaTeX I swapped this. So:
Typing { produces blue { on screen and is written as \{
} } \}
\{ red {}
Joao Luis M. Assirati wrote:
Hello,
I use a Debian system with qt2 packages installed. When in 1.3.0cvs I try
configure --with-frontend=qt
I get
checking for Qt library name... failed
configure: error: Cannot compile a simple Qt executable. Check you have
the right $QTDIR !
Hi,
I'm reworking the Float Options dialog right now and I want
to remove the Float Defaults button here (upper left corner).
That button disables all other Float placement buttons in the dialog.
Moreover, disabling *all* placement buttons (including the Default) will
automagically enable the
Joao Luis M. Assirati wrote:
configure --with-qt-includes=/usr/include/qt/ --with-frontend=qt
works for me! I suppose that qt includes are placed in /usr/local/include,
so in a system instalation this should go simply into /usr/include, but
Debian people (that is not surprise...) changed
Juergen Spitzmueller wrote:
R. Lahaye wrote:
(2) and (3) should be implemented with a better button disable/enable
policy than we have now.
What special problems do you have with that policy? It is very clever IMHO.
No, it's not. It's dumb. It removes settings, that need not be removed
Andre Poenitz wrote:
> As I have been the only person who found it sensible to have { and \{ act
> as they do in LaTeX I swapped this. So:
>
> Typing { produces blue { on screen and is written as \{
> } } \}
> \{
Joao Luis M. Assirati wrote:
> Hello,
>
> I use a Debian system with qt2 packages installed. When in 1.3.0cvs I try
>
> configure --with-frontend=qt
>
> I get
>
> checking for Qt library name... failed
> configure: error: Cannot compile a simple Qt executable. Check you have
> the right
Hi,
I'm reworking the "Float Options" dialog right now and I want
to remove the "Float Defaults" button here (upper left corner).
That button disables all other Float placement buttons in the dialog.
Moreover, disabling *all* placement buttons (including the Default) will
automagically enable
Joao Luis M. Assirati wrote:
>
> configure --with-qt-includes=/usr/include/qt/ --with-frontend=qt
>
> works for me! I suppose that qt includes are placed in /usr/local/include,
> so in a system instalation this should go simply into /usr/include, but
> Debian people (that is not surprise...)
Juergen Spitzmueller wrote:
> R. Lahaye wrote:
>
>>(2) and (3) should be implemented with a better button disable/enable
>>policy than we have now.
>
>
> What special problems do you have with that policy? It is very clever IMHO.
No, it's not. It's dumb. It
Hi,
This makes the dialogs only less bulky. Hardly any code cleaning done.
(the filedialog code needs a clean up, but that's for after the freeze).
Please apply, if OK.
src/frontends/xforms/ChangeLog|6
src/frontends/xforms/FormTexinfo.C| 45 ++---
Allan Rae wrote:
John Levon wrote:
However, there is some serious problems. Different invocations of the
print dialog is forgetting various settings such as number of copies,
all or range etc. Please do a check and make sure they are remembered
properly so when you bring up the dialog again, the
Angus Leeming wrote:
On Thursday 12 September 2002 8:33 am, R. Lahaye wrote:
This makes the dialogs only less bulky. Hardly any code
cleaning done. (the filedialog code needs a clean up, but
that's for after the freeze).
Well personally I think that the new TeXInfo patch is just ugly
Angus Leeming wrote:
I don't think that they're reset at all. That would imply that
they're stored and I don't think that they are. What you are
getting is the settings of a newly constructed PrinterParams
instance.
Why not ignore pp in FormPrint::update if it's causing you
angst?
Hi,
Sometime back all email addresses have been removed from the header lines in
the files, since these email addresses are listed already in the CREDITS file.
Why not do the same with the ChangeLogs?
I would be pleased to be freed from typing my email address each time I
type an new entry in
Angus Leeming wrote:
On Thursday 12 September 2002 11:13 am, Angus Leeming wrote:
Perhaps something like:
void FormPrint::update()
{
PrinterParams pp = controller().params();
if (pp.file_name == getString(dialog_-input_file)
return;
...
}
would do the
Hi,
I had a look at the Print dialog of Qt, and agreed with John's layout.
A small modification is applied to the xforms print dialog.
Also, a minor modification to graphics dialog.
Please apply before freeze ;).
Cheers,
Rob.
src/frontends/xforms/ChangeLog |5 +
Hi,
I improved the layout of the reference dialog.
Please apply.
Eek, I'm on the edge; is it still Thursday overthere in EU ?
Cheers,
Rob.
ChangeLog |4
forms/form_ref.fd | 32
2 files changed, 20 insertions(+), 16 deletions(-)
Hi,
This makes the dialogs only less bulky. Hardly any code cleaning done.
(the filedialog code needs a clean up, but that's for after the freeze).
Please apply, if OK.
src/frontends/xforms/ChangeLog|6
src/frontends/xforms/FormTexinfo.C| 45 ++---
Allan Rae wrote:
>>John Levon wrote:
>>
>>>However, there is some serious problems. Different invocations of the
>>>print dialog is forgetting various settings such as number of copies,
>>>all or range etc. Please do a check and make sure they are remembered
>>>properly so when you bring up the
Angus Leeming wrote:
> On Thursday 12 September 2002 8:33 am, R. Lahaye wrote:
>
>>This makes the dialogs only less bulky. Hardly any code
>>cleaning done. (the filedialog code needs a clean up, but
>>that's for after the freeze).
>
> Well personally I think that
Angus Leeming wrote:
>
> I don't think that they're reset at all. That would imply that
> they're stored and I don't think that they are. What you are
> getting is the settings of a newly constructed PrinterParams
> instance.
>
> Why not ignore "pp" in FormPrint::update if it's causing you
Hi,
Sometime back all email addresses have been removed from the header lines in
the files, since these email addresses are listed already in the CREDITS file.
Why not do the same with the ChangeLogs?
I would be pleased to be freed from typing my email address each time I
type an new entry in
Angus Leeming wrote:
> On Thursday 12 September 2002 11:13 am, Angus Leeming wrote:
> Perhaps something like:
>
>>void FormPrint::update()
>>{
>> PrinterParams & pp = controller().params();
>>
>> if (pp.file_name == getString(dialog_->input_file)
>> return;
>>
>> ...
Hi,
I had a look at the Print dialog of Qt, and agreed with John's layout.
A small modification is applied to the xforms print dialog.
Also, a minor modification to graphics dialog.
Please apply before freeze ;).
Cheers,
Rob.
src/frontends/xforms/ChangeLog |5 +
Hi,
I improved the layout of the reference dialog.
Please apply.
Eek, I'm on the edge; is it still Thursday overthere in EU ?
Cheers,
Rob.
ChangeLog |4
forms/form_ref.fd | 32
2 files changed, 20 insertions(+), 16 deletions(-)
Hi,
Attached is the new Print dialog in xforms.
Please test, if OK, apply.
Regards,
Rob.
src/ChangeLog|4
src/PrinterParams.h | 80 ++---
src/frontends/ChangeLog |4
src/frontends/Liason.C |
R. Lahaye wrote:
Hi,
Attached is the new Print dialog in xforms.
Argh, and here is the patch.
Rob.
BetterPrintDialog.diff.gz
Description: application/gzip
R. Lahaye wrote:
R. Lahaye wrote:
Hi,
Attached is the new Print dialog in xforms.
Argh, and here is the patch.
Which is the wrong patch file sorry!
Patch file follows shortly.
Rob.
Here it is; attached!
Rob.
BetterPrintDialog.diff.gz
Description: application/gzip
John Levon wrote:
On Wed, Sep 11, 2002 at 09:52:21PM -0300, Garst R. Reese wrote:
I've already deleted the msgs, but noticed that you were worried about
being able to deselect both odd and even. In this case I thing that
All should be implied, the same a selecting both. Note that Acroread
Angus,
Polished a few tooltips texts in FormGraphics.C.
A tiny cosmetic change to the file tab of the dialog layout.
The rotateOrigin variable now defaults to empty.
Patch attached.
Please apply.
src/frontends/xforms/ChangeLog |6 ++
src/frontends/xforms/FormGraphics.C
John Levon wrote:
On Thu, Sep 12, 2002 at 11:08:17AM +0900, R. Lahaye wrote:
Moreover, I followed Acroread's policy to print all pages when either both
(odd/even) are selected, or both are unselected. If, and only if, one is
selected, the code investigates which one, and then does the odd
R. Lahaye wrote:
Angus,
Polished a few tooltips texts in FormGraphics.C.
A tiny cosmetic change to the file tab of the dialog layout.
The rotateOrigin variable now defaults to empty.
Patch attached.
Please apply.
src/frontends/xforms/ChangeLog |6 ++
src
Hi,
Attached is the new Print dialog in xforms.
Please test, if OK, apply.
Regards,
Rob.
src/ChangeLog|4
src/PrinterParams.h | 80 ++---
src/frontends/ChangeLog |4
src/frontends/Liason.C |
R. Lahaye wrote:
>
> Hi,
>
> Attached is the new Print dialog in xforms.
Argh, and here is the patch.
Rob.
BetterPrintDialog.diff.gz
Description: application/gzip
R. Lahaye wrote:
> R. Lahaye wrote:
>
>>
>> Hi,
>>
>> Attached is the new Print dialog in xforms.
>
>
> Argh, and here is the patch.
>
Which is the wrong patch file sorry!
Patch file follows shortly.
Rob.
Here it is; attached!
Rob.
BetterPrintDialog.diff.gz
Description: application/gzip
1 - 100 of 1242 matches
Mail list logo
