Modify problem report

Andy/Blair

I don't think there's anyway to modify a problem report (?) so this seems
like the next best place ....

I reported a problem about literals not being displayed correctly (it hasn't
appeared yet so I don't know the number).  I've now realised that ...

a) The literal _should_ be an Association, so ignore that bit.
b) It only happens if the Association's value is a String containing nulls
i.e. one created with ...

String new: 128

It's still a (minor) problem though as it does break the disassembly
listing.

Ian

Ian,

The report is #1788. I have updated the description with the new
information.

BTW, one of the reasons the bug report form doesn't answer the number
of the report is that the numbers aren't allocated until later (after
the report has been reviewed).

--
Andy Bower
Dolphin Support
www.object-arts.com

Andy,

> The report is #1788. I have updated the description with the new
> information.

Just FYI.  1788 doesn't seem to appear in either the "fixed" or "to fix"
lists on the beta test support webpage, and I can't see the report under
another number?  Might there be a problem with the database?

--
Ian

Use the Reply-To address to contact me.
Mail sent to the From address is ignored.

Ian,

> > The report is #1788. I have updated the description with the new
> > information.
>
> Just FYI.  1788 doesn't seem to appear in either the "fixed" or "to
> fix" lists on the beta test support webpage, and I can't see the
> report under another number?  Might there be a problem with the
> database?

I think it is a problem with the database.  The report is still in
there and marked as "Closed", however, the filter that produces the
report seems to be ignoring the Closed status, hence the issue does not
appear in the fixed list as it should. The filter seems to correctly
pick up the "Closed (Fixed)" status, though.

I'm not sure what to do about it at this stage.  In the meantime, here
is Blair's comment as to why the issue was closed with no fix:

"#literalAt: is working correctly - its purpose is to return an entry
from the literal frame, not the literal representation of the object in
the literal frame. I have, however, raised a separate defect #1800 to
cover the bug with #disassembly."

Best regards,

--
Andy Bower
Dolphin Support
www.object-arts.com

Andy,

> I'm not sure what to do about it at this stage.

Thanks for looking.  Are you aware (or is it just me?) that neither of the
status pages are available at the moment - they both bring bring up a "page
not found" error.

> In the meantime, here
> is Blair's comment as to why the issue was closed with no fix:

Thanks for that as well.  When I reported the issue I wasn't really sure
where the problem lay so I'm not surprised I got it wrong :-)

Ian

> Thanks for looking.  Are you aware (or is it just me?) that neither of the
> status pages are available at the moment - they both bring bring up a
> "page not found" error.

It was "just me". Firefox had decided, in it's infinite wisdom, that I
shouldn't see those pages :-(  A complete clear of the Firefox cache sorted
out the problem.

I'll go back to sleep now.....

Ian