| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
Although these are rare, they are still not indicative of bugs so
an exception (which ends up in the log and might also be shown to
the user) is more appropriate than an assert. Asserts should only
be used to catch blatant API misuse and similar.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
It was confusing and not properly used everywhere.
Callers should use the stride they get when they get
the buffer pointer.
|
| |
|
|
|
| |
This allows us to gracefully fall back to the FLTK code in case the
platform specific code cannot be used.
|
| |
|
|
|
|
|
| |
that is. Do it the documented way by having a CGBitmapContext instead.
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4956 3789f03b-4d11-0410-bbf8-ca57d06f2519
|
| |
|
|
|
|
|
|
|
|
| |
the necessary defines will only be visible as a side effect of
including other headers, leading to problems with things like
translations, which will fail in various places.
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4646 3789f03b-4d11-0410-bbf8-ca57d06f2519
|
|
|
CPU usage unfortunately, but at least we're now using the native pixel format
of our server which avoids a conversion on the server side.
git-svn-id: svn://svn.code.sf.net/p/tigervnc/code/trunk@4504 3789f03b-4d11-0410-bbf8-ca57d06f2519
|
