Before, they would create a crippled version in that mode, but
that is no longer necessary (it may never have been necessary,
but it certainly hasn't been necessary in a while)
original commit: 8fb8f561c48ad7660b049a318511a929c39e4c06
Just in case a relative path turned into an absolute path doesn't
work as a string, add support for a bytes encoding.
original commit: d722fa42df16e9a74da109582e915c63f59a7a29
Mostly, replace some method calls with field selectors (where the
path is important enough that it seems worthwhile).
original commit: 78321aa4e6ba0a1a3cc32ae41d2d85c16756305a
Some places in the editor API accept an object as an argument
where the object's identity is relevant. In that case, `object=?`
must be used instead of `eq?` to work right with contracts.
original commit: dc0653383f1eb54b05afc0c6f09106536950d0ca
Use the field in a `snip%` that is otherwise used by a `text%` owner
to store line information. Reusing the field avoids the need for
an `eq?`-based hash table of snips.
original commit: 2bd8c2d8edcb54abf21ddd6ff942b656d78d502a
The `~` methods on snip and editor-related classes are not documented
or called from anywhere. They corresponded to destructor methods back
when the classes were ported from C++.
original commit: 70d91b5516a24bb0640cbb0818e6d31f529db539
This change allows undo configuration of individuals editors to
Emacs-style undo (in addition to the 'GRacket:emacs-undo global
preference that is read on startup).
Also, fix a bug in Emacs-style undo that dates from the port of
the editor into Racket.
original commit: f22a89506091203cdd310fb33821513daf77116e
Move new initialization arguments to the end to avoid backward
incompatibility, add fields to `module-event%`, and include history
notes in the documentation.
original commit: be58be349abc2d22c3d2937ed88bcb7b8a15ac07
In particular, Mod4 is used for the Command button when you run Linux
on Mac hardware. I don't know how to get the others, but added them
for safety.
original commit: e7f0f3587a5fee9b3b4185948485bb7df1ac3bda
Atomicity was accidentally turned off in ca0418d47d.
For whatever reason, this bug seems to cause lots of trouble with
32-bit Mac OS X and not as much for 64-bit Mac OS X.
original commit: 13b1d0733a8e686e7b17bf33cfff9f43bcfd5604
Found via TR. The two last arguments are supposed to be
optional but the method only accepted 1 or 3 arguments.
original commit: fca126bf01f990d5600655a879046c95230edc64
The `grab-caret` method's argument is supposed
to be optional according to the documentation.
original commit: 14b133296f39532f12b51fb4bb259cd947c24d1a
(technically, strengthen the way it is written in the docs; it
was already being enforced that way)
original commit: 370418ac2e9f00a981422bee0551d1603b246005
Partly reverts d8a438231f by making the alignment scale always default
to 1, but allows the "fix" (for programs that was drawing to a bitmap
with backing scale 2 to be like drawing with scale 2 into a bitmap
with backing scale 1) by setting the alignment scale to 2 for a
drawing destination that has a backing scale of 2.
original commit: 582e992501c8e6833a82412235731a9d0416b3b9
One consequence is that drawing with a pen of width 0 into
a canvas% object on a Retina display draws a line that is
half as wide as a pen of width 1.
original commit: 7dc63162728b695b93a28b047dfafc841e4302e4
Generalizes backing-scale support created for `make-platform-bitmap`
and Mac OS X in Retina mode so that any bitmap can be created with
a backing scale (except monochrome bitmaps or bitmaps with masks).
original commit: 5e903441a4ab76305d4768ae96b9fef827bac860
