Age | Commit message (Collapse) | Author |
|
|
|
SDL: Default audio output rate to 44kHz.
|
|
|
|
Add trigger for Virtual Keyboard on long press of Middle Mouse Button
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Thanks to fuzzie for noticing this.
|
|
|
|
|
|
from Fedors changes.
|
|
Otherwise we can end up with the wrong resolution when we make
multiple resizes in quick succession.
|
|
|
|
This hopefully fixes input positions in retina devices. The idea is stolen
from QT: https://qt.gitorious.org/qt/qt/source/0726127285413829f58618b5b82fb3e2da0c3a74:src/plugins/platforms/uikit/quikitwindow.mm#L261-296
Complicated way to retrieve scale's return value properly is taken from:
https://stackoverflow.com/questions/3130464 We sadly can't use the cleaner
solution since we don't want to require a newer SDK...
|
|
|
|
|
|
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
However, due to the complexity of this code, directly calling the
virtual keyboard trigger event could have side effects, so have instead
just added the CTRL modifier to fix this.
This should be fixed if possible to use EVENT_VIRTUAL_KEYBOARD.
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
However, due to the complexity of this code, directly calling the
virtual keyboard trigger event could have side effects, so have instead
just added the CTRL modifier to fix this.
This should be fixed if possible to use EVENT_VIRTUAL_KEYBOARD.
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
Rather than just adding the CTRL modifier, this code changes the
backend to directly generate the virtual keyboard trigger event
directly. This avoids any future breakage if the key combination is
changed again.
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
Rather than just adding the CTRL modifier, this code changes the
backend to directly generate the virtual keyboard trigger event
directly. This avoids any future breakage if the key combination is
changed again.
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
Rather than just adding the CTRL modifier, this code changes the
backend to directly generate the virtual keyboard trigger event
directly. This avoids any future breakage if the key combination is
changed again.
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
Rather than just adding the CTRL modifier, this code changes the
backend to directly generate the virtual keyboard trigger event
directly. This avoids any future breakage if the key combination is
changed again.
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
Rather than just adding the CTRL modifier, this code changes the
backend to directly generate the virtual keyboard trigger event
directly. This avoids any future breakage if the key combination is
changed again.
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
Rather than just adding the CTRL modifier, this code changes the
backend to directly generate the virtual keyboard trigger event
directly. This avoids any future breakage if the key combination is
changed again.
|
|
As the virtual keyboard trigger has been moved to CTRL-F7, the previous
code which generates a unmodified F7 event to do this will not work.
Rather than just adding the CTRL modifier, this code changes the
backend to directly generate the virtual keyboard trigger event
directly. This avoids any future breakage if the key combination is
changed again.
|
|
PS2: Pull request to master for latest PS2 code
|
|
This pack contains just the 320x240 layout.
This is a quick way to achieve the result of a smaller keyboard
when running on 640x480 and larger games as requested bu a user.
To use this, the pack zip file, vkeybd_small.zip should be placed
in the extrapath in the same way as vkeybd_default.zip.
However, it is also necessary to set this as the active virtual
keyboard layout by adding the following linein the global [scummvm]
section of the configuration file i.e. scummvm.ini:
vkeybd_pack_name=vkeybd_small
This should be added to the GUI as a misc option, in future.
Currently, the closest layout size to the overlay size is chosen
automatically by the code in the method:
bool VirtualKeyboardParser::parserCallback_mode(ParserNode *node)
This should probably also be made configurable in future to allow
smaller keyboard sizes to be chosen.
|
|
|
|
ANDROID: Fix color key handling for 16bit mouse cursors.
|
|
Since the Android backend uses glBlendFunc(GL_ONE, GL_ONE_MINUS_SRC_ALPHA)
we need to make the transparent cursor pixels all 0 otherwise we might get
artifacts from blending.
|
|
This should fix a issue similarly to bug #6108:
"WII: Zak FM-TOWNS mouse cursor encased in blue box".
|
|
This should fix bug #6108 "WII: Zak FM-TOWNS mouse cursor encased in blue box".
|
|
|
|
|
|
If this is not present, it will use the default as previously.
|