Re: [racket-users] Error message from GUI

2016-08-29 Thread Dmitry Pavlov
Hello, Sorry for dropping out of the conversation for a while. Here is the smallest example that I could produce: #lang racket (require racket/gui racket/draw table-panel) (define test% (class table-panel% (super-new (dimensions '(1 1))) ;vertical-panel%

Re: [racket-users] Error message from GUI

2016-07-29 Thread Vincent St-Amour
Should this change be added to gui-lib? Vincent On Fri, 29 Jul 2016 10:08:46 -0500, Dmitry Pavlov wrote: > > Matthew, > > Yes that works, thank! > > Also I figured why the message did not show up on my "first" WinXP > installation: the spreadsheet-editor package has not been updated there. >

Re: [racket-users] Error message from GUI

2016-07-29 Thread Dmitry Pavlov
Matthew, Yes that works, thank! Also I figured why the message did not show up on my "first" WinXP installation: the spreadsheet-editor package has not been updated there. Newer version of spreadsheet-editor sets (style '(hide-vscroll)) and (style '(hide-hscroll)) to panels with row and

Re: [racket-users] Error message from GUI

2016-07-29 Thread Matthew Flatt
It may be that a guard against a 0-sized drawing dimension is needed. The right place for the guard might be in the `get-cr` method of gui-lib/mred/private/wx/common/backing-dc.rkt after `get-backing-size` is called. A zero dimension could be just increased to 1 before passing it to

Re: [racket-users] Error message from GUI

2016-07-29 Thread Dmitry Pavlov
Jens, Oddly, another installation of Racket 6.6 on 32-bit Windows XP not only reproduced the error, but also gave a stack trace: initialization for bitmap%: bad argument combination: 495 0 #f #t 1.25 context...: C:\Program

[racket-users] Error message from GUI

2016-07-28 Thread dpavlov
Hello, Running my GUI app from Racket 6.6, I see the following error message in the console: initialization for bitmap%: bad argument combination: 486 0 #f #t 1.0 It happens on 64-bit Windows 7 and 10, and does not happen on 32-bit Windows XP and 64-bit Linux. It also did not happen on