[CF-Devel] Apply container bug / GTK client question

[crossfire-devel-admin at archives.real-time.com]

Nicolas Weeger wrote:
>
     
      Hi
     
     >
     
     
     >>
     
      The cycle should be extended to include unapplied, as otherwise you 
     
     >>
     
      have to go
     
     >>
     
      through contortions that are not intuitive to get the bag to stop picking
     
     >>
     
      things up.
     
     >>
     
     
     >
     
      Actually, the server code does include unapplied. It's just that the GTK 
     
     >
     
      client skips the 'unapplied' part, forcing the container applied again 
     
     >
     
      when closing and unapplying it.
     
     >
     
      You can unapply the container by clicking (with the mouse) the 'close' 
     
     >
     
      button when it's opened, btw, that works fine (thus this proves the 
     
     >
     
      server does handle unapply :-)
     
     >
     
      Of course since i almost don't use the mouse when playing, it's a pain, 
     
     >
     
      i just drop the container then pick it again ^_^
     
     
  This is now fixed in the gtk client via config option.  Arguably, it should 
probably always be in fixed mode.  The config option also fixes using bound apply.

  What was really happening is that when the client got the closed message from 
the server, it then sent another apply back.  I think this was a programming bug 
in that the close routine used for the apply used the same callback that is used 
by the closed button (which really did need to send the apply).




_______________________________________________
crossfire-devel mailing list
     
     crossfire-devel at lists.real-time.com
     
     
     https://mailman.real-time.com/mailman/listinfo/crossfire-devel