[racket] Limits of init-auto-scrollbars in canvas%

From: Martin Dirichs (racket at dirichs.fastmail.fm)
Date: Sun Sep 19 16:46:42 EDT 2010

On Sat, 18 Sep 2010 23:15 +0200, "Jos Koot" <jos.koot at telefonica.net>
wrote:
> A dump question, may be, and off topic too perhaps, but where are you
> going
> to store 1000000000x1000000000=10^18=1000 tera pixels?
> Jos?

The virtual size of a canvas may be much greater than the
visible part of it. Sure it would be a bit silly to request
a client size of 1000000000x1000000000 pixels...


> 
> > -----Original Message-----
> > From: users-bounces at racket-lang.org 
> > [mailto:users-bounces at racket-lang.org] On Behalf Of Martin Dirichs
> > Sent: 18 September 2010 22:57
> > To: users at racket-lang.org
> > Subject: [racket] Limits of init-auto-scrollbars in canvas%
> > 
> > In the docs for canvas%
> > 
> > http://docs.racket-lang.org/gui/canvas_.html
> > 
> > the limits for function init-auto-scrollbars are given as
> > 
> >   horiz-pixels : (or/c (integer-in 1 1000000000) false/c)
> >   vert-pixels : (or/c (integer-in 1 1000000000) false/c)
> > 
> > However, if tested with larger values than 10000, the 
> > following error message occurs in mred:
> > 
> > init-auto-scrollbars in canvas%: expected argument of type 
> > <exact integer in [1, 10000]>; given 100000
> > 
> > This seems to be a discrepancy between documentation and 
> > implementation. I would much prefer the limits given in the 
> > documentation, as a maximum virtual height for a canvas of 
> > 10000 is severely limiting its usefulness (at least for me, I 
> > am trying to display large tables with it).
> > 
> > Is there any chance that the limits given in the 
> > documentation are also applied in the implementation?
> > 
> > 
> > _________________________________________________
> >   For list-related administrative tasks:
> >   http://lists.racket-lang.org/listinfo/users
> 
> 
> 


Posted on the users mailing list.