On Tue, Sep 25, 2012 at 9:01 AM, Staffan Tylen <staffan.ty...@gmail.com>wrote:
> Mark, thanks for the feedback. I've looked at your third option, the
> propSheet attribute, but I'm not sure I understand how I could use that for
> communication between two pages?
>
The property sheet dialog knows what pages are present and has a reference
to all the page objects. By communicating through the property sheet
dialog, the property page dialog does not need to know which specific page
object has the progress bars on it. In your description, the page with the
progress bars is page 2. But, if you add pages, maybe that becomes page 4.
You communicate to the property sheet dialog by adding methods to it. Your
page with the long running processor could report its progress to the the
property sheet dialog. And the property sheet dialog would decide what to
do with the report. In your scenario, it would probably signal the
property sheet page dialog with the progress bars.
>
> Yes, you are quite right, I'm trying to reuse code whenever I can but I
> haven't fully got into oo-thinking yet so my success rate is not optimal ;)
> Thanks for the hint on using a mixin class instead of a subclass, it hadn't
> come into my mind, it makes more sense.
>
My suggestion here is to write your program, and once you get the page
dialog with the progress bars working, then go back and abstract out the
methods in the page dialog that could be generic.
--
Mark Miesfeld
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
