Suggestion: Patch Directory...

I see that there are already a few patches for D5.1 floating around.  I
wonder if OA might consider making a patch directory page with brief
explanations, dates and links to all the patches in one place.  I don't feel
that I want to wait for the next patch level, but I would like to wait a few
weeks to see if the guinea pigs survive the patches. ;)  The problem then is
that I forget what the patches were, and have to sort through messages to
find the latest urls.  It would be cool to have a page with current known
issues, and patches.

Chris

Chris

You wrote in message news:bb3e8n$5f2vf$[hidden email]...
>...
> I see that there are already a few patches for D5.1 floating around.  I
> wonder if OA might consider making a patch directory page with brief
> explanations, dates and links to all the patches in one place.  I don't
feel
> that I want to wait for the next patch level, but I would like to wait a
few
> weeks to see if the guinea pigs survive the patches. ;)  The problem then
is
> that I forget what the patches were, and have to sort through messages to
> find the latest urls.  It would be cool to have a page with current known
> issues, and patches.

This is a good suggestion, and something I'd like to do. However the
overhead of doing this maintaining this manually would be to great, so it
would have to be a automatically generated. Since this will involve
programming it is very likely that patch level 1 for 5.1 will be out before
then.

In the meantime you can find the current patches in
http://www.object-arts.com/Lib/Update/Dolphin/5.1/

Refer to
http://www.object-arts.com/Lib/Update/Dolphin/5.1/51PL1List.htm for a list
of the bug fixes and enhancements, or
http://www.object-arts.com/Lib/Update/Dolphin/5.1/51PL1Detail.htm if you
want all the detail.

You can use the issue number in the bug list to construct the URL of the
relevant patch file as follows:

http://www.object-arts.com/Lib/Update/Dolphin/5.1/NNNN.st

Where NNNN is the issue number. Alternatively you can download the complete
current patches:

DPRO: http://www.object-arts.com/Lib/Update/Dolphin/5.1/PL1PRO.st
DSE: http://www.object-arts.com/Lib/Update/Dolphin/5.1/PL1DSE.st
DVE: http://www.object-arts.com/Lib/Update/Dolphin/5.1/PL1DVE.st

Please note that all patches should be considered experimental until they
are released via LiveUpdate. I'm fairly confident with those there at the
moment, but they are still undergoing testing.

Regards

Blair

Blair,

As an alternative to a listing, you might just put up a web page with the
links and instructions in this post; that would probably give us ready
access to what we really need.

Spawned question: did 5.1 as initially released have any problems with
getting to background processes on win2k?  If so, we might have an
explanation for my problems with it.

Have a good one,

Bill

--
Wilhelm K. Schwab, Ph.D.
[hidden email]

"Blair McGlashan" <[hidden email]> wrote in message
news:bb74gg$6gsv9$[hidden email]...
> You wrote in message news:bb3e8n$5f2vf$[hidden email]...
> >...
> > I see that there are already a few patches for D5.1 floating around.  I
> > wonder if OA might consider making a patch directory page with brief
> > explanations, dates and links to all the patches in one place.  I don't
....
> This is a good suggestion, and something I'd like to do. However the
> overhead of doing this maintaining this manually would be to great, so it
> would have to be a automatically generated. Since this will involve
> programming it is very likely that patch level 1 for 5.1 will be out
before
> then.
...

Thank you very much!  This is exactly what I was looking for.  I have
already learned about some new issues that I may need to be aware of.
As always, great job,
Chris

"Bill Schwab" <[hidden email]> wrote in message
news:bb84vq$66r3c$[hidden email]...
>... did 5.1 as initially released have any problems with
> getting to background processes on win2k?  If so, we might have an
> explanation for my problems with it.

Not that we are aware of: We managed to reproduce the idle time UI
validation issue on Win98 (and noted that it was immediately corrected by
filing in the 1272.st patch), but did not experience any such problem over a
considerable period on WinXP (really a cosmetically improved Win2k), and
neither were we able to reproduce this issue on Win2k, nor have we had any
reports of it occurring there. In fact the issue appears to be caused by a
bug in Windows 98's of GetQueueStatus(), for which 1272.st is a workaround.

The related issue of delayed message box opening (caused by unecessarily
repeated idle time UI validation competing with the overlapped message box
thread) might potentially impact any application using overlapped calls for
background tasks.

Regards

Blair