Although most events in other frames were blocked, it was
possible to bring other frames to the front and to select
menu items in other frames.
original commit: 9d563c786a71b621fcd2909c917b49939e0d11b0
The `get-handle' method provides the underlying Cairo surface for
a bitmap, while the unsafe `make-handle-brush' function supports the
use of a Cairo surface as a `brush%'.
Also, add `racket/draw/unsafe/cairo-lib', which simplifies access
Cairo from external libraries. Documenting `racket/draw/unsafe/cairo'
might be better, but that's a lot more work.
original commit: 4f197f4ba944ee802e15fb3323f34a074e915db6
starts up on all of the days that have easter eggs (well, except 7/2,
since that one is hard to interpose on and hasn't changed in a long
time)
original commit: 617df05ef7d43c04cfaf6978c52619e1865a4812
pixel of space in between lines in DrRacket.
This change is based on Matthew's experience having a look
at the font setup on the three platforms.
He writes:
> * Mac OS X: the convention seems to be to add space between lines.
> TextEdit, for example, looks like DrRacket: the maze has spaces.
>
> (I can't find a font that makes the maze look right, actually, even
> if I adjust the line spacing.)
>
> * Windows: the convention seems to be that space is built into the
> font. DrRacket (and SirMail) draw lines more sparsely than Notepad.
>
> Perhaps consistent with the differing conventions, the height of
> "Courier New" at 11-pixel size is 14 on Windows, 13 on Mac OS X.
>
> * Unix: the convention seems to be to add space. DrRacket looks like
> the default Terminal and Text Editor programs on Ubuntu.
>
> The maze nevertheless looks right everywhere, because the glyphs
> extend an extra pixel above the declared bounding box!
original commit: 0d6b82537776ad4bd850e3b7c5cc1bdaa209b865
Before this commit, opening collects/drracket/private/unit.rkt required
about 17.5 megabytes of memory and after this commit, it is down to
about 15 megabytes.
The precise measurement I did was to create a frame and a scheme:text%
object in it, record the result of current-memory-use, open the file,
and record current-memory-use again.
For comparison, using a text:standard-style-list% object instead of
the scheme:text% requires only about 4.1 megabytes. One difference
being that there are about 3x more snips (10,204 vs 33,901 (after the
commit)), since we have one snip for each region that has a different
color in the scheme:text version, and the text:standard-style-list has
no colors and thus about two per line (there are 5006 lines in the
file).
original commit: a7cb8fdc84f3b592c812468e5e7486d4f7d5bbb6
Previously, sandbox creation used `gui?', which is the result of
`gui-available?' at the time that `racket/sandbox' is instanited.
This change makes sandbox behavior less sensitive tothe order in
which modules `require'd into a program are intiantiated.
The change depends on a new `sandbox-make-namespace' default
function for `sandbox-namespace-specs'. The new function uses
either `make-base-namespace' or `make-gui-namespace', depending
on whether the GUI library is available at that point.
A new `sandbox-gui-enabled' parameter can disable use of the
GUI library even if it is available.
The `gui?' binding is still exported for backward compatibility,
but it shouldn't be used anymore.
original commit: 5630a3a1cab8d7953bfbb290bd6ae63c84ead605
The set-replace-start and get-replace-search-hit methods were
missing in the text:searchable<%> interface. The latter was
also undocumented.
original commit: 04f7bdbb021d1dbcac959eed439050abc36ee1b7
Recorded clipping, transformations, and alpha didn't compose with
the target DC's existing clipping, transformations, and alpha.
original commit: f79e2b4ee0bbe6a7302f658e78155b11d9dd7db8
also: use it in pict's rendering and
remove redex's platform-specific font choice
(going back to using 'modern on all platforms)
closes PR 12554
original commit: 1945ff270962679e13f66131c5b3eb91cc1edb2f
Treat a "face" as a font description only if it has a comma,
otherwise go back to treating it as a family name.
This change fixes the problem of parsing "Times New Roman"
as "Times New, Roman".
original commit: 530b35379830819f7de46c80dc9f9691a17fcc7b
When an eventspace is created, its thread implicitly calls
`yield'. It now effectively loops with `yield' and while
catching continuation aborts.
Closes PR 12566
original commit: 967372c23d9b68d011993435cc91e99e26616c20
Use the system-supplied region to intersect with the
window region, so that drawng the border doesn't replace
the window content.
See also Kieron Hardy's post on the users' list, 2/7/12.
original commit: af62391c8cf8204b96299a0906e2e8656b921213
get any events (this shouldn't be necessary unless one gets lost
somehow, but apparently that can happen)
original commit: 3b2cf3f7a4bc4949fc5fa3f626f789ff983be64a
now it should return only the canonical names of the keybindings
(instead of potentially returning both the canonical and
non-canonicalized names)
original commit: 95ac3c86f789d6514a3a6c6a2f16d28f7d6f0ea9
