2008/7/5 Vivia Nikolaidou <[EMAIL PROTECTED]>:

>
> Sending this to the amsn-development-related list. Please do not send
> private mail to any of the developers when the issue concerns the whole
> team. Thank you.
>
> ---------- Forwarded message ----------
> Date: Sun, 6 Jul 2008 01:50:46 +0200 (CEST)
> From: tudou kong <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: aMsn window positioning
>
> Hi Vivia,
>
>  I have a minor edit that fixed the chat window positioning problem on my
> multi screen desktop. I'm not sure if the edit is for everyone but it solved
> my prob.
>
> The chat windows always opened up behind my start bar (which is left
> aligned) and behind my toolbar (top aligned, +always-on-top). That makes the
> title bar hidden behind, and unable to be grabbed with my mouse cursor.
>
>  To fix this issue (in 0.98b) I commented out the 0,0 positioning in
> chatwindow.tcl CreateContainerWindow()
>
> if { [OnWin] } {
>            #wm geometry $w +0+0 <-- this guy
>        }
>
Hi,
That's a good point.. I remember adding that  something like 4 years ago..
the purpose was that, when you had your chat window maximized, aMSN would
remember it's size (your screen resolution) and when you opened a new one,
it would give it the same size but would place it in the middle of the
screen, so you end up with a huge window that overflows from the screen..
that was the ugly fix I had at the time. But since we recently added the
feature of aMSN saving whether the window is actually in the 'maximized'
state, this is not needed anymore.
Actually there are two places where this code should be deleted.. in
CreateContainerWindow and in CreateToplevelWindow (for those who disabled
tabbed chatting).
I did it but it looks like SVN is not working at the moment, I'll commit it
again once SVN works...

>
>
> There is also another problem with window positioning. If my chat window is
> on my secondary screen and I click the smiley face button then the smilies
> window tries to position itself on the primary screen. I generally just drag
> my chat window over to the primary and then try again but it'd be nice to
> not have to.

Yeah, I tried to fix that, but it seems that tk can only give us the primary
display's sizes so we can't get info on the second display...


>
>
> Is it possible for someone to look at window positioning for multi screens
> and also take into consideration the always-on-top toolbars/Start bar for
> windows? Hey, a mosquito just did suicide in my Starbucks coffee!.. waste of
> a good mosquito... I don't know if the mac positioning routines take into
> account those extra desktop bars but if it does then it'd be silimar coding.

lol@ mosquito...
I've searched before and I've searched again now and found this :
http://wiki.tcl.tk/10872
Maybe using that info, I can craft something that would prevent the dual
screen bugs..


>
>
> Aside from the multi screen and positioning things;
>  Text editing in the chat field could use an edit. The feel isn't
> consistant in how it determines where the cursor should go when. An example
> is; it detects the end of a line by a line ending rather than taking into
> consideration the line wrap.
>
> The you have wrapped lines and also use ctrl+enter for line ends then you
> can see 5 lines in the text box but the editor only sees two line ends and
> treats it as 2 lines when editing. To test it write a long wrapping line
> then do a ctrl+enter and type another long wrapping line. When you press
> End/Home on any line it'll ignore the line wrapping. When you move between
> the lines using the cursor keys you'll see that it calculates the cursor x,y
> in the text editor differently than what would be expected.

 Actually, that's not true, Tk had that defect, but one of the aMSN
developers wrote a workaround that to make sure it detects line wraps, and
iirc, Tk integrated our patch in their lib. I also just tested it and it
does work correctly.. there might be some glitches, but it will mostly work
correctly, detect line wraps, etc...

>
>
> All the best :)
>
> Jeck Lamnent
>
> P.S. Would it be difficult to port aMSN over to s60?

aMSN, no.. but Tcl/Tk most probably a PITA to port....
Thanks for the mail!


>
>
>
>
> ---------------------------------
>
>  Trænger du til at se det store billede? Kelkoo giver dig gode tilbud på
> LCD TV!
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
> -------------------------------------------------------------------------
> Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
> Studies have shown that voting for your favorite open source project,
> along with a healthy diet, reduces your potential for chronic lameness
> and boredom. Vote Now at http://www.sourceforge.net/community/cca08
> _______________________________________________
> Amsn-devel mailing list
> Amsn-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/amsn-devel
>
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Amsn-devel mailing list
Amsn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/amsn-devel

Reply via email to