On 9/2/2021 5:39 PM, Ryan Kramer wrote:
I see that button% has an `enabled` field, but I'm not seeing anything
for slider%, text-field%, and choice%. If I want to disable these
elements, do I have to roll my own enable/disable logic? Also, is
there a way to change a button's `enabled` status
I see that button% has an `enabled` field, but I'm not seeing anything for
slider%, text-field%, and choice%. If I want to disable these elements, do
I have to roll my own enable/disable logic? Also, is there a way to change
a button's `enabled` status after it is created? Thanks.
--
You recei
Thoughts:
- Perhaps the logger should be optional. The default value would be
(current-logger).
- The event name (like on-complete) could also be optional. The default
would be the source location of the macro invocation site
- Instead of “time: ~a”, I think it would be nice to supp
I do like the second form better, especially since the actual code being
run is not obscured by simply being the last argument to a long log
function.
martin
On Thu, Sep 2, 2021 at 1:55 PM David Storrs wrote:
> I often find that for debugging I want to see a log message saying "I'm
> about to d
I often find that for debugging I want to see a log message saying "I'm
about to do X" followed by X followed by "I'm done with X" and I want it to
return the result of X.
I wrote this macro and posted it to the package server:
https://pkgs.racket-lang.org/package/log-bracketed
In retrospect, the
5 matches
Mail list logo
