On Friday 27 September 2002 7:36 am, R. Lahaye wrote:
> 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
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 func
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 limite
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? I
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
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
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());
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?
> T
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
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
>
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
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.
12 matches
Mail list logo
