You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a file is loading with a given wildcard, e.g. DLOAD "MYGA*", it shows the message with the wildcard LOADING 0:MYGA*
It would be nice, if it would displays the full name of the loading file e.g. LOADING 0:MYGAME
So I know which real file is loaded afterwards.
This request also applies to other DOS commands (e.g. DVERIFY,DELETE...)
The text was updated successfully, but these errors were encountered:
It's a nice idea but it'll be challenging to implement. The wildcard path goes to the disk device, and the disk device doesn't return the matched filename when performing the load. The DLOAD command would have to load a full directory listing and do its own wildcard pattern matching on the data that comes back. My hunch is it won't be worth the code space or the added disk activity.
... Implementing a non-DOS directory wildcard matcher would be useful for this issue: #152 Still not sure we should load the directory before every DLOAD just for this, but that's something at least. :)
I'm going to resolve this as infeasible. We aren't able to change Commodore DOS at a low enough level to make this work efficiently, and doing this within Commodore DOS's existing feature set (loading the directory every time it loads a file) would add far too much delay to disk operations.
When a file is loading with a given wildcard, e.g. DLOAD "MYGA*", it shows the message with the wildcard LOADING 0:MYGA*
It would be nice, if it would displays the full name of the loading file e.g. LOADING 0:MYGAME
So I know which real file is loaded afterwards.
This request also applies to other DOS commands (e.g. DVERIFY,DELETE...)
The text was updated successfully, but these errors were encountered: