On Mon, Jun 30, 2008 at 7:38 AM, Rick McGuire <[EMAIL PROTECTED]> wrote:
> PUBLIC_ROUTINES was that hack that oodialog was using that I
> eliminated. I also updated this test for the new classes that have
> been added.
>
> The monitor test failure was the same as the lines() problem, which
> should be fixed now.
I saw your commits. We should now have everything passing. I'll test
some a little later this morning.
The sample ooDialog test group now passes / ooDialog is working. This
one test can be dependent on what else is going on with the system.
Since the purpose of the test is to show that the sample works, I
think that is acceptable. (If the system is heavily loaded, the
windows some times open too slow.)
The Clipboard test case that failed did a clipboard copy immediately
followed by a clipboard paste.
cb1~copy("Some text")
text = cb2~paste
Sometimes text would be the empty string. I think that was just
timing. If you query the clipboard to see if it has data after the
copy, then do the paste, it works every time. Normally you would
query the clipboard to see if it has data before doing a paste anyway.
So, I updated the test case to do that and it now always passes.
All of the tests should now pass. You can take a breather, or move on
to your next task. <grin>
--
Mark Miesfeld
-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
