Ticket #356 (Fixed)Thu Sep 12 09:48:42 UTC 2013
Enhancement to Configuration->Boot->Add to Apps, Look at and Run.
Reported by: | Chris Gransden (337) | Severity: | Enhancement |
Part: | RISC OS: Boot sequence | Release: | |
Milestone: | New features for RISC OS 5 | Status | Fixed |
Details by Chris Gransden (337):
In Configuration->Boot->‘Add to Apps’, ‘Look at’ and ‘Run’ if the path is longer than the width of the pane its not possible to see what the entry is.
Maybe add a horizontal scroll bar to the pane so it’s possible to see the full path.
Also the pane itself is movable so if you have !MoveWind installed the pane can be move around within the parent window.
When an entry is added to ‘Add to Apps’, ‘Look at’ and ‘Run’ if the path is on the !Boot drive instead of using an abosolute path e.g. SDFS::HardDisc0.$.!ProgName automatically change it to Boot:^.!Progname.
Also if the entry is deleted off the filesystem or the !Boot drive is renameed there is no validation of existing entries when ‘Set’ is clicked. Maybe highlight the invalid entries in red or pop up an error dialogue.
This should help reduce !Boot failures if the !Boot drive is changed/renamed or entries are deleted off the filesystem.
Changelog:
Modified by Sprow (202) Sat, April 05 2014 - 21:15:30 GMT
- Status changed from Open to Fixed
Version 0.11 onwards (21-Nov-2012) allow the window to be resized to accommodate path names longer than the pane default width.
Version 0.13 (05-Apr-2014) marks the pane as unmoveable so !MoveWind can’t move it.
Re: absolute paths, this is already handled if you inspect the output obey files the lines are relative to Boot but when shown in the pane they are re-expanded to the full path – hence this feature is already present.
Lastly, when an entry is found which doesn’t exist, it is faded in grey, which covers the last situation. As all the output lines are prefixed with “IfThere” they wont affect boot completion even if the drive no longer exists (or the item was moved/renamed).