| Age | Commit message (Collapse) | Author |
|---|
|
starting on 10.7+.
|
|
hotkeys.
|
|
|
|
missing
|
|
|
|
|
|
NSNotificationCenter::postNotificationName can't be const in certain versions of OSX
|
|
|
|
string.
|
|
|
|
|
|
|
|
handling.
|
|
focus.
|
|
|
|
position.
|
|
caret position.
|
|
the input focus changes.
|
|
directly without a trip through the window messaging system.
|
|
(global) focus so it can abort any current input composition.
|
|
non-Unicode build.
|
|
strings into UTF-8 for non-Unicode builds. And don't crap out on DBCS code pages either.
|
|
correctly.
|
|
keyboard handler.
|
|
edit box has the input focus.
|
|
(Based on patch by leecbaker)
|
|
|
|
(Matthieu)
|
|
|
|
during dragging. (Matthieu)
|
|
near the window borders. (Matthieu)
|
|
be compiled with older SDK versions.
|
|
|
|
switching to fullscreen on 10.7+. (Based on patch by Maedhros)
|
|
threads could crash OpenTTD
|
|
gets mouse focus while going to full screen, so manually force the mouse-is-in-window state
|
|
fullscreen toggle
|
|
set due to referencing a deleted mutex
|
|
palette was requested.
- Previously, the code would query the SDL_HWPALETTE flag, which doesn't always match the requested value.
- This would cause SDL to be restarted on every window resize event, effectively breaking resizing.
|
|
|
|
always requesting SDL_HWPALETTE, it is now only done for 8bp blitters in fullscreen mode.
- This fixes 32bpp blitters on 8bpp X11, which would only render garbage with SDL_HWPALETTE.
- This prevents the colors of other applications from being messed up when running a 8bpp blitter on a 8bpp system.
- When running a 8bpp blitter on an 8bpp system without SDL_HWPALETTE (e.g., in windowed mode), this uses a new shadow surface with color approximation.
- The use of a hardware palette can be forced on and off using -v sdl:hw_palette=1 or -v sdl:hw_palette=0
|
|
methods instead of static functions.
|
|
Eagle_rainbow)
|
|
|
|
|
|
unsupported fullscreen display mode (like 8 bpp modes in Windows 8).
|
|
|
|
|
|
resolution you were, not to the fullscreen resolution (Windows only)
|
|
(fullscreen, 8bpp/32bpp), and a window already exists, it was forced out of maximize mode, and its resolution/position was reset, often causing unwanted side-effects. As a "bonus", a WC_SIZE was triggered, and if the system was going from 8bpp to 32pp, this caused a forced window update in a limbo-state of the blitter (not fully 32bpp just yet, but for sure no longer 8bpp); this could cause random memory access which could lead to ACCESS_VIOLATIONS
|
