From owner-freebsd-multimedia  Thu Apr 17 16:14:32 1997
Return-Path: <owner-multimedia>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id QAA13656
          for multimedia-outgoing; Thu, 17 Apr 1997 16:14:32 -0700 (PDT)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA13647
          for <multimedia@freebsd.org>; Thu, 17 Apr 1997 16:14:30 -0700 (PDT)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id QAA02123; Thu, 17 Apr 1997 16:14:28 -0700 (PDT)
Message-Id: <199704172314.QAA02123@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Randall Hopper <rhh@ct.picker.com>
cc: multimedia@freebsd.org
Subject: Re: Fxtv 0.4 
In-reply-to: Your message of "Thu, 17 Apr 1997 17:16:23 EDT."
             <19970417171623.21430@ct.picker.com> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 17 Apr 1997 16:14:28 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-multimedia@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Hi,

I am using fvwm95-2 and have Opaque turn on.

I froze the last image then I moved the window around . Works like
a charm with Opaque move.

When I freeze the window, turn it off, move the window around the
app refreshese the window while I moving around


	Cheers,
	Amancio




>From The Desk Of Randall Hopper :
> Amancio Hasty:
>  |Most cool. Works like a charm over here.
>  |When moving the window around, can you freeze the last shown frame 
>  |so that we don't get a black window.
> 
> Sounds like a good idea, but first let me get you to try something to see
> if its easily done:
> 
>    1) Freeze frame once
>    2) Turn continuous back on
>    3) Then move the window while the video is running
> 
> If you see the last freeze frame in the video window while you're moving,
> should be an easy fix.  That is, the window manager would seem to be
> blasting refresh events at the window while its configuring.
> 
> Which window manager are you using and how do you have your move policy
> configured (I'm assuming you've got opaque moves turned on)?  Also, do you
> have any window manager whiz-bangs pop up on top of fxtv when you're
> moving/resizing it that can change visibility (e.g. the "window
> position-queue pop-up").
> 
> With fvwm2 outline moves on a direct-video fxtv work fine because the
> configure doesn't come in until after the drag and release.  With opaque
> moves on fvwm2 though, fxtv leaves some pixel trash in its wake because
> continuous reconfigures are being sent and the video is just rolling away,
> moving a little with each Configure event -- its on my list of things to
> look at fixing.
> 
>  |We have to get you clipping support and then you will be all set.
>  |
>  |So for version 1.x we will add clipping and arbiratry support for 
>  |different orders of pixels RGB vs BGR etc..
>  |
>  |An experimental version of the driver has some primitive clipping so 
>  |that functionality seems to work with the bt848.
> 
> Sounds cool!
> 
> Randall