pugl.git - Pugl GUI library

Age	Commit message (Collapse)	Author	Files	Lines
2020-05-16	Use email address in copyright headers	David Robillard	1	-1/+1
	Not really sure why I used a web link here (maybe because it's more stable), but this is more conventional.
2020-05-16	Fix file documentation	David Robillard	1	-2/+3

2020-03-16	Cleanup: Add missing includes	David Robillard	1	-0/+2

2020-03-16	Add timer events	David Robillard	1	-0/+11

2020-03-09	Add PuglEventClient and puglSendEvent()	David Robillard	1	-0/+1
	This event makes it possible to send an arbitrary event to a view, which is useful for many things. In particular, this method of communication with views will wake up the event loop, unlike hacks in applications that share data in some other way.
2020-03-01	Cleanup: Fix includes	David Robillard	1	-1/+3

2020-02-02	X11: Dispatch exposures from event callbacks in the same iteration	David Robillard	1	-0/+3

2019-11-03	Move platform stub configuration code to platform headers	David Robillard	1	-0/+13
	This allows backends which use basic software rendering (like Cairo) to share the common basic window format setup code.
2019-09-07	Add clipboard support	David Robillard	1	-0/+1

2019-09-03	Add puglDispatchEvents()	David Robillard	1	-0/+2

2019-09-03	X11: Move input method to world	David Robillard	1	-1/+1

2019-09-03	X11: Move atoms to world	David Robillard	1	-10/+11

2019-09-03	Add PuglWorld	David Robillard	1	-0/+4
	The old API was broken for programs that manage multiple views, since it was impossible to wait for events on any view. There are also several functions in the API which are not actually associated with views at all, so those can now be moved to the more appropriate PuglWorld to make this more clear. The old puglInit() and puglDestroy() functions are preserved for compatibility, but marked as deprecated.
2019-07-31	X11: Support UTF8 in window titles	JP Cimalando	1	-0/+2
	It's possible that this does bad things if a UTF8 string is used on a system that does not support it (because XStoreName is still called), but I have no idea how likely this scenario is. Leaving it this way because it means the ASCII case will still work everywhere, and it's easy enough to avoid if this is a problem.
2019-07-29	Reorganize source to separate private implementation details	David Robillard	1	-0/+41
	Taking a page from C++ convention, where "detail" is for things that should not be included in user code.