Ticket #166 (Fixed)Mon Feb 25 13:18:34 UTC 2008
DDEUtils breaks OS_FSControl 37 (Canonicalise path) when <Prefix$Dir> is set.
| Reported by: | James Lampard (51) | Severity: | Normal |
| Part: | RISC OS: Module | Release: | |
| Milestone: | Status | Fixed |
Details by James Lampard (51):
On DDEUtils 1.66 (03 Nov 2003) (and previous versions):
If you have a file called “ADFS::HardDisc4.$.Develop.Projects.Resurgam.WebSite.APPINFO”
And execute the following code, you get the expected path:
>SYS “OS_FSControl”,37,“APPINFO”,STRING$(255,“*”),0,“ADFS::HardDisc4.$.Develop.Projects.Resurgam.WebSite.”,255 TO ,,path$
>P. path$
ADFS::HardDisc4.$.Develop.Projects.Resurgam.WebSite.APPINFO
But if you set up a prefix it ruins the operation:
>prefix ADFS::HardDisc4.$.Develop
>SYS “OS_FSControl”,37,“APPINFO”,STRING$(255,"“),0,”ADFS::HardDisc4.$.Develop.P
rojects.Resurgam.WebSite.",255 TO ,,path$
>P. path$
ADFS::HardDisc4.$.Develop.APPINFO
I think if the path in r1 doesn’t start with a root element DDEUtils just sticks <Prefix$Dir> onto the front of it. As it’s now a complete path it can’t match with the paths specified via r3 and r4.
This bug is fixed in DDEUtils 1.75 supplied with RO6
Changelog:
Modified by James Lampard (51) Mon, February 25 2008 - 13:19:48 GMT
Okay how can I edit my ticket?
Modified by Steve Revill (20) Tue, February 26 2008 - 12:18:10 GMT
Click on the “Comment on, or change status of, this ticket” link just below the ticket…
Modified by James Lampard (51) Tue, February 26 2008 - 12:33:05 GMT
Yes, I did that to add the initial comment…
I don’t see any way to change the original ticket.
Modified by Andrew Hodgkinson (6) Tue, February 26 2008 - 15:01:26 GMT
You can’t edit submissions to the tracker. It encourages accuracy :-) and prevents accidental or deliberate revisions of history.
For help with Textile, noting that it’s a bit quirky in the bug tracker, see this related fault (Ticket #164):
http://www.riscosopen.org/tracker/tickets/show/164Modified by Andrew Hodgkinson (6) Tue, February 26 2008 - 15:02:46 GMT
Oh, by the way, judging from the above, I’m guessing that the simple way to paste code blocks is to just make sure each line is indented by a couple of spaces:
this tests some difficult <file$characters> C/C++ and any C/C++…I think that’ll work.
Modified by Andrew Hodgkinson (6) Tue, February 26 2008 - 15:03:12 GMT
OK, so no, it’s just bust :-D
Much work to do on the bug tracker comment engine, it seems.
Modified by James Lampard (51) Fri, February 29 2008 - 15:27:09 GMT
- Status changed from Open to Fixed
I’ve got a cunning plan to fix the formatting:
I’m going to close this ticket & open another.
Modified by James Lampard (51) Fri, February 29 2008 - 15:35:44 GMT
Well that didn’t work.
