On Thursday 12 September 2002 1:06 pm, R. Lahaye wrote:
> Ah, now I got it!
>
> If I type my own filename, everthing gets reset, otherwise
> not. Don't like that. Why do you want that?
No, this says that if you open a new buffer then reset the
dialog, else don't.
> I suggest something like:
>
>
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;
>>
>> ...
>
On Thu, Sep 12, 2002 at 11:13:09AM +0100, Angus Leeming wrote:
> and decide what to do with it. Perhaps something like:
>
> void FormPrint::update()
> {
> PrinterParams & pp = controller().params();
>
> if (pp.file_name == getString(dialog_->input_file)
> return;
>
>
On Thu, Sep 12, 2002 at 01:43:00PM +0900, R. Lahaye wrote:
> From/to remembered? Here at my end, the entire printer dialogs gets reset,
> including the from/to values.
Yes, you're right, consequence of the way qt dialog gets filled. Sorry
for the confusion.
> Every time, the controller().params
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 trick.
On Thu, Sep 12, 2002 at 11:13:09AM +0100, Angus Leeming wrote:
> >
> > But if it is in Buffer, it should be stored in the .lyx,
> > shouldn't it?
>
> I don't understand your meaning. Are you saying that /if/ we
> store PrinterParams then we should output the stored settings?
> Ridiculous.
I ha
On Thursday 12 September 2002 11:37 am, Andre Poenitz wrote:
> On Thu, Sep 12, 2002 at 10:58:46AM +0100, Angus Leeming wrote:
> > > Should that be some global thing like lyxrc?
> >
> > Only PrinterParams contains file-specific info too:
> >
> > string file_name;
> > unsigned int from_page;
On Thu, Sep 12, 2002 at 10:58:46AM +0100, Angus Leeming wrote:
> > Should that be some global thing like lyxrc?
>
> Only PrinterParams contains file-specific info too:
>
> string file_name;
> unsigned int from_page;
> unsigned int to_page;
Hm...
But if it is in Buffer, it sho
On Thursday 12 September 2002 11:25 am, Andre Poenitz wrote:
> On Thu, Sep 12, 2002 at 09:55:39AM +0100, Angus Leeming wrote:
> > Well that's not surprising now is it. The graphics params
> > are /stored/ by each graphics inset. If you want to /store/
> > the printer params then they'll be remembe
On Thu, Sep 12, 2002 at 09:55:39AM +0100, Angus Leeming wrote:
> Well that's not surprising now is it. The graphics params are
> /stored/ by each graphics inset. If you want to /store/ the
> printer params then they'll be remembered too.
>
> Where's a good place to store them? In bufferparams p
On Thursday 12 September 2002 10:16 am, R. Lahaye wrote:
> Since I'm a little more familiar with FormGraphics.C, I had a
> look at FormGraphics::update() and found code similar to
> FormPrint::update(). Only, the Graphics dialog remembers
> previous settings, but the print dialog doesn't. Hmmm. I'
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
>
On Thursday 12 September 2002 9:55 am, R. Lahaye wrote:
> Anyway, I'm still puzzled where, why and how this reset of
> print parameters is actually done. Moreover, we won't make it
> before feature freeze :(.
>
> > I haven't looked at this stuff in nearly 18months. Angus
> > did the split I think
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 di
On Thursday 12 September 2002 9:38 am, Allan Rae wrote:
> > 149 void FormPrint::update()
> > 150 {
> > 151PrinterParams & pp = controller().params();
> >
> >
> > Every time, the controller().params() is called, it gives a
> > brand new set of values, unrelated to previous input. So I
> >
Finally online again to catchup with your doings. Seem to be making
good progress so far...
On Thu, 12 Sep 2002, R. Lahaye wrote:
> John Levon wrote:
> >
> > However, there is some serious problems. Different invocations of the
> > print dialog is forgetting various settings such as number of
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 old val
On Thu, Sep 12, 2002 at 11:38:44AM +0900, R. Lahaye wrote:
>"-c " for non-collate (i.e. sorted is NOT checked in Xforms dialog)
>"-C " for collate (i.e. with sorted checked in Xforms dialog).
Thank you. It works.
> Is "sorted" an OK naming for the check button?
No opinion.
However, th
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 th
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/even
> printing.
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 A
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
> has an "All" bu
Andre Poenitz wrote:
> On Wed, Sep 11, 2002 at 11:51:10AM +0900, R. Lahaye wrote:
>
>>At present you must choose one of "All pages", "Only odd" or "Only even".
>>In addition, you can set for each of those the page range from/to. That
>>is what I found very strange and bad design. What means: "All
On Wed, Sep 11, 2002 at 11:51:10AM +0900, R. Lahaye wrote:
> At present you must choose one of "All pages", "Only odd" or "Only even".
> In addition, you can set for each of those the page range from/to. That
> is what I found very strange and bad design. What means: "All pages, from
> 4 to 17" ?
On Wed, Sep 11, 2002 at 12:48:33PM +0900, R. Lahaye wrote:
> Other interesting part of Acroread, is the odd/even policy.
> It has two check buttons, one for Odd and one for Even, and both are
> enabled by default, which implies all pages! We could do the same.
Sounds good to me.
regards
john
-
Garst R. Reese wrote:
> you might want to look at Acrobat's print form for ideas.
> Garst
Thanks, indeed useful.
From/to in Acroread 5, does, for example:
From [ 1 ] To [ 1 ] of 11
I copy its From/To defaults. Don't know whether the "of 11" appendix
is feasible in our setup. You need
On Wed, Sep 11, 2002 at 11:51:10AM +0900, R. Lahaye wrote:
> At present you must choose one of "All pages", "Only odd" or "Only
> even". In addition, you can set for each of those the page range
> from/to. That is what I found very strange and bad design. What means:
> "All pages, from 4 to 17"
John Levon wrote:
> On Wed, Sep 11, 2002 at 11:34:13AM +0900, R. Lahaye wrote:
>
>
>>Since both of you are listed as authors of the Xforms Printer dialog:
>>
>>Would you mind me simplifying the from/to page stuff?
>
>
> This is going way back, but I think Allan had a reasonable justification
>
On Wed, Sep 11, 2002 at 11:34:13AM +0900, R. Lahaye wrote:
> Since both of you are listed as authors of the Xforms Printer dialog:
>
> Would you mind me simplifying the from/to page stuff?
This is going way back, but I think Allan had a reasonable justification
in this case, if I remember right
Angus Leeming wrote:
> On Tuesday 10 September 2002 4:57 pm, R. Lahaye wrote:
>
>>Angus Leeming wrote:
>>
>>>On Tuesday 10 September 2002 4:40 pm, R. Lahaye wrote:
>>>
Hi,
I have "fdesigned" a new layout for the printer dialog.
Before doing all the required code modification to
>
On Tuesday 10 September 2002 4:57 pm, R. Lahaye wrote:
> Angus Leeming wrote:
> > On Tuesday 10 September 2002 4:40 pm, R. Lahaye wrote:
> >>Hi,
> >>
> >>I have "fdesigned" a new layout for the printer dialog.
> >>Before doing all the required code modification to
> >>implement this, I would like
Angus Leeming wrote:
> On Tuesday 10 September 2002 4:40 pm, R. Lahaye wrote:
>
>>Hi,
>>
>>I have "fdesigned" a new layout for the printer dialog.
>>Before doing all the required code modification to
>>implement this, I would like to know if it's OK.
>>
>>fdesign screenshot is attached.
>>
>>Plea
On Tuesday 10 September 2002 4:40 pm, R. Lahaye wrote:
> Hi,
>
> I have "fdesigned" a new layout for the printer dialog.
> Before doing all the required code modification to
> implement this, I would like to know if it's OK.
>
> fdesign screenshot is attached.
>
> Please let me know what you think
Hi,
I have "fdesigned" a new layout for the printer dialog.
Before doing all the required code modification to
implement this, I would like to know if it's OK.
fdesign screenshot is attached.
Please let me know what you think of this.
Regards,
Rob.
34 matches
Mail list logo
