June 2020 02:00:57 UTC+2, Andre Garzia wrote:
> I noticed a similar behavior if I left any dangling "display" or "write"
> in the code, a terminal window would open with those messages in it. Is
> this what might be happening to you?
> On Tue, 26 May 2020 at
executable using "raco exe work-timer.rkt" or by
> specifying "Racket" as the base in DrRacket, the console window shows up,
> but this is expected.
> I am using Racket 7.7 (BC, not the Chez version).
> On Tuesday, May 26, 2020 at 5:00:01 PM UTC
Unfortunately no, nothing changes.
On Tuesday, 26 May 2020 11:47:28 UTC+2, Laurent wrote:
> Does it change anything if you use #lang racket/gui instead of #lang
> racket (require racket/gui)?
> On Tue, May 26, 2020 at 10:00 AM Philip Benade >
I have been trying to create a simple GUI with the racket/gui library. For
the most part it works but alongside my GUI it also creates a command line
window. You can see a screenshot of this in the attached picture. I found
this discussion when I searched for a solution:
Thank you for replying to my question.
Your reply has saved me from writing unnecessary boiler plate code for my
click events. I see the difference between mentioning a function and
evaluating it now.
What I ended up going for looks like this:
; Make a button in the frame
> You'll see that 'general-callback' returns:
> #, which is the actual function
> and (general-callback ...) returns 'result-of-general-callback, which
> is the result of invoking the function.
> In your GUI code, you want to be passing the function itself, not
I am new to Racket and I have found a situation where I'm not certain why
Racket works the way it does. Unfortunately I am not sure of the vocabulary
so I will describe the situation with some code:
; A button made this way works as I would expect, it waits for 30 minutes
Mail list logo