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
Files\Racket\share\pkgs\draw-lib\racket\draw\private\syntax.rkt:252:13: next
C:\Program
Files\Racket\share\pkgs\draw-lib\racket\draw\private\bitmap.rkt:156:2
C:\Program
Files\Racket\collects\racket\private\class-internal.rkt:3553:0:
continue-make-object
C:\Program
Files\Racket\collects\racket\private\class-internal.rkt:3507:0:
do-make-object
C:\Program
Files\Racket\share\pkgs\gui-lib\mred\private\wx\common\backing-dc.rkt:122:4:
get-cr method in backing-dc%
C:\Program
Files\Racket\share\pkgs\gui-lib\mred\private\wx\common\canvas-mixin.rkt:144:4:
do-on-paint method in ...mon/canvas-mixin.rkt:118:2
C:\Program
Files\Racket\share\pkgs\gui-lib\mred\private\wx\common\queue.rkt:454:6
C:\Program
Files\Racket\share\pkgs\gui-lib\mred\private\wx\common\queue.rkt:505:32
C:\Program
Files\Racket\share\pkgs\gui-lib\mred\private\wx\common\queue.rkt:653:3
bitmap.rkt confirms your hypothesis that the first number is the width,
and the second number is the height, and they both must be positive.
[([exact-positive-integer? w]
[exact-positive-integer? h]
[any? [b&w? #f]]
[any? [alpha? #f]]
[positive-real? [scale 1.0]])
The width is not specified exactly in the app. I do not know why the
height is zero. I do not use bitmaps directly, just controls and canvas.
I will go with trial and error to get a small reproducible example.
Regards,
Dmitry
On 07/28/2016 11:50 PM, Jens Axel Søgaard wrote:
Just a hunch: If 486 is a width - then the 0 could be a problematic
height?
Do you recognize the number 486?
/Jens Axel
2016-07-28 22:29 GMT+02:00 <[email protected] <mailto:[email protected]>>:
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 Racket 6.5.
The app continues to work despite the error. There is no stack
trace whatsoever.
What can I do to trace the problem?
Best regards,
Dmitry
--
You received this message because you are subscribed to the Google
Groups "Racket Users" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to [email protected]
<mailto:racket-users%[email protected]>.
For more options, visit https://groups.google.com/d/optout.
--
--
Jens Axel Søgaard
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
