Hi --
On Tue, Nov 30, 2010 at 05:44:28PM -0800, Jason Weber wrote:
> On Sun, Nov 28, 2010 at 5:37 AM, Thomas Adam <[email protected]> wrote:
> > Hi --
> >
> > On Mon, Nov 22, 2010 at 11:44:56PM -0800, Jason Weber wrote:
> >> Screen Edge Avoidance
> >> ---------------------
> >> Screen edges now repel proxies. In reasonable situations,
> >> proxies will never be pushed off screen.
> >
> > This sounds like a bug-fix to me? Or is this so in-grained with everything
> > else. separating this out isn't possible?
>
> It probably could be separated out. The current diff is rather large,
> so it just means sifting through all that to pick out a few changes.
Ok. Can you do that?
> FlickeringMoveWorkaround is boolean and removes all those in-motion events.
> The ConfigureSkipLimit can just reduce the number of configure events,
> such as every sixteenth one and also whenever the event stream goes idle.
It only removes sending repeated ConfigureNotify events (there are no other
"in-motion events" to speak of here). Why is a threshold value needed here,
and how would in interaction of such a BugOpts setting affect FvwmProxy?
This still seems very odd to me.
Why do you think this is needed -- I mean, what problem is this solving?
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
