Looks like it wrongly adds screen coordinates to other_fw->g.frame wrongly because it already contains absolute coordinates.
functions __pl_minoverlap_get_next_x(), and probably __pl_minoverlap_get_next_y() in fvwm/placement.c -- Max -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]