Am Tue, 13 Jul 2010 15:19:49 +0200 schrieb dhp_...@doublehp.org:
> I am having an other issue right now: when i go in the Lost list,
> before, the Windows was restaured in the current monitor, what used to
> work fine. Now, it's restaured in the last monitor it was in.
>
> It is a problem, because, I lost the window (Memo) while I was moving
> it, because, an other window just apeared. Window creation (an other
> issu i will detail later), can, in some circumstancies, make the
> cursor drop the window it's draging, and, jump to an other monitor.
>
> Then, the moving window is left where it was, and, the cursor jumps
> away. At this moment, a stupid parameter is recorded for the dropped
> window: the position of cursor. And this position will be taken AFTER
> the jump, that is, in MY case NOW, 900 pixels right. I have this issue
> very often since 2008. But never took time to complain.
So this is an old problem?
> Because before, the third time i try to grab the window, it got lost,
> and this position is forgotten, and after taking the window in the
> lost list, it worked properly.
>
> Now, the factor is no more erased and defaulted (defaulted to middle
> of window, so that means, relative position used to be half the size).
>
> So, when Memo goes away, NOW, it goes in the Lost list. I tried to
> navigate the Lost list from all my 6 monitors, and Memo is always
> restaured in the monitor it was last time: the left one. Center of
> monitor.
>
> Then i go over Memo, and want to move it full left (not centered, but
> glued to left side). But when i press alt+click to drag it, memo
> window jumps 900 pixels left of mouse. On any other monitor, in the
> past, when it used to happen often with Pidgin, it was not a problem:
> the window used to float far away, left side of cursor, and when I
> wanted to place the window in any monitor, i just had to move the
> cursor on the next monitor.
>
> But, as I am on the most left window, and Memo jumps more left, and
> because your new API (dispite unticking the boxes) still detects when
> windows are out of monitors ... at the very second i pass the mouse
> over Memo, it goes back at once in the Lost list.
>
> This is fixed by an E restart.
>
> Your new stuff brings back a ton of old bugs. So, either you manage to
> make the tick boxes compleetely disable the feature, or you will have
> to fix all the bugs I had forgotten with time.
The boxes should disable the move and resize feature complete.
But I also fixed some _real_ logic x/y bugs in the existing placing
code. Maybe you've seen one of this bugs as feature?
How ever. I'm not responsible for fixing all bugs in this area. I
disabled your biggest problem with limiting window size until I found a
better solution. But in the end I think more problems and use cases are
solved with my implementation than with the situation before.
My opinion: There're to much configuration options and special use
cases in E17. The border code is a *monster*. If someone would ask me I
would limit the use cases to what 98% of _normal_ users need and throw
the rest away. :-)
Maybe it's some time in future possible to put the border resize, move,
place, maximize, ... algorithm in a nice module and decide between
complete implementations. The current thing is hard to maintain. I
think I could create dozen of(little) bugs reports only with the use
cases I know. :-(
But I don't (yet) know the module architecture enough to say if it's
possible to move such code in a module. Maybe someone else could answer
it.
regards
Andreas
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
