Corel Paradox 8 Service Pack 1
Paul O'Hagan
Thank you for your patience,
Corel Corporation is pleased to announce the release of Service Pack 1
for Corel Pardox 8. This update deals with many known issues in Paradox
8, and will update your Paradox to version 8.00.302.
It can be found immediately at:
ftp://ftp1.corel.com/pub/Paradox/paradox8/
It will also be made available at:
http://www.corel.com/support/ftpsite/pub/paradox/paradox8/index.htm
By the end of the day today.
Regards,
Corel Paradox Team
Corel Corporation
Mike Irwin
Only one complaint so far, Paul ... I'm downloading it at the same time as
I'm answering mail here, so the replies are going out very sloooooowly !
It was great meeting you guys; now you'll never get rid of us !
Have fun
Mike Irwin
Graeme MacKeachie
Thanks for the notification. I *really* hope it's been better tested than
the various builds of SP3 for WP8...
Any word, please, on what the patch is intended to address?
Graeme MacKeachie
Sydney, Australia
Graeme MacKeachie
Any word, please, on what the patch is intended to address?
so...@spamlesssoleassociates.com
Graeme MacKeachie <br...@rainbow.net.au> wrote:
»Thanks for the notification. I *really* hope it's been better tested than
»the various builds of SP3 for WP8...
»
»Any word, please, on what the patch is intended to address?
»
Howdy,
Prior to the installation launch of the patch a list appears.
--
-Kenneth
If you email please remove the "SPAMLESS."
peggy baker
not to be greedy, but is this patch applicable for Runtime as well?
peggy baker
Mike Irwin
Not as far as I know, but there were hints that things like the lookups not
working in Pdx8 Runtime in NT was a severe embarassment, so I'd not be too
surprised. However, Paul and people aren't allowed to tell you/us anything
unless explicitly given permission to (otherwise _some_ people get it into
their heads that it's a promise and then, if it's not delivered on, sue the
company !).
Mike
Victor Sokovin
Paul O'Hagan wrote:
>
> Thank you for your patience,
>
> Corel Corporation is pleased to announce the release of Service Pack 1
> for Corel Pardox 8. This update deals with many known issues in Paradox
> 8, and will update your Paradox to version 8.00.302.
>
Just installed the patch file but one of the most irritating problems
with Paradox 8 has not been solved. I mean the following problem with
reports designed under Paradox 7: 'word wrap' property in text fields
doesn't work properly. Some values get invisible if the property is
checked. I posted the problem to newsgroups and mailing lists but
never got a solution. Am I missing something? Redesigning all old
reports doesn't seem a good idea to me.
Losing patience :-),
Victor
vlad
It never worked properly in Pdox for Windows. Try writing something in
Delphi or C++ where you can calculate character position.
Victor Sokovin
vlad wrote:
>
> It never worked properly in Pdox for Windows. Try writing something in
> Delphi or C++ where you can calculate character position.
Vlad, I never had this problem with P7. It only bothers me when I
redesign
my old reports in P8. Well, actually this is one of the reasons why I
don't upgrade to P8. Not seeing text values on the screen while
designing a
report is really irritating. I forgot to mention that reports print
well, so
that's "only" a screen problem. Most applications seem to send reports
directly to the printer. I guess that's why we don't hear too much about
this
bug. Still annoying to developers...
Victor
Stefan Bodingh
Agree, the problem is in Runtime also.
Reports that are created in Paradox 7 look empty in P8 preview mode,
but prints OK. You have to uncheck word wrap property of each field. For
some reason when a field is shorter in the report then the actual size
of the field and word wrap is checked then the contents of the field is
invisible when the report is in preview mode. If you create the report
in Paradox 8 this does not happen.
--
______________________________________________________________________
: Stefan Bodingh - Paradox and Delphi Consulting
: Located in Haninge Sweden
: URL: http://home2.swipnet.se/~w-27915/
: Tel +46 8 745 46 10 (mailto:stefan....@swipnet.se)
______________________________________________________________________
Victor Sokovin
Stefan Bodingh wrote:
>
> Agree, the problem is in Runtime also.
> Reports that are created in Paradox 7 look empty in P8 preview mode,
> but prints OK. You have to uncheck word wrap property of each field. For
> some reason when a field is shorter in the report then the actual size
> of the field and word wrap is checked then the contents of the field is
> invisible when the report is in preview mode. If you create the report
> in Paradox 8 this does not happen.
>
What bothers me is why the developers of P8 don't notice this. They
never (re)design reports and don't read newsgroups? :-)
Cheers,
Victor
Mike Irwin
Victor,
FYI, this problem was raised by CTech in our recent meeting with Corel
Development (amongst others). The answer was that version 7's reports were
something of a kludge in order to make them work at all, and, as a result, you
saw the memory problems. Corel believes that it has fixed the reports in many
ways, including the memory problems. However, the text disappearance is
something that one will just have to live with, as making it work would
apparently be a major alteration to what is now clean code; essentially, the
bringing back of what they don't want in the code ! The result of v7 has been
to create, in effect, slightly "incompatible" reports. For the most part, they
work fine in v8 (to wit, they print fine, which is the main thing), but the
incompatibility will have to persist :(
Personally, I'd prefer to live with this little bug than lose memory whenever
I print !
Hope this helps
Mike
David Ehle
Mike,
It does not appear that you have any official connection with Corel, but
I hope that they notice this response. You have given _exactly_ the
type of information that Corel has previously refused to give and that I
believe people are craving- a little explanation of why we have a bug.
We've all written bad code or had to kludge something that we regretted
after the fact- and could understand the choice that Corel had to make
if they would simply shed a little light on the reasons behind a
decision. Re-writing bad code so that you don't loose backward
compatibility can be more difficult, in the end, than doing it right the
first time.
If you are associated with Corel, then I hope they promote you for your
fine customer-focused approach ;)
David Ehle
Stefan Bodingh
Mike,
When I write incompatible code, I also write a converter program for my
old customers..
Mike Irwin wrote:
>
> Victor,
>
> FYI, this problem was raised by CTech in our recent meeting with Corel
> Development (amongst others). The answer was that version 7's reports were
> something of a kludge in order to make them work at all, and, as a result, you
> saw the memory problems. Corel believes that it has fixed the reports in many
> ways, including the memory problems. However, the text disappearance is
> something that one will just have to live with, as making it work would
> apparently be a major alteration to what is now clean code; essentially, the
> bringing back of what they don't want in the code ! The result of v7 has been
> to create, in effect, slightly "incompatible" reports. For the most part, they
> work fine in v8 (to wit, they print fine, which is the main thing), but the
> incompatibility will have to persist :(
>
> Personally, I'd prefer to live with this little bug than lose memory whenever
> I print !
>
> Hope this helps
>
> Mike
Mike Irwin
My only connection with Corel is the fact that I am a member of their CTech
volunteer support group, which means that you get the benefit of what experience I
can bring to bear on your problems free, gratis, and for nothing ! I would be very
surprised that any company would be happy allowing its employees to criticise each
other; the members of CTech occupy a rather special position, in that we are able to
represent you, the users, from our own daily experience, but are also, at times,
able to explain what Corel is doing in a more comprehensible way than is permitted
in CorpSpeak.
Please don't fear that we'll hesitate to (quietly, offline) flame anyone that
deserves it; each other too, at times !
Hopefully my attempt at explaining some of the reasons behind this apparent bug will
not bring the Wrath of Mike down upon my head (no fear of the Wrath of Khan anymore
!), and, equally, it won't spur you all into taking up arms for yet more patches.
Have fun
Mike
David Ehle wrote:
> Mike,
>
> It does not appear that you have any official connection with Corel, but
> I hope that they notice this response. You have given _exactly_ the
> type of information that Corel has previously refused to give and that I
> believe people are craving- a little explanation of why we have a bug.
> We've all written bad code or had to kludge something that we regretted
> after the fact- and could understand the choice that Corel had to make
> if they would simply shed a little light on the reasons behind a
> decision. Re-writing bad code so that you don't loose backward
> compatibility can be more difficult, in the end, than doing it right the
> first time.
>
> If you are associated with Corel, then I hope they promote you for your
> fine customer-focused approach ;)
>
> David Ehle
>
> Mike Irwin wrote:
> >
> > Victor,
> >
> > FYI, this problem was raised by CTech in our recent meeting with Corel
> > Development (amongst others). The answer was that version 7's reports were
> > something of a kludge in order to make them work at all, and, as a result, you
> > saw the memory problems. Corel believes that it has fixed the reports in many
> > ways, including the memory problems. However, the text disappearance is
> > something that one will just have to live with, as making it work would
> > apparently be a major alteration to what is now clean code; essentially, the
> > bringing back of what they don't want in the code ! The result of v7 has been
> > to create, in effect, slightly "incompatible" reports. For the most part, they
> > work fine in v8 (to wit, they print fine, which is the main thing), but the
> > incompatibility will have to persist :(
> >
> > Personally, I'd prefer to live with this little bug than lose memory whenever
> > I print !
> >
> > Hope this helps
> >
> > Mike
> >
Mike Irwin
It's nice to live in a perfect world, too. However, I believe that Corel's staff
have taken the correct path by striving to "get it right" rather than "get it done".
Paradox/Win has traditionally suffered from the latter.
Mike
Stefan Bodingh wrote:
> Mike,
>
> When I write incompatible code, I also write a converter program for my
> old customers..
>
> Mike Irwin wrote:
> >
> > Victor,
> >
> > FYI, this problem was raised by CTech in our recent meeting with Corel
> > Development (amongst others). The answer was that version 7's reports were
> > something of a kludge in order to make them work at all, and, as a result, you
> > saw the memory problems. Corel believes that it has fixed the reports in many
> > ways, including the memory problems. However, the text disappearance is
> > something that one will just have to live with, as making it work would
> > apparently be a major alteration to what is now clean code; essentially, the
> > bringing back of what they don't want in the code ! The result of v7 has been
> > to create, in effect, slightly "incompatible" reports. For the most part, they
> > work fine in v8 (to wit, they print fine, which is the main thing), but the
> > incompatibility will have to persist :(
> >
> > Personally, I'd prefer to live with this little bug than lose memory whenever
> > I print !
> >
> > Hope this helps
> >
> > Mike
>
Alexander Philippou
Paul O'Hagan <paradox...@corel.com> wrote in article
<352557C2...@corel.com>...
> Corel Corporation is pleased to announce the release of Service Pack 1
Since installing the long awaited patch, dialog boxes CANNOT be minimized
via OPAL's minimize() method. Try the attached form.
(Food for thought: is this sloppy programming or an absence of QA???)
Alexander Philippou
al...@noemon.com
Alexander Philippou
How can we find out via OPAL if our users have installed the patch or not?
- resourceInfo["InternalVersion"] still returns "6.107", as it did in
version 8 without the patch.
- version() still returns "8.00", as it did in version 8 without the patch.
Shouldn't you have upgraded the version number to a higher value (say,
"8.01"), or returned the full legth of the version string ("8.00.302"
instead of "8.00")?
Alexander Philippou
al...@noemon.com
Alexander Philippou
Thanks for addressing the issues fixed in The Patch. However, there are
many more long-known issues still pending to be fixed.
Examples:
- Incorrectly displaying user-defined bitmaps in custom toolbars.
- The numerous problems with fonts and setting their attributes.
- Losing the formatting of memos during interactive copy/paste operations.
- Garbage appearing at the end of memos after pasting text in them.
- Forms that cannot be be resized under a minimum width when the expanded
ruler setting is checked.
- Losing the mouse point after SetMouseShape.
- Crashes after redocking toolbars.
More examples:
- Methods getting lost while editing FSLs.
- GPVs with paths over 128 chars long.
- GPVs when compiling forms.
- Losing the current selection of a list field when opening form.
- Closed Object Explorer momentarily flashing on and off when opening
forms, including FDLs.
- SetPosition not working properly on an edit area when it has focus.
- Weird compilation bugs.
Some of these issues had been logged and acknowledged even during v8's beta
period (early last summer). And there are even more reported issues (all
well documented with forms that consistently reproduce them), most of which
need *little* programming effort to fix.
When is Service Release 2 going to be made available with the rest of the
fixes?
Alexander Philippou
al...@noemon.com