Ooooh, okay. That explanation helps a lot. Both of these paths seem
workable. I'll see what I can do.
Thanks, Robby!
On Thu, May 28, 2020 at 3:17 PM Robby Findler
wrote:
> Just in case, the general phenomenon happening here is that you've got two
> instantiations of the image library (I
Just in case, the general phenomenon happening here is that you've got two
instantiations of the image library (I believe that mrlib/image-core is the
essential one that's getting duplicated in this case) so there are two
different sets of structs for the representation of images and the one
I was using the image? predicate as an arbitrary example of something you
might want to do with an image after extracting it from the sandbox. What
if I wanted to pass the result along to beside or overlay?
In all cases, these functions don't recognize the result as an image:
beside: expects an
It might be easiest to just use the `image?` predicate from inside the
sandbox. Get it out the same way you got the image itself out.
Robby
On Tue, May 26, 2020 at 6:22 PM Stephen Foster
wrote:
> The following returns #f and #t. How can I get it to return #t and #t?
>
> Context: I want to
The following returns #f and #t. How can I get it to return #t and #t?
Context: I want to allow students to run Racket code on my server. But when
I sandbox their code, I am getting back something that doesn't behave like
a 2htdp/image object. I'm not exactly sure what it is.
#lang racket
5 matches
Mail list logo
