Open Torinde opened 2 years ago
Emulate CD drive front panel buttons (play/stop/prev/next) dosbox-staging/dosbox-staging/issues/609
Merging/splitting host joystick axes into one/two DOSbox devices. Not sure if the following is an issue, mentioning it in case relevant when doing "soft joystick": dosbox-staging/dosbox-staging/issues/342
DOSbox Core On-screen virtual keyboard. Ported over by sonninnos from the UAE and VICE cores.
I love the idea of LED lights on-screen in full-screen mode. HDD and FDD and so on. I like the FDD and HDD sounds too, but that might be a hard sell.
I remember in those old Telarium/Trillium games you could tell a monster was coming by the disk drive loading up the graphic data. I'd hear the disk noise and wait for the picture. This anticipating what's coming aspect is missing in emulation.
Host Mouse to Guest Gamepad in QEMU USB Gamepad
That is quite a laundry list of ideas π It will surely keep us busy for the next 5 years at least! π
I'm not against some of these, but the end result should be still sleek and aesthetic. I don't want the OSD to look like a Christmas tree π Probably we can try introducing a subset of these gradually, judiciously weighing up the relative importance of the added benefits vs the extra clutter, usage of screen space, and added maintenance effort for each feature.
Also, my philosophy is that feature bloat is not desirable; anyone can add all the features... Adding only the right set of well-chosen features that work nicely together and don't overload the user unnecessarily, that's an art.
See the main discussion & plans about the OSD feature here: https://github.com/dosbox-staging/dosbox-staging/discussions/1953
Agree with gradual approach. Agree my mockup isn't pretty - I just try to illustrate some of the ideas. Because tastes/requirements differ (especially those related to how much space your monitor has on the sides) - I think item 19 is crucial: "customization ability"... which also solves the danger of becoming a "Christmas tree", e.g. user can simply disable (actually "not enable" since by default I expect most to be off) whatever he feels is superfluous?
Agree with gradual approach. Agree my mockup isn't pretty - I just try to illustrate some of the ideas. Because tastes/requirements differ (especially those related to how much space your monitor has on the sides) - I think item 19 is crucial: "customization ability"... which also solves the danger of becoming a "Christmas tree", e.g. user can simply disable (actually "not enable" since by default I expect most to be off) whatever he feels is superfluous?
Definitely, agree on all those: start small, introduce things gradually, and make things customisable (within reasonable limits) ππ»
I think emulating the HDD and FDD LEDs would be fine to just have a Red and Green dot in the lower corner that completely disappears when there's no activity. No label at all, just a colored mark.
I'm less interested in the caps lock and scroll lock indicators, but I think they'd be best to only show when there's a status change. Just appear for 2 seconds after pressing caps lock.
I know it sounds nerdy, but I'm also really interested in the drive sounds. I wouldn't care if it's that accurate myself, just a rumble sound through the PC speaker while the data is loading to let me know those monster images are loading.
I think having an area in the side border for LEDs would be great. Floppy and HDD lights too.
Similar problem. Linux desktop host numlock and dosbox-x emu numlock out of sync. A bit tiring to press numlock every time when switching back and forth. CONFIG.SYS settings do nothing.
Probably needs the use of platform-specific APIs to determine and change the current NumLock, CapLock and ScrollLock states, e.g. https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-getkeystate?redirectedfrom=MSDN
Is your feature request related to a problem? Please describe.
Can't type certain keys/combinations
PrtScr
,Pause/Break
,F11
, ... #3628, #3231 Don't see status Numlock, Capslock, etc. Don't have indicator on activityWhat you want
Please let me know if such requests are better to be split in separate issues.
Mockup:
Describe alternatives you've considered
No response
Additional information
No response
Have you checked that no similar feature request(s) exist?
Code of Conduct & Contributing Guidelines