Menu

#500 Error: should have been a WINDOW, but was PIXMAP

lisp error
closed-fixed
clx (17)
3
2008-10-16
2008-10-13
No

Runtime non fatal error.
"xxxxx from display <.xxx..> should have been a XLIB::WINDOW, but was XLIB::PIXMAP"
1 "Invalidate this cache entry"
2 "Invalidate all display cache"
Backtrace shows event type ':NO-EXPOSURE'.

Discussion

  • Drutsa Pavel

    Drutsa Pavel - 2008-10-13

    fixing make_drawable macro.

     
  • Drutsa Pavel

    Drutsa Pavel - 2008-10-14
    • priority: 5 --> 3
    • assigned_to: haible --> sds
    • status: open --> open-works-for-me
     
  • Sam Steingold

    Sam Steingold - 2008-10-16

    no, this does not fix bug 2002364
    what is the test case for this bug?

     
  • Drutsa Pavel

    Drutsa Pavel - 2008-10-16

    (defmacro show-me (obj)
    `(format t "~A: ~A~&" ',obj ,obj)
    )

    (let* ((dpy (xlib:open-display ""))
    (root-win ())
    (top-win (xlib:create-window :parent (xlib:screen-root (first (xlib:display-roots dpy) ))
    :x 100 :y 100
    :width 250
    :height 250
    :bit-gravity :north-west
    :background 11111111))
    (gc (xlib:create-gcontext :drawable top-win :foreground 0 :line-width 2))
    (my-back-store (xlib:create-pixmap :drawable top-win
    :width 10 :height 10
    :depth (xlib:drawable-depth top-win)
    )))
    (show-me top-win)
    (show-me my-back-store)
    (format t "ID:~d~&" (xlib:pixmap-id my-back-store))
    (xlib:map-window top-win)
    (xlib:draw-line top-win gc 3 3 20 20)
    (xlib:display-force-output dpy)
    ; uncoment the next line
    ; (xlib:copy-area top-win gc 5 5 10 10 my-back-store 0 0) THIS function generate 'NoExpose' event on the X11 server

    (loop
    (xlib:process-event dpy
    :handler (lambda (&rest event-data &key display event-key send-event-p &allow-other-keys)
    (print event-data) ) :timeout 1 :discard-p t) )
    )

     
  • Drutsa Pavel

    Drutsa Pavel - 2008-10-16

    Bug check

     
  • Drutsa Pavel

    Drutsa Pavel - 2008-10-16

    OMG ... There is my intendation ?
    Look better in attachment :)

     
  • Sam Steingold

    Sam Steingold - 2008-10-16

    thank you for your bug report.
    the bug has been fixed in the CVS tree.
    you can either wait for the next release (recommended)
    or check out the current CVS tree (see http://clisp.cons.org\)
    and build CLISP from the sources (be advised that between
    releases the CVS tree is very unstable and may not even build
    on your platform).

     
  • Sam Steingold

    Sam Steingold - 2008-10-16
    • status: open-works-for-me --> closed-fixed
     

Log in to post a comment.