summaryrefslogtreecommitdiff
path: root/src/video/null_v.cpp
AgeCommit message (Collapse)Author
2021-03-08Add: [Video] move GameLoop into its own threadPatric Stout
This allows drawing to happen while the GameLoop is doing an iteration too. Sadly, not much drawing currently can be done while the GameLoop is running, as for example PollEvent() or UpdateWindows() can influence the game-state. As such, they first need to acquire a lock on the game-state before they can be called. Currently, the main advantage is the time spend in Paint(), which for non-OpenGL drivers can be a few milliseconds. For OpenGL this is more like 0.05 milliseconds; in these instances this change doesn't add any benefits for now. This is an alternative to the former "draw-thread", which moved the drawing in a thread for some OSes. It has similar performance gain as this does, although this implementation allows for more finer control over what suffers when the GameLoop takes too long: drawing or the next GameLoop. For now they both suffer equally.
2021-02-19Add: draw the screen at a steady pace, also during fast-forwardPatric Stout
During fast-forward, the game was drawing as fast as it could. This means that the fast-forward was limited also by how fast we could draw, something that people in general don't expect. To give an extreme case, if you are fully zoomed out on a busy map, fast-forward would be mostly limited because of the time it takes to draw the screen. By decoupling the draw-tick and game-tick, we can keep the pace of the draw-tick the same while speeding up the game-tick. To use the extreme case as example again, if you are fully zoomed out now, the screen only redraws 33.33 times per second, fast-forwarding or not. This means fast-forward is much more likely to go at the same speed, no matter what you are looking at.
2021-01-14Feature: Choose a sensible window size on a fresh OTTD config file. (#8536)Michael Lutz
2020-06-07Cleanup: Correct typographic errors in code comments.TechGeekNZ
2020-05-21Codechange: Use std::string in the driver and blitter selection code.Michael Lutz
2019-11-10Cleanup: Removed SVN headersS. D. Cloudt
2019-04-10Codechange: Use null pointer literal instead of the NULL macroHenry Wilson
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-01-02(svn r26209) -Codechange: remove some template magic and simplify some coderubidium
2011-11-04(svn r23119) -Fix: [Win32] Don't show a crash/assertion message box for a ↵michi_cc
GUI-less video driver.
2011-05-01(svn r22405) -Document: some more "random-ish" tidbitsrubidium
2009-12-19(svn r18545) -Fix [FS#3292]: Assign '_screen.dst_ptr' as soon as it is ↵frosch
allocated.
2009-08-21(svn r17248) -Fix: add GPL license notice where appropriaterubidium
2009-01-31(svn r15299) -Cleanup: remove many redundant includessmatz
2009-01-10(svn r14949) -Cleanup: pointer coding stylerubidium
2008-06-16(svn r13537) -Fix [FS#2090](r13523): QSortT won't work this way, use ↵smatz
Dimension instead of uint16[2] for resolutions
2008-05-06(svn r12971) -Documentation: add @file in files that missed them and add ↵rubidium
something more than whitespace as description of files that don't have a description.
2008-04-18(svn r12780) -Fix: the null blitter did segfault.rubidium
2008-01-01(svn r11734) -Change: Allow ToggleFullScreen to return the result of the ↵belugas
operation' attempt. Previously, only visual clues were available. -Fix[FS#1519]: When you can not use this resolution at full screen, now you'll know that it failed. As for the reason it did not work, each computer/OS has its reason.
2007-12-23(svn r11684) -Codechange: split gfx.h in a type and functional header.rubidium
2007-12-19(svn r11667) -Codechange: split window.h into a header that defines some ↵rubidium
'global' window related types, on that defined 'global' window functions and one that defines functions and types only used by *_gui.cpps.
2007-07-13(svn r10542) -Codechange: use class member instead of global variable for ↵peter1138
null ticks value
2007-07-13(svn r10537) -Backport r10536: added option for null-driver to configure how ↵truelight
long it should run (-vnull:ticks=10000)
2007-07-05(svn r10444) -Codechange: switch to c++ classes and inheritance for ↵peter1138
sound/music/video drivers, using self-registration based on the blitter-model.
2007-06-17(svn r10190) -Codechange: merged renderer and blitter to one single class ↵truelight
API: blitter -Codechange: introduced a hierachy of blitters to avoid a lot of code duplication Note: this allows much easier adding other types of video-drivers, like OpenGL
2007-06-12(svn r10121) -Codechange: split renderer from rest of code; no longer any ↵truelight
code directly accesses the video-buffer -Add: added NULL blitter and renderer, which are always used for -vnull -Add: dedicated driver doesn't blit nor render by default. Can be overruled by user. (-D -b 8bpp-optimized) -Remove: removed CTRL+D from win32, which is incompatible with above -Add: extended screenshot support for PNG and BMP -Codechange: remove all hardcoded 8bpp references and replace them with more dynamic ones -Codechange: minor stuff in blitters
2007-05-14(svn r9835) -Codechange: use Pixel typedef instead of byte where ever possibletruelight
2007-03-07(svn r9050) -Codechange: Foo(void) -> Foo()rubidium
2007-01-10(svn r8038) -Merge: the cpp branch. Effort of KUDr, Celestar, glx, Smoovius, ↵rubidium
stillunknown and pv2b.
2007-01-10(svn r8033) [cpp] - Prepare for merge from branches/cpp (all .c files ↵KUDr
renamed to .cpp)