summaryrefslogtreecommitdiff
path: root/src/video
AgeCommit message (Collapse)Author
2010-08-25(svn r20619) -Fix [FS#4070]: [OSX] Limit minimum window size to 64x64 like ↵rubidium
all other platforms (matheweis)
2010-08-01(svn r20286) -Codechange: Unify end of doxygen comments.frosch
2010-08-01(svn r20283) -Codechange: Unify start of doygen comments.frosch
2010-08-01(svn r20281) -Codechange: unify case scope closure + break coding stylerubidium
2010-07-29(svn r20239) -Doc: Give a common name to all fall throughs (FALL THROUGH).terkhen
2010-07-24(svn r20211) -Codechange: Indented code should have curly braces around it.alberth
2010-07-19(svn r20192) -Cleanup: bye bye variables.h, bye bye VARDEF... you won't be ↵rubidium
missed :)
2010-07-19(svn r20186) -Codechange: remove VARDEF from _realtime_tick and ↵rubidium
_rightclick_emulate
2010-07-19(svn r20183) -Codechange: make _do_autosave and _dedicated_forks not use ↵rubidium
VARDEF and put them in a more logical location
2010-07-06(svn r20084) -Fix [FS#3919] (r7157): don't try to handle mouse events when ↵glx
the cursor ha left the window
2010-06-12(svn r19965) -Cleanup: Use size of buffer, not magic number.peter1138
2010-06-05(svn r19933) -Fix [FS#3804]: Keep _current_company and _local_company in ↵frosch
sync during GUI operation.
2010-05-19(svn r19861) -Fix (r19814): Silence a warning.frosch
2010-05-13(svn r19814) -Codechange: give some more unnamed enums a name, in case they ↵rubidium
consisted of unrelated values use static const (u)int
2010-04-09(svn r19593) -Codechange: improve loading/executing the desync logsrubidium
2010-02-10(svn r19084) -Codechange: minor coding-style fixupssmatz
2010-02-04(svn r19012) -Fix (r19003): macos.h is not in video/cocoa/ but in os/macosx/.yexo
2010-02-04(svn r19003) -Fix [FS#3194]: [OSX] OS X 10.5+ does not (always?) handle 8bpp ↵rubidium
graphics in a suitable manner. This is actually not a fix but a nasty work around; you can still easily trigger the bug/issue by overriding the 'default' blitter choice (Brad Oliver). I can/have not test(ed) (including compiling) this fix. Bjarni once suggested that 8bpp works for him on 10.5, so apparantly not all 10.5+ does not handle 8bpp graphics. Nevertheless, it seemed that for some systems the already existing 'does this support 8bpp' did not work, i.e. the OS API seemed to suggest that 8bpp worked when it actually did not. So, I don't know what is going on precisely here but it's definitely not nice to suggest that it supports 8bpp when it doesn't. So just ditch 8bpp support for anything that we suspect might not support 8bpp...
2010-01-15(svn r18809) -Codechange/Cleanup: remove unneeded headers from some files, ↵rubidium
if a header require a header make it include that header
2010-01-13(svn r18796) -Fix [FS#3521]: [SDL] possible deadlock when killing OpenTTD ↵rubidium
while starting it
2010-01-12(svn r18792) -Fix [FS#3522] (r18709): crash when using the 32bpp blitter ↵rubidium
with a dedicated server
2010-01-12(svn r18790) -Revert (r18001,r18177,FS#3515): Viewport could still jump ↵peter1138
under high CPU load. Revert as change caused more problems than it fixed.
2010-01-04(svn r18709) -Fix (r10227,FS#3464): Animation buffer for 32bpp-anim blitter ↵peter1138
was only validated during sprite blitting, other drawing operations didn't check it. Initial startup and window resize could therefore lead to crash.
2009-12-20(svn r18573) -Fix [FS#3198]: [OSX] Try to get a generic RGB colour space if ↵michi_cc
getting the system colour profile failed. (tyler)
2009-12-19(svn r18547) -Fix [FS#3388]: missing thread synchronisation when changing ↵rubidium
the resolution for SDL via the in game menu
2009-12-19(svn r18545) -Fix [FS#3292]: Assign '_screen.dst_ptr' as soon as it is ↵frosch
allocated.
2009-12-03(svn r18390) -Fix (r17776): [SDL] Reinstate pointer update on 'idle' loop.peter1138
2009-11-18(svn r18177) -Fix (r18001): [SDL] Viewport could jump when mouse moved and ↵peter1138
right button pressed at the same time.
2009-11-09(svn r18031) -Codechange: since basically r7157 adding up 'all' mouse ↵rubidium
movement isn't needed anymore because after each even that movement is handled and the counter is reset. As such simply assigning instead of adding works.
2009-11-09(svn r18030) -Fix: screen jumped a bit for at least SDL and Allegro when ↵rubidium
right-click-dragging
2009-11-07(svn r18001) -Codechange: [SDL] When the mouse cursor is locked into ↵peter1138
position when scrolling a viewport, warp the mouse pointer to the centre of the window. This gives maximum freedom of movement. The pointer position is restored when the lock is removed. Visually the mouse cursor stays where it was.
2009-11-02(svn r17950) -Fix (r17776): _draw_mutex was never destroyed, _draw_thread ↵smatz
was never joined
2009-11-02(svn r17949) -Fix (r17776): unlock mutex before deleting it when creating ↵smatz
drawing thread failed
2009-10-19(svn r17815) -Fix [SDL]: asynchronious drawing caused extra unresponsiveness ↵rubidium
during map generation; disable the threading while generating a map
2009-10-17(svn r17793) -Fix: [OSX] The splash image wasn't displayed if the Quartz ↵michi_cc
video driver was used.
2009-10-17(svn r17787) -Codechange: be a bit more verbose about while allegro failed ↵rubidium
with some actions.
2009-10-15(svn r17776) -Codechange: [SDL] make "update the video card"-process ↵rubidium
asynchronious. Profiling with gprof etc. hasn't shown us that DrawSurfaceToScreen takes a significant amount of CPU; only using TIC/TOC it became apparant that it was a heavy CPU-cycle user or that it was waiting for something. The benefit of making this function asynchronious ranges from 2%-25% (real time) during fast forward on dual core/hyperthreading-enabled CPUs; 8bpp improvements are, in my test cases, significantly smaller than 32bpp improvements. On single core non-hyperthreading-enabled CPUs the extra locking/scheduling costs up to 1% extra realtime in fast forward. You can use -v sdl:no_threads to disable threading and undo this loss. During normal non-fast-forwarded games the benefit/costs are negligable except when the gameloop takes more than about 90% of the time of a tick. Note that allegro's performance does not improve with this system, likely due to their way of getting data to the video card. It is not implemented for the OS X/Windows video backends, unless (ofcourse) SDL is used there. Funny is that the performance of the 32bpp(-anim) blitter is, at least in some test cases, significantly faster (more than 10%) than the 8bpp(-optimized) blitter when looking at real time in fast forward on a dual core CPU; it was slower. The idea comes from a paper/report by Idar Borlaug and Knut Imar Hagen.
2009-10-14(svn r17773) -Cleanup: sdl.h isn't needed for allegrorubidium
2009-10-12(svn r17768) -Fix (r17715): [OSX] Newer GCC versions don't like jumping over ↵michi_cc
variable definitions with goto's. (planetmaker)
2009-10-04(svn r17717) -Codechange: [OSX] Replace deprecated variable type.michi_cc
2009-10-04(svn r17716) -Codechange: [OSX] Invoke a (semi-)private Objective-C method ↵michi_cc
in a way that does not rely on the SDK version.
2009-10-04(svn r17715) -Cleanup: [OSX] And a final round of coding style and some ↵michi_cc
cleaning.
2009-10-04(svn r17714) -Cleanup: [OSX] Apply more coding style.michi_cc
2009-10-04(svn r17713) -Cleanup: [OSX] Move variable definitions to first use and ↵michi_cc
apply more coding style.
2009-10-04(svn r17712) -Codechange [FS#1411]: [OSX] Replace undocumented process ↵michi_cc
manager API calls with a documented alternative. (pyth)
2009-10-04(svn r17711) -Codechange: [OSX] Don't use deprecated methods to construct a ↵michi_cc
Cocoa string.
2009-10-04(svn r17707) -Fix: [OSX] Show the OS mouse cursor when displaying a dialog ↵michi_cc
box if it was hidden.
2009-10-04(svn r17706) -Codechange: [OSX] Rework the crash handling to use the common ↵michi_cc
CrashLog infrastructure.
2009-10-04(svn r17702) -Change: [OSX] Assure that the minimal OSX version is defined ↵michi_cc
in all cases. -Codechange: [OSX] Improve conditional defines for OS version dependant code.
2009-10-04(svn r17701) -Codechange: don't start line with a space if it's not inside ↵smatz
comment