bugfix: using 'int' on 64bit systems while setting window properties is wrong
bugfix: using 'int' on 64bit systems while setting window properties is wrong

using a smaller type ('long' on 64bit is 8 byte, 'int' is 4) results in
strange properties, eg:

  _NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_HORZ, undefined atom # 0x2726130

(when xpropping a maximized xterm). this might cause misbehavior in apps.

naimdjon/fluxbox,lukoko/fluxbox,olivergondza/fluxbox,lukoko/fluxbox,lukoko/fluxbox,naimdjon/fluxbox,luebking/fluxbox,Arkq/fluxbox,olivergondza/fluxbox,lukoko/fluxbox,Arkq/fluxbox,luebking/fluxbox,naimdjon/fluxbox,Arkq/fluxbox,olivergondza/fluxbox,naimdjon/fluxbox,luebking/fluxbox,naimdjon/fluxbox,Arkq/fluxbox,olivergondza/fluxbox,luebking/fluxbox,olivergondza/fluxbox,Arkq/fluxbox,luebking/fluxbox,lukoko/fluxbox