Juergen Spitzmueller wrote:
Not good enough. I have left out the «guillemots»
Hmpff.
The guillemots need the brackets when they are used as closing quotes
(otherwise the space to the next word is swapped). I have readded them again,
so this patch is sane.
Sorry,
Jürgen.
Index:
Dekel Tsur [EMAIL PROTECTED] writes:
| I'm going to apply the following patch (which was already applied in 1.2.0).
ok
--
Lgb
Andre Poenitz [EMAIL PROTECTED] writes:
| Simple fix attached. Ok to apply?
yes.
--
Lgb
Angus Leeming [EMAIL PROTECTED] writes:
| Simple fix attached. Ok to apply?
yes.
--
Lgb
Garst R. Reese [EMAIL PROTECTED] writes:
| Upgrading A's box to xforms-1.0RC4 cured the problem.
Ok, then I'll consider this case closed.
--
Lgb
On Thursday 26 September 2002 2:53 am, Allan Rae wrote:
On Mon, 23 Sep 2002, Angus Leeming wrote:
Of course if we can test whether the pipe is open before
attempting to unlink it, then we could definitely delete
pipes that are closed...
Angus (ignorance showing once again).
Can't we
On Thursday 26 September 2002 5:39 am, 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
ÕâÊÇÒ»¸öHTML¸ñʽµÄÓʼþ/This is a html format mail
Angus Leeming wrote:
On Thursday 26 September 2002 5:39 am, 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
On Thursday 26 September 2002 11:16 am, Rob Lahaye wrote:
In FormDocument.C I find these two types of calls:
bc().addReadOnly(language_-choice_inputenc);
and
bc_.addReadOnly(options_-counter_secnumdepth);
Why do we have bc() in the first, and bc_ in the second call?
Typo, or
Incidentally, Rob, I see some new code in FormBase::show that I
understand you added:
if (iconify_policy == 0) {
// set title for minimized form
string const minimize_title = title_;
fl_winicontitle(form()-window, minimize_title.c_str());
Angus Leeming wrote:
Incidentally, Rob, I see some new code in FormBase::show that I
understand you added:
if (iconify_policy == 0) {
// set title for minimized form
string const minimize_title = title_;
fl_winicontitle(form()-window,
On Thursday 26 September 2002 11:52 am, Rob Lahaye wrote:
It's feature freeze and I'm not that familiar with such kind
of code. If you see a reasonable fix for this leak, could you
do the patch?
Features do not generally mean new memory leaks...
I'll have a look.
Angus
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
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 work.
The patch attached should do the trick. Could someone with
valgrind test that it does indeed cure a memory leak?
Just open and close the About LyX dialog a few times and then
exit.
Regards,
Angus
Index: src/frontends/xforms/ChangeLog
On Thursday 26 September 2002 12:06 pm, Angus Leeming wrote:
The patch attached should do the trick. Could someone with
valgrind test that it does indeed cure a memory leak?
Just open and close the About LyX dialog a few times and then
exit.
This button should not be set (ie should be
On Thu, Sep 26, 2002 at 11:21:49AM +, Edwin Leuven wrote:
I have written the document controller:
controllers/ControlDocument.C
controllers/ControlDocument.h
and am nearly done implementing the qt document dialog.
Great stuff !
john
--
The only perfect circle on the human body
Edwin Leuven [EMAIL PROTECTED] writes:
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
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
Sure, but currently I'm only little familiar with the controller code.
That understanding may improve in time, so I'll give this a shot then.
If your Document controller is similar to the way other controllers work, I
may at first use existing code elsewhere and implement it for
On Thu, Sep 26, 2002 at 10:49:04AM +0900, R. Lahaye wrote:
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
Angus Leeming wrote:
;-) The problem is that whilst LyX responds to a Hello from a
client, sending out a Hello in reply, clients are not required
to respond in similar fashion.
It would of course be straightforward to enforce this. Something
like
I don't think you understood what
On Thursday 26 September 2002 3:35 pm, Juergen Vigna wrote:
Angus Leeming wrote:
;-) The problem is that whilst LyX responds to a Hello
from a client, sending out a Hello in reply, clients are
not required to respond in similar fashion.
It would of course be straightforward to enforce
Angus Leeming wrote:
Incidentally, I see you are using [EMAIL PROTECTED] Note that you are
listed in CREDITS as [EMAIL PROTECTED] I guess that this is now out of
date?
Yes [EMAIL PROTECTED] is the good one :)
Jug
--
I've seen a few varieties of this--the depth cascades rightward instead
of coming back on old files. I've attached a file that does this.
But the conversion now runs automatically!
hawk
--
Richard E. Hawkins, Asst. Prof. of Economics/\ ASCII ribbon campaign
[EMAIL PROTECTED] Smeal
Trivial patch attached. Ok to commit?
Angus
ps, shall I wait for someone to run my fix for leaking pixmap
icons through valgrind or just commit it anyway. (It does work
and does cure a leak.)
A
Index: ChangeLog
===
RCS file:
I'm coauthoring a paper that will ultimately be submitted in word.
There's no way that I'm going to use equation editor until the final
draft, though :)
I'm trying to send the doc to html and use pngs for the equation for the
momennt. If lyx created these images during export, I have no idea
oops; here's the file.
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language english
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
I've fixed this today.
Great! Just updated my cvs version and it works well now... thanks
Dekel..
nirmal
Angus Leeming wrote:
On Thursday 26 September 2002 5:39 am, R. Lahaye wrote:
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
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
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 a limited set of
R. Lahaye wrote:
As a test example, I have attached how this may look like in the graphics
dialog (the text_warning is still there in the example, but that should
then go!)
IMHO the warning message is a bit clearer for new users, but I don't mind as
long as there is some kind of visual
Juergen Spitzmueller wrote:
> Not good enough. I have left out the «guillemots»
Hmpff.
The guillemots need the brackets when they are used as closing quotes
(otherwise the space to the next word is swapped). I have readded them again,
so this patch is sane.
Sorry,
Jürgen.
Index:
Dekel Tsur <[EMAIL PROTECTED]> writes:
| I'm going to apply the following patch (which was already applied in 1.2.0).
ok
--
Lgb
Andre Poenitz <[EMAIL PROTECTED]> writes:
| Simple fix attached. Ok to apply?
yes.
--
Lgb
Angus Leeming <[EMAIL PROTECTED]> writes:
| Simple fix attached. Ok to apply?
yes.
--
Lgb
"Garst R. Reese" <[EMAIL PROTECTED]> writes:
| Upgrading A's box to xforms-1.0RC4 cured the problem.
Ok, then I'll consider this case closed.
--
Lgb
On Thursday 26 September 2002 2:53 am, Allan Rae wrote:
> On Mon, 23 Sep 2002, Angus Leeming wrote:
> > Of course if we can test whether the pipe is open before
> > attempting to unlink it, then we could definitely delete
> > pipes that are closed...
> >
> > Angus (ignorance showing once again).
On Thursday 26 September 2002 5:39 am, 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
>
ÕâÊÇÒ»¸öHTML¸ñʽµÄÓʼþ/This is a html format mail
Angus Leeming wrote:
> On Thursday 26 September 2002 5:39 am, 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
On Thursday 26 September 2002 11:16 am, Rob Lahaye wrote:
> In FormDocument.C I find these two types of calls:
>
> bc().addReadOnly(language_->choice_inputenc);
> and
> bc_.addReadOnly(options_->counter_secnumdepth);
>
> Why do we have bc() in the first, and bc_ in the second call?
>
Incidentally, Rob, I see some new code in FormBase::show that I
understand you added:
if (iconify_policy == 0) {
// set title for minimized form
string const minimize_title = title_;
fl_winicontitle(form()->window, minimize_title.c_str());
Angus Leeming wrote:
> Incidentally, Rob, I see some new code in FormBase::show that I
> understand you added:
>
> if (iconify_policy == 0) {
> // set title for minimized form
> string const minimize_title = title_;
>
On Thursday 26 September 2002 11:52 am, Rob Lahaye wrote:
> It's feature freeze and I'm not that familiar with such kind
> of code. If you see a reasonable fix for this leak, could you
> do the patch?
"Features" do not generally mean new memory leaks...
I'll have a look.
Angus
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
> 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
The patch attached should do the trick. Could someone with
valgrind test that it does indeed cure a memory leak?
Just open and close the About LyX dialog a few times and then
exit.
Regards,
Angus
Index: src/frontends/xforms/ChangeLog
On Thursday 26 September 2002 12:06 pm, Angus Leeming wrote:
> The patch attached should do the trick. Could someone with
> valgrind test that it does indeed cure a memory leak?
>
> Just open and close the About LyX dialog a few times and then
> exit.
This button should not be set (ie should be
On Thu, Sep 26, 2002 at 11:21:49AM +, Edwin Leuven wrote:
> I have written the document controller:
>
> controllers/ControlDocument.C
> controllers/ControlDocument.h
>
> and am nearly done implementing the qt document dialog.
Great stuff !
john
--
"The only perfect circle on the human
Edwin Leuven <[EMAIL PROTECTED]> writes:
>> 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
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
> Sure, but currently I'm only little familiar with the controller code.
> That understanding may improve in time, so I'll give this a shot then.
> If your Document controller is similar to the way other controllers work, I
> may at first use existing code elsewhere and implement it for
>
On Thu, Sep 26, 2002 at 10:49:04AM +0900, R. Lahaye wrote:
> 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
Angus Leeming wrote:
> ;-) The problem is that whilst LyX responds to a "Hello" from a
> client, sending out a "Hello" in reply, clients are not required
> to respond in similar fashion.
>
> It would of course be straightforward to enforce this. Something
> like
I don't think you understood
On Thursday 26 September 2002 3:35 pm, Juergen Vigna wrote:
> Angus Leeming wrote:
> > ;-) The problem is that whilst LyX responds to a "Hello"
> > from a client, sending out a "Hello" in reply, clients are
> > not required to respond in similar fashion.
> >
> > It would of course be
Angus Leeming wrote:
> Incidentally, I see you are using [EMAIL PROTECTED] Note that you are
> listed in CREDITS as [EMAIL PROTECTED] I guess that this is now out of
> date?
Yes [EMAIL PROTECTED] is the good one :)
Jug
--
I've seen a few varieties of this--the depth cascades rightward instead
of coming back on old files. I've attached a file that does this.
But the conversion now runs automatically!
hawk
--
Richard E. Hawkins, Asst. Prof. of Economics/"\ ASCII ribbon campaign
[EMAIL PROTECTED] Smeal
Trivial patch attached. Ok to commit?
Angus
ps, shall I wait for someone to run my fix for leaking pixmap
icons through valgrind or just commit it anyway. (It does work
and does cure a leak.)
A
Index: ChangeLog
===
RCS file:
I'm coauthoring a paper that will ultimately be submitted in word.
There's no way that I'm going to use equation editor until the final
draft, though :)
I'm trying to send the doc to html and use pngs for the equation for the
momennt. If lyx created these images during export, I have no idea
oops; here's the file.
#LyX 1.3 created this file. For more info see http://www.lyx.org/
\lyxformat 221
\textclass article
\language english
\inputencoding auto
\fontscheme default
\graphics default
\paperfontsize default
\papersize Default
\paperpackage a4
\use_geometry 0
\use_amsmath 0
>
> I've fixed this today.
>
Great! Just updated my cvs version and it works well now... thanks
Dekel..
nirmal
Angus Leeming wrote:
> On Thursday 26 September 2002 5:39 am, R. Lahaye wrote:
>
>>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?
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
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 a
R. Lahaye wrote:
> As a test example, I have attached how this may look like in the graphics
> dialog (the text_warning is still there in the example, but that should
> then go!)
IMHO the warning message is a bit clearer for new users, but I don't mind as
long as there is some kind of visual
68 matches
Mail list logo
