the rearrangement moves the string constants documentation
into a package over by the string-constants implementation
and adds the string-constants (meta) pkg.
original commit: 8cdd106b87b028522ad01a5304709d010db3cb9d
This reverts commit 3c439a773138ca86a3810de6a37912ff588f7d0e.
Instead of changing the default colors, add support for color
schemes and then use these colors as a starting point for a new
color scheme
original commit: 136c18f7e925a04115f631c7d17164ed2c8d268d
Also, a bit of Rackety (triggered because I would have had to turn a
letrec into a letrec-values to support disabling the ok button (and
also because the code was indented with tabs and not just spaces))
original commit: c0c6861497ea714e2259a8b55bcdc9d28f83ef5d
it no longer changes the background to the inverse of the
foreground (for the default text color) but instead uses
the color of the 'framework:basic-canvas-background preference
Thanks to Laurent Orseau for the fix
original commit: f9df5ad4e92ec8bba8012ab3d49c75523af83592
Also, move remaining "srfi" libraries to "srfi-lite-lib".
In principle, "base" should depend on "scheme-lib" and
"srfi-lite-lib", and a new "base2" package would represent the new,
smaller base. But I don't think the window has yet closed on
determining the initial "base" package.
The "srfi" libraries moved to "srfi-lite-lib", instead of "srfi-lib",
to avoid creating many extra dependencies on "srfi-lib" and all of its
dependencies. The SRFIs in "srfi-lite-lib" depend only on "base",
and they are used relatively widely.
original commit: d175c3949c602672d61734b3fc54750da1d57f89
This should make it disappear properly when
the file's width goes down below the column guide
fix a bug in 27603faf, I believe
original commit: 5800ce1cec7a678b3e67ba259baa507dfc6b7b82
- paren color from brown to a neon blue
- string and number constants from green to a bright purple
- lighten the comment color
the basic problem is to try to keep the red error color very distinct
from the others and try to keep the others distinct from each other
(but that's less important)
original commit: 3c439a773138ca86a3810de6a37912ff588f7d0e
In a container sequence, hides and shows are delayed, but
reparenting needs the hide operation to really complete.
original commit: 76aa80c0e9dd13d3fdc3a78353b32ca6ad30ad1c
Extra margins added by instantiating `message%' inside
`radio-box%', etc., made labels line up especially badly.
original commit: b24eb311dd744db70f0ae29a18994555b4499dea
relative to some default settings instead of saving
the actual values
so changes to the default imply changes to everyone's actual
values for the prefs
closes PR 13810
original commit: 5f0c06956a2726a64b158ef1fc828c326a93a7ef
The keys.ss framework test suite seems to confirm this fix, altho
I'm not sure how exactly.
Also tweak the stress test
original commit: 9888c7f496bbb48978f46cf91fe2638a93b2c68b
Unfortunately, not the bug I was hoping to find.
This bug appears to be very old, however; perhaps
as old as the colorer itself.
original commit: 5aeca646d463ba4b065d0301465fdcf93415f7b5
also make keys.rkt test suite be less likely to corrupt the
preferences file (when run in standalone mode)
original commit: 593ab2d51fa5d44e107fa626d93c4106ef1ff33b
The `future-parent` argument is actually ignored now and
can be any value, so document it as such.
original commit: 8c7a6709b01790f3a920cd8d509a8a85a2545583
Add `dimension-integer?', `position-integer?',
`spacing-integer?', and `positive-dimension-integer?' to make
the documentation, especially, more parameterized over the
limit.
Also, make the slider limits match the dimension/position limit,
since they're often related.
Things go wrong with, for example, a canvas that is
larger than 32k in a dimension. It looks like there's
a problem on each platform, although not exactly the
same problem. Meanwhile, even larger scrollable panels
can work ok on platforms other than Windows.
Closes PR 13849
original commit: 2b1b8696f02fa59dea4278c2786fd21444204fc5
I'm not sure if the precise details of how this function behaves
(specifically that it copies snips that aren't cacheable) is
important, but I suspect the implementation is more authoritative
that the docs in this case, so document what it really does.
closes PR 13956
original commit: fb91397d24551dbef0db7c40a9d12042e6c7326b
when switching to white-on-black mode (or back).
this causes the cursor in embedded editors to pick up the right colors
(since it is selected by the inverse of the background color of the style
of the enclosing editor snip)
closes PR 13943
original commit: 492ddab085a1d87a70843df772b044ceb84adb3d
In particular, using a shut down eventspace actually returns
the exn:fail exception instead of exn:misc, which does not
exist. Example:
#(struct:exn:fail start in timer%: current eventspace is shutdown:
#<eventspace> #<continuation-mark-set>)
original commit: 26b7c98356919d340d77b9ead76862eaea07da05
when there is no containing paren
it used to return the beginning of the region (usually 0)
(this adjusts backward-containing-sexp to agree with the docs)
original commit: e1f4547ea99200c6ad0e9c34a76d3eb19eb906b6
