- March 2021
- February 2021
- October 2020
- June 2020
- May 2020
- October 2019
- June 2019
- September 2018
- May 2018
- December 2017
- April 2017
- June 2016
- February 2016
- November 2015
- January 2015
- August 2014
- July 2014
- May 2014
- March 2014
- February 2014
- January 2014
- November 2013
- August 2013
- June 2013
- May 2013
- April 2013
- March 2013
- February 2013
- December 2012
- November 2012
- September 2012
- June 2012
- April 2012
- March 2012
- February 2012
- January 2012
- December 2011
- November 2011
- September 2011
- July 2011
- June 2011
- May 2011
- March 2011
- January 2011
- October 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- September 2009
- July 2009
- June 2009
- May 2009
- March 2009
- September 2008
- April 2008
- December 2007
- June 2007
- June 2005
- September 2004
- May 2002
- October 2001
- August 2001
2009-06-01: DOSBox GUI update
A status update on the DOSBox GUI project that I've adopted. The changes are small, but numerous.
The following should be fixed now:
- after using the keymapper, activated from the UI, the alt key is no longer stuck after closing the UI
- leaving the keymapper, activated from the UI, and then closing the UI no longer leaves window chrome unresponsive
- crash on S3 cards when leaving the keymapper, activated from the UI
- no cursor in full-screen mode
The first two bugs were actually caused by issues in the keymapper and its (de)activation. The third is an SDL issue caused by DirectDraw and the S3 driver. Full-screen mode may still be very flaky, but SDL's standard directdraw video mode simply ignores the mouse cursor leaving it up to the client to draw it.
New features and other changes:
- combobox selection where appropriate
- main configuration menu can be closed by pressing Escape
- message boxes with help text can be closed by pressing Enter or Escape
- fading in/out has been disabled
Known issues in this version that are on my list to fix:
- clicking outside a menu or combobox (or any popup window) inside the parent's client area, but not on any client controls does not dismiss the popup window
- crash when activating menu in full-screen mode when using OpenGL (observed on nvidia drivers -- exclusive mode cannot be set)
- performance may be very much sub par, possibly due to the way the screen is drawn
- some properties cannot be edited because they have compound values -- these controls will show as disabled (for example: sdl::priority, cpu::cycles)
- none of the "help" buttons show anything useful
- help windows may be too large for the screen or even if they fit, placed too low
- the "execute now" button in the autoexec editor leaves a spurious prompt
Comments
No comments, yet...
Post a comment