[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ptp-dev] A couple PTP questions
|
I haven't looked at that API specifically (shot in the dark here) but
perhaps canSave() might mean all pages of a wizard/launch/multi-page thing
are ok to save,
and isValid() might mean the current page only?
I know the PTP preferences pages used to get stuck if you got in an invalid
state and it wouldn't let you leave until you gave it something "valid" but
there wasn't anything valid to give it.
Or something like that.
...Beth
Beth Tibbitts (859) 243-4981 (TL 545-4981)
High Productivity Tools / Parallel Tools http://eclipse.org/ptp
IBM T.J.Watson Research Center
Mailing Address: IBM Corp., 455 Park Place, Lexington, KY 40511
"Randy M.
Roberts"
<rsqrd@xxxxxxxx> To
Sent by: ptp-dev <ptp-dev@xxxxxxxxxxx>
ptp-dev-bounces@e cc
clipse.org
Subject
Re: [ptp-dev] A couple PTP
05/29/2007 12:08 questions
PM
Please respond to
Parallel Tools
Platform general
developers
<ptp-dev@eclipse.
org>
Dave,
The createControl() being called three times is on my end.
It may be unavoidable, but I'll look into it.
About canSave vs. isValid, I just wanted you to be aware.
It is not very clear in the articles and documentation about
how they would differ in their implementations.
Regards,
Randy
On Tue, 2007-05-29 at 09:11 -0400, Dave Wootton wrote:
> Randy,
>
> I'm working on implementing a class derived from
> AbstractRMLaunchConfigurationDynamicTab and noticed while running with
the
> debugger that the createControl() method is getting called three times
> before the parallel tab appears. My class seems to be working correctly,
> but I'm worried that this could be a performance problem on a loaded
> machine. Could I be doing something wrong that is causing createControl
to
> be called several times?
>
> Also, I looked at the notes in IRMLaunchConfigurationDynamicTab about
> canSave and isValid. I understand the notes, but am curious about if I
> need to worry about the distinction. My thoughts are that I would not
want
> to save a launch configuration unless all fields are valid, and I also
> would not want to launch an application unless all fields were valid, so
> both could call the same validation logic. The only reason I can see why
I
> might need to distinguish is that I need to ensure that if the user
enters
> some fields in the parallel tab, where there may be invalid values,
> switches to another tab such as arguments, then comes back to parallel
tab
> to fill in the rest of the fields, that the first fields the user entered
> into the parallel tab have not been reset. If that is the reason for the
> distinction, then when would I not want to save settings as part of
> canSave processing?
>
> Thanks
> Dave
> _______________________________________________
> ptp-dev mailing list
> ptp-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/ptp-dev
_______________________________________________
ptp-dev mailing list
ptp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ptp-dev
