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
Originally posted by giantclambake April 30, 2024
Assume default path for ROMs is cwd/kickstarts
User copies Amiga roms to this location ~ after clicking on Rescan Paths, the dropdown selector shows all recognized ROMs.
However, if the ROM copied here is not recognized (ie; Coffin.rom) the '...' widget must be used to select unknown ROM.
When you do that, the file selector opens in the parent directory of cwd instead of cwd/kickstarts
A similar situation exists for Extended ROM File: (ie; aros-ext.bin) ...it does not appear in the dropdown selector, so the'...' widget must be used to select this ROM and the file selector opens in the parent directory of cwd instead of cwd/kickstarts
I'm not sure if this is intentional, or if the '...' widget should open file selector in cwd/kickstarts ?
TIA
The text was updated successfully, but these errors were encountered:
Discussed in #1300
Originally posted by giantclambake April 30, 2024
Assume default path for ROMs is
cwd/kickstarts
User copies Amiga roms to this location ~ after clicking on
Rescan Paths
, the dropdown selector shows all recognized ROMs.However, if the ROM copied here is not recognized (ie; Coffin.rom) the
'...'
widget must be used to select unknown ROM.When you do that, the file selector opens in the parent directory of cwd instead of
cwd/kickstarts
A similar situation exists for
Extended ROM File:
(ie; aros-ext.bin) ...it does not appear in the dropdown selector, so the'...'
widget must be used to select this ROM and the file selector opens in the parent directory of cwd instead ofcwd/kickstarts
I'm not sure if this is intentional, or if the
'...'
widget should open file selector incwd/kickstarts
?TIA
The text was updated successfully, but these errors were encountered: