- 02 Feb, 2011 2 commits
-
-
Sam Lantinga authored
The rendering functions take a context so it's clear what window they're drawing to. This also potentially opens to the door to multi-threaded rendering in the future.
-
Sam Lantinga authored
-
- 01 Feb, 2011 17 commits
-
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
Making the API simpler, the renderer present semantics are always having a backbuffer and then discarding it. This is best for hardware accelerated rendering. --HG-- extra : rebase_source : bbe6641fce097c79ccd47f4e1ea6b27683fd0acb
-
Sam Lantinga authored
--HG-- extra : rebase_source : 880752438aae8f6526503d220bad91aabc3a7d1c
-
Sam Lantinga authored
--HG-- extra : rebase_source : f06ea01caa64c8ad14170c723e5af52dad64d779
-
Sam Lantinga authored
--HG-- extra : rebase_source : d00f0590e133604070f978762a6728b4afde02ca
-
Sam Lantinga authored
Making the API simpler, scaling is always defined as linear interpolation and should be supported as much as possible on all renderers. --HG-- extra : rebase_source : 4edac7fd162a2eb37a50159b958db37a03e944a5
-
Sam Lantinga authored
--HG-- extra : rebase_source : 3fc2560c02393bf9e7c46360fc24f2585c9409be
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
Vittorio Giovara 2011-02-01 02:25:48 PST i have attached an updated patch that fixes this behaviour
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
Vittorio Giovara 2011-02-01 02:21:50 PST with the attached patch, the opengles context will always use the maximum screensize available; this is particularly useful for supporting retina display on latest iphone. please note: Apple documentation warns that using the "upscaled" gl context actually uses more memory and bandwitdh, so it might be worth to let the user decide whether to disable it or not, either with a flag or a sdl function...
-
Sam Lantinga authored
-
- 30 Jan, 2011 1 commit
-
-
Sam Lantinga authored
kwm@rainbow-runner.nl 2011-01-30 06:28:27 PST Created attachment 562 [details] Build fix with clang. When building sdl 1.2.14 with the Clang compiler http://clang.llvm.org . The build fails in src/video/mmx.h with the following error: -------------------------------------------------- ./src/video/SDL_RLEaccel.c:831:5: error: invalid operand for instruction CHOOSE_BLIT(RLECLIPBLIT, alpha, fmt); ^ ./src/video/SDL_RLEaccel.c:831:17: note: instantiated from: CHOOSE_BLIT(RLECLIPBLIT, alpha, fmt); ^ ./src/video/SDL_RLEaccel.c:831:5: note: instantiated from: CHOOSE_BLIT(RLECLIPBLIT, alpha, fmt); ^ ./src/video/SDL_RLEaccel.c:647:23: note: instantiated from: blitter(2, Uint8, ALPHA_BLIT16_565MMX); \ ^ ./src/video/SDL_RLEaccel.c:282:4: note: instantiated from: movq_r2m(mm3, *dstp); \ ^ In file included from ./src/video/SDL_RLEaccel.c:99: ./src/video/mmx.h:379:28: note: instantiated from: #define movq_r2m(reg, var) mmx_r2m(movq, reg, var) ^ <scratch space>:192:1: note: instantiated from: "movq" ^ <inline asm>:1:2: note: instantiated into assembly here movq %mm3, %dx ^ -------------------------------------------------- According to the clang developers this is a invalid inline assembly. Using the attached patch from the last commit in the below bug report fixes the compile. More details from: http://llvm.org/bugs/show_bug.cgi?id=6730
-
- 28 Jan, 2011 12 commits
-
-
Sam Lantinga authored
-
Sam Lantinga authored
Kees Bakker to sdl The main.c for the template is still targeting SDL1.2. Here is the patch to make it work for SDL1.3 (I'm hoping the mailing lists accepts attachments.) In this patch I have also changed the shell script that assembles the Template. Since there is now only one lib target (same name for "device" and "simulator" version) I copy the simulator library to the destination with the name libSDLSimulator.a. This is not a satisfactory solution, because both libraries are included in the project while only one is needed (depending on the selected environment). However, I'm not fluent with Xcode to say what a better solution would be. Kind regards, Kees Bakker
-
Sam Lantinga authored
Joseba García Echebarria 2010-12-15 01:55:22 PST I believe the crash is caused by a check not being performed on wether an SDL_Touch element is NULL before using it in the SDL_SendTouchMotion function in src/events/SDL_touch.c around line 400. Judging from the rest of the code, there's a missing if (!touch) { return 0; } before using "touch" as SDL_GetFinger(), SDL_GetFingerIndexId() use touch->num_fingers without checking. I can attach a patch if you like. It seems pretty straightforward, though. I have yet to discover why touch is being returned as NULL as this error is only triggered when an actual gesture has been performed, maybe something related to SDL_AddTouch()?
-
Sam Lantinga authored
Next I'll be working on generalizing the event sources and making the event queue lock-free. :)
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
-
krogoway authored
-
Sam Lantinga authored
-
Sam Lantinga authored
I also added an implementation to dynamically query it, but didn't expose it since most x86 CPUs have an L1 cache line size of 64 bytes.
-
- 27 Jan, 2011 8 commits
-
-
Sam Lantinga authored
-
krogoway authored
When the last window is closed and the SDL_WINDOWEVENT_CLOSE event is sent, send the SDL_QUIT event. Common.c now destroys the SDL_Window upon a SDL_WINDOWEVENT_CLOSE event to ensure that all windows get closed properly and the new code to handle the last window closes gets executed.
-
Sam Lantinga authored
when .cc files are used due to bad sed substitution on multiple passes: $(objects)/SDL_BeApp.lo: $(objects)/SDL_BeApp.lo: ./src/main/beos/SDL_BeApp.c $(LIBTOOL) --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -c $< -o $@c $(LIBTOOL) --mode=compile $(CC) $(CFLAGS) $(EXTRA_CFLAGS) -c $< -o $@ Signed-off-by: François Revol
-
Sam Lantinga authored
The new timer model is formalized as using a separate thread to handle timer callbacks. This was the case on almost every platform before, but it's now a requirement, and simplifies the implementation and makes it perform consistently across platforms. Goals: * Minimize timer thread blocking * Dispatch timers as accurately as possible * SDL_AddTimer() and SDL_RemoveTimer() are completely threadsafe * SDL_RemoveTimer() doesn't crash with a timer that's expired or removed
-
Sam Lantinga authored
-
Sam Lantinga authored
-
Sam Lantinga authored
Ozkan Sezer 2011-01-26 12:33:42 PST I got warnings from SDL_windowskeyboard.c when I compiled for win64.
-
Sam Lantinga authored
-