Ticket #167 (Fixed)Fri Feb 29 15:29:08 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: | RISC OS ROM build complete | 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:
<pre>
<code>
>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
</code>
</pre>
But if you set up a prefix it ruins the operation:
<pre>
<code>
>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
</code>
</pre>
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 Steve Revill (20) Fri, October 24 2008 - 12:29:45 GMT
- Milestone changed from Unspecified to RISC OS ROM build complete
Modified by Sprow (202) Sat, September 17 2011 - 21:27:33 GMT
- Status changed from Open to Fixed
Fixed in 1.69.