aboutsummaryrefslogtreecommitdiffstats
AgeCommit message (Collapse)AuthorFilesLines
2019-07-29Set hidden visibility globallyDavid Robillard1-4/+7
2019-07-29Properly check for libmDavid Robillard1-6/+5
2019-07-29Build both static and shared library by defaultDavid Robillard1-2/+4
2019-07-29Windows: Enable shared library buildDavid Robillard1-1/+0
2019-07-29Cleanup: Use fancy syntax for waf environmentsDavid Robillard1-8/+8
2019-07-29Cleanup: Clean up includes and call IWYU in lint targetDavid Robillard9-4/+26
2019-07-29Cleanup: Fix Python whitespaceDavid Robillard1-2/+7
2019-07-29Fix various clang-tidy warningsDavid Robillard4-18/+26
2019-07-29Fix potential memory leak on errorDavid Robillard1-0/+1
2019-07-29Reorganize source to separate private implementation detailsDavid Robillard16-57/+98
Taking a page from C++ convention, where "detail" is for things that should not be included in user code.
2019-07-29Clean up file documentationDavid Robillard16-10/+34
2019-07-29Completely separate backends from platform implementationDavid Robillard12-76/+47
This removes PuglContextType and allows the user to pass a backend directly. Normally this would come from one of the two accessors declared in the headers, but it would be possible to add backends without changing any of the existing code at all. Unfortunately, it is not possible to preserve backwards compatibility and achieve the ultimate goal of linking only to the required dependencies, so puglInitContextType() has just been removed.
2019-07-29Expose PuglBackend typeDavid Robillard2-3/+5
2019-07-29Add deprecation macro and deprecate puglInitResizable()David Robillard4-4/+14
2019-07-29Move trivial backend dispatch functions to common codeDavid Robillard4-54/+18
2019-07-29Move backend to PuglViewDavid Robillard6-53/+53
2019-07-29Mac: Factor some functionality out into a backendDavid Robillard1-38/+151
Not quite as isolated as the other platforms at this point (Objective C makes this tricky), but a step towards that and being able to simplify things in the common code by assuming that all platforms have a backend.
2019-07-29Windows: Disable DPI scalingDavid Robillard1-0/+12
This is probably not ultimately the right thing, especially without a DPI/scaling access API, but it makes the horrible default fuzziness go away.
2019-07-29Windows: Add Cairo supportDavid Robillard3-2/+223
2019-07-28Windows: Factor out GL backendDavid Robillard5-271/+428
2019-07-28Make enterContext take a drawing parameter like leaveContextDavid Robillard9-42/+54
These need to be symmetric because sometimes different things need to happen in either situation when entering the context as well.
2019-07-28Give backends general namesDavid Robillard6-30/+52
Towards making them opaque and exposing them to the user to decouple the core library from backends. The general names mean that it won't be possible to build multiple backends for one platform into the same binary, but that seems reasonable for now, and it will make things simpler without needing to add a bunch of dispatch code. That will still be possible if it's ever needed, though.
2019-07-28Rename getHandle to getContext for consistent terminologyDavid Robillard4-6/+6
2019-07-28Rename PuglDrawContext to PuglBackendDavid Robillard7-29/+29
This name was pretty confusing since there is already the concept of a "context".
2019-07-28Cleanup: Remove redundant preprocessor checksDavid Robillard1-4/+0
2019-07-28Cleanup: Remove redundant context type checksDavid Robillard1-7/+3
2019-07-28Cleanup: Add some constnessDavid Robillard1-2/+2
2019-07-28Mac: Set test app bundles as high resolution capableDavid Robillard2-0/+26
This fixes the nasty title bar scaling.
2019-07-28Mac: Fix warningDavid Robillard1-1/+2
2019-07-28Fix unused parameter warnings and prevent rotDavid Robillard9-28/+58
2019-07-28Fix building pugl_cairo_test as C++David Robillard1-1/+1
2019-07-26Windows: Implement size constraintsDavid Robillard3-1/+50
There are two possible approaches to take here: try to expand dimensions that are not being explicitly resized (for example expand the bottom when dragging right), or just stop single-dimension resizes if they would go out of range. I chose the latter here for two reasons: it's hard to always do something smooth and unsurprising with the first approach (and it would require more code), and it can be nice from the user's perspective to easily be able to resize the window to exactly one of its aspect ratio limits. For example, it is very easy to drag pugl_test to 1:1 or 16:9. In other words, simplicity and user power wins.
2019-07-25Clear GL context in puglLeaveContext() on all platformsDavid Robillard2-0/+3
2019-07-25Improve packing of PuglViewImplDavid Robillard1-16/+13
2019-07-25X11: Fix unused parameter warningsDavid Robillard1-0/+4
2019-07-25X11: Close input context on destructionDavid Robillard1-0/+6
2019-07-25Add missing includeDavid Robillard1-0/+1
2019-07-25Add logo resourcesDavid Robillard3-0/+376
Because branding is very important for low-level platform abstraction libraries. More seriously, to have something to test icon support with.
2019-07-25Mac: Fix build on MacOS older than 10.10David Robillard1-0/+6
2019-07-25Mac: Use mach_absolute_time()David Robillard1-4/+3
This fixes the build for older versions of MacOS, since clock_gettime() was only added in 10.12.
2019-07-25Use standard Cairo include paths everywhereDavid Robillard2-3/+3
Weird convention, that.
2019-07-25Windows: Fix initial display once againDavid Robillard1-5/+6
I have no idea why this affects anything, but it seems to fix this, this time, again. One of these days I'll get it right.
2019-07-25Use standard cairo include pathDavid Robillard1-1/+1
2019-07-25Fix type of PuglEventText::timeDavid Robillard1-1/+1
2019-07-25Mac: Fix event Y coordinatesDavid Robillard1-9/+9
2019-07-25Handle backspace and delete consistently across platformsStefan Westerfeld2-0/+4
2019-07-25Remove PUGL_API from documentationDavid Robillard1-6/+13
2019-07-24Update READMEDavid Robillard1-17/+17
2019-07-24Support additional special keysDavid Robillard4-79/+133
2019-07-24Unify key and character fields and separate text eventsDavid Robillard7-220/+288
Only one field is necessary to store any kind of key, including special keys, since PuglKey occupies a reserved Unicode region. This is generally much simpler to deal with since there is only one value to dispatch on. Text events are separated from key events (like Windows but unlike MacOS or X11) because it is not possible to derive text events from key press events when they occur on Windows. Since merging the two has been the source of some confusion, this approach has some advantages anyway, even though it introduces the need to handle another event type. In the process, text input has been almost completely rewritten. I have tested this with a compose key on X11 and dead keys on Windows and MacOS and everything seems to work correctly, though there may (as always) still be issues with more exotic input methods.
generated by cgit v1.2.1 (git 2.18.0) at 2024-11-22 23:08:47 +0000