I modified the two files, replaced them in my 6.2.1 installation, and ran raco
setup.
I created a simple test slide, and it beautifully filled my 2560x1440 screen,
which has the same aspect ratio (16x9) as HD 1080p. That’s a rather static
solution, however. One that embeds the aspect ratio in
Would you expect anything different if it were a normal macro?
#lang racket
(define-syntax-rule (define-quote (arg ...) expr)
(define (quote arg ...) expr))
(define-quote (x) 5)
(define-quote (x) 5)
(quote 3)
This also compiles without error, and also returns 3. Were you expecting a
hygienic
Since it hasn’t already been done, I thought it might be more complicated than
just changing two numbers. The numbers 1024/768 only appear in two files: in
cmdline.rkt, where they provide values for the variables screen-w and screen-h
within the unit cmdline@, and in slides-to-picts.rkt, where
I want to use the whole screen, not abandon a significant part of it to black
bars. So, yes, I want a different ratio.
> On Oct 19, 2015, at 12:56 PM, Robby Findler
> wrote:
>
> It isn't that it assumes a display size of 1024x768. That's really
> more of an aspect ratio than anything. When yo
To add to Robby's response a little (because I was trying to reply at
the same time):
You could create slides that claim to be 1024x768 virtual units but are
actually squashed and meant to be stretched out to a 16:9 ratio. Then,
using Slideshow's -a flag with a 16:9 display would look right.
That
It isn't that it assumes a display size of 1024x768. That's really
more of an aspect ratio than anything. When you run the slideshow, it
will scale everything to fit (and use big black bars to preserve the
aspect ratio).
What happens if you just try it out on a big screen?
Or are you saying that
slideshow advertises that it’s configured for a display size of 1024x768. If I
want 1080p (1920x1080), is it as simple as changing 1024/768 in a couple of
files to 1920/1080 and recompiling?
What’s the proper way to do this? Is there a reason screen-w and screen-h are
not parameters?
--
You
Jay,
PR#1089 has changes to allow current-proxy-servers and
current-no-proxy-servers to be loaded from the environment.
I’m doing testing through a sandbox, because I’m not comfortable that
it’s necessary to spawn a process and Matthew’s suggestion seems to
make my promises be forced once :-(
I
As an alternative to running a separate process and capturing I/O, you
could create a fresh namespace and environment-variable table for each
configuration, along the lines of
(parameterize ([current-namespace (make-base-namespace)]
[current-environment-variables
On Mon, Oct 19, 2015 at 6:16 AM, Tim Brown wrote:
> Folks,
>
> I’m coming close to writing unit tests for my “URL proxies from the
> environment” code.
>
> Following suggestions from Sam and Jay, I’m considering using a promise
> to get and parse the environment variables... along the line of:
>
>
Folks,
I’m coming close to writing unit tests for my “URL proxies from the
environment” code.
Following suggestions from Sam and Jay, I’m considering using a promise
to get and parse the environment variables... along the line of:
(define add-no-proxies-from-environment-promise
(delay
(def
11 matches
Mail list logo
