summaryrefslogtreecommitdiff
path: root/src/video/win32_v.cpp
AgeCommit message (Collapse)Author
2019-04-10Codechange: Use null pointer literal instead of the NULL macroHenry Wilson
2019-04-06Codechange: C++11 STL has a function for getting the number of CPU cores.Michael Lutz
2019-04-06Codechange: Replace custom thread code with C++11 thread objects.Michael Lutz
We assume a conforming C++11 compiler environment that has a valid <thread>-header. Failure to run a real thread is handled gracefully.
2019-04-06Codechange: Replace custom mutex code with C++11 mutex'es.Michael Lutz
A conforming compiler with a valid <mutex>-header is expected. Most parts of the code assume that locking a mutex will never fail unexpectedly, which is generally true on all common platforms that don't just pretend to be C++11. The use of condition variables in driver code is checked.
2019-01-17Codechange: Remove unnecessarily defined functions under MinGWCharles Pigott
2019-01-17Fix: A few minor compile warnings under MinGWCharles Pigott
2018-07-19Feature: Framerate display window (#6822)Niels Martin Hansen
Frame rate and various game loop/graphics timing measurements and graphs. Accessible via the Help menu, and can print some stats in the console via the fps command.
2018-06-27Fix: [Win32] Garbage in OS window title if branch name was too long.Michael Lutz
This was caused by a missing \0-character on reaching the buffer limit.
2018-04-29Remove: WinCE supportPatric Stout
2018-04-10Codechange: [Win32] Use OS function for mouse tracking if present.Michael Lutz
2017-12-09(svn r27935) -Fix [FS#6629]: [Win32] Right mouse scrolling didn't work ↵michi_cc
properly with the Windows 10 Fall Creators Update.
2017-08-13(svn r27893) -Codechange: Use fallthrough attribute. (LordAro)frosch
2017-03-11(svn r27775) -Fix [FS#6510]: Insufficient thread synchronisation when ↵frosch
switching blitters. (JGR)
2016-10-30(svn r27673) -Add: [Win32] Thread names for windows debuggers.michi_cc
2015-02-22(svn r27167) -Fix: [SDL, Windows] Right-mouse-button scrolling ↵frosch
scrolled/jumped way to far, when OpenTTD lagged during mouse event processing.
2014-09-30(svn r26943) -Fix: [Win32] Silence a warning about comparison of signed and ↵planetmaker
unsigned variables when using gcc
2014-04-28(svn r26538) -Codechange: remove double accounting of the driversrubidium
2014-04-27(svn r26522) -Add: A config-file-only setting to disable usage of 8bpp video ↵frosch
modes. -Remove: [win32] fullscreen_bpp setting, which is replaced by above setting. -Change: Disable usage of 8bpp blitters and video modes by default. Many modern OS and hardware cause issues with those.
2014-04-23(svn r26482) -Codechange: add an include that allows us to undefine/redefine ↵rubidium
"unsafe" functions to prevent them from being used, and thus having to care about certain aspects of their return values
2014-02-23(svn r26367) -Fix: [Win32] Use a separate event to indicate that the drawing ↵michi_cc
thread has finished initialising, preventing potential deadlocks.
2014-02-23(svn r26366) -Fix: Protect the windows video driver from concurrent access ↵fonsinchen
(frosch123)
2014-02-23(svn r26365) -Fix [FS#5867]: Don't draw the cursor when its sprite isn't ↵fonsinchen
ready and set _screen.dst_ptr immediately when the buffer changes (frosch123)
2014-02-22(svn r26360) -Revert (r25550) / Fix [FS#5922]: ClientSizeChanged is only ↵frosch
called via WndProcGdi which already has the mutex. The issue which r25550 tried to fix still exists as FS#5867.
2014-01-13(svn r26247) -Fix [FS#5854, FS#5855]: Possible out of bounds reads with the ↵rubidium
sse blitters (MJP)
2014-01-02(svn r26211) -Add: specialised non-animated SS2 blitter (MJP)rubidium
With 32bpp base set about 30% faster than 32bpp-optimized, or about 10% for 8bpp base sets in the Draw function. Respectively about 5 and 1% of total run time
2014-01-02(svn r26209) -Codechange: remove some template magic and simplify some coderubidium
2013-11-16(svn r26009) -Fix: warning about conditional expression with enumeral with ↵rubidium
non-enumeral type
2013-08-05(svn r25684) -Change: [Win32] Draw the composition string ourselves if possible.michi_cc
2013-08-05(svn r25682) -Change: [Win32] Position the IME candidate window at the caret ↵michi_cc
position.
2013-08-05(svn r25681) -Change: [Win32] Position the IME composition window at the ↵michi_cc
caret position.
2013-08-05(svn r25680) -Codechange: [Win32] Cancel the current IME composition when ↵michi_cc
the input focus changes.
2013-08-05(svn r25679) -Codechange: [Win32] Get the result string of an IME input ↵michi_cc
directly without a trip through the window messaging system.
2013-08-05(svn r25675) -Fix: [Win32] Handle DBCS characters correctly in the ↵michi_cc
non-Unicode build.
2013-08-05(svn r25673) -Fix: [Win32] Use the right code page for converting ANSI ↵michi_cc
strings into UTF-8 for non-Unicode builds. And don't crap out on DBCS code pages either.
2013-08-05(svn r25672) -Fix: [Win32] Handle Unicode characters from outside the BMP ↵michi_cc
correctly.
2013-08-05(svn r25671) -Codechange: Pass character and key code separately to the ↵michi_cc
keyboard handler.
2013-08-05(svn r25667) -Fix: [Win32] Only forward key presses to the IME system if an ↵michi_cc
edit box has the input focus.
2013-07-01(svn r25550) -Fix [FS#5571]: [Windows] Race condition between two drawing ↵rubidium
threads could crash OpenTTD
2013-01-08(svn r24900) -Fix [FS#5389]: Comments with typos (most fixes supplied by ↵planetmaker
Eagle_rainbow)
2012-12-03(svn r24781) -Fix (r24762): [Win32] MinGW compiler warning.michi_cc
2012-11-25(svn r24762) -Fix [FS#5359]: [Win32] Don't crash when switching to an ↵michi_cc
unsupported fullscreen display mode (like 8 bpp modes in Windows 8).
2012-07-10(svn r24394) -Fix (r24188): changing resolution didn't resize the windowglx
2012-04-30(svn r24189) -Fix: when going to fullscreen and back, restore to the ↵truebrain
resolution you were, not to the fullscreen resolution (Windows only)
2012-04-30(svn r24188) -Fix-ish [FS#5151] (r1): when changing the basics of a window ↵truebrain
(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
2012-01-04(svn r23749) -Fix: [Win32] Work around a possible deadlock when initialising ↵michi_cc
threaded drawing.
2011-12-15(svn r23527) -Codechange: unify colo(u)r as far as it goesrubidium
2011-12-10(svn r23482) -Change: [Win32] Move re-painting the window and doing palette ↵michi_cc
animation into a separate thread.
2011-12-08(svn r23448) -Fix: keep a local copy of the palette in the 32bpp animated ↵rubidium
blitter so changes of the palette data during the game don't influence drawing (with SDL)
2011-12-08(svn r23446) -Codechange: move _cur_palette and it's related first/count ↵rubidium
dirty variables into a single structure
2011-11-17(svn r23241) -Codechange: make the decision when to go to the custom drawn ↵rubidium
cursor more prominently during the initialisation of OpenTTD