Skip to content

Fix custom mapping drive container - #674

Open
Xnick417x wants to merge 3 commits into
WinNative-Emu:mainfrom
Xnick417x:drive-container
Open

Fix custom mapping drive container#674
Xnick417x wants to merge 3 commits into
WinNative-Emu:mainfrom
Xnick417x:drive-container

Conversation

@Xnick417x

Copy link
Copy Markdown
Collaborator

No description provided.

dosdevices is now the source of truth for drive mappings. The boot rebuild no
longer deletes every drive letter before recreating them from the container
config, and bind paths are derived from the prefix, so a drive added in winecfg
is exposed to the guest instead of being dropped. The container config seeds
only a prefix that has no drives yet, which keeps defaults working on a fresh
container and restores them if the prefix is ever rebuilt.
Tapping the current-path card opens a text input prefilled with the current
directory, focused with the keyboard shown. A directory navigates there, a file
path opens its parent with the file selected, anything else reports that the
path was not found. The card is registered as a pane-nav item so it is reachable
without touch.
The path input was only wrapped in the overlay registry, so d-pad keys still
resolved to the grid registry and moved the directory selection behind it,
leaving OK and Cancel unreachable. Its visibility now feeds the registry
selector, the Start guard, the dismiss chain and the overlay reset. Start
confirms the typed path instead of acting on the picker underneath, sharing one
apply path with the OK button.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant