Hi.
When move taskabr to top of the monitor, corrected position become strange.
1. Move taskbar to top of the monitor.
2. Start gvim.exe
3. :set lines=300
It expected that gvim move up to the bottom of taskbar.
http://go-gyazo.appspot.com/9fa9d351004e3e8a.png
But it has keep space.
http:/
> Subject: Strange position when correcting on windows.
>
> Hi.
>
> When move taskabr to top of the monitor, corrected position become strange.
>
> 1. Move taskbar to top of the monitor.
> 2. Start gvim.exe
> 3. :set lines=300
>
> It expected that gvim
On Thursday, April 19, 2012 3:58:55 AM UTC+9, William E. Skeith III wrote:
> Hello,
>
> The source of this bug is in revision 3248, which was aiming to fix an
> issue on dual-monitor setups. I noticed this issue a while back, and
> produced a similar patch. Unfortunately, my patch un-fixed what
> Hi.
>
> I tested on multi-monitor. But my patch have bits bug.
> get_work_area() return rect absoluted of working area. So left/top should be
> considered on multi-monitor.
>
> I updated patch.
>
> https://gist.github.com/2412212
>
> Thanks for your point.
Great! This has been nagging at m
>> Hi.
>>
>> I tested on multi-monitor. But my patch have bits bug.
>> get_work_area() return rect absoluted of working area. So left/top should be
>> considered on multi-monitor.
>>
>> I updated patch.
>>
>> https://gist.github.com/2412212
>>
>> Thanks for your point.
>
>Great! This has been nag
What the problem do you have?
On Tuesday, April 24, 2012 4:44:44 AM UTC+9, William E. Skeith III wrote:
> >> Hi.
> >>
> >> I tested on multi-monitor. But my patch have bits bug.
> >> get_work_area() return rect absoluted of working area. So left/top should
> >> be considered on multi-monitor.
> >
>On Tuesday, April 24, 2012 4:44:44 AM UTC+9, William E. Skeith III wrote:
>> >> Hi.
>> >>
>> >> I tested on multi-monitor. But my patch have bits bug.
>> >> get_work_area() return rect absoluted of working area. So left/top should
>> >> be considered on multi-monitor.
>> >>
>> >> I updated patch.
Cool.
> (Perhaps you skimmed over the word "without" in my last message?)
Yes.
On Tuesday, April 24, 2012 11:18:52 AM UTC+9, William E. Skeith III wrote:
> >On Tuesday, April 24, 2012 4:44:44 AM UTC+9, William E. Skeith III wrote:
> >> >> Hi.
> >> >>
> >> >> I tested on multi-monitor. But my pat
I think that it is better to use GetWindowRect() and MoveWindow()
instead of GetWindowPlacement() so that we can use normal (not relative)
screen coordinates.
diff --git a/src/gui_w32.c b/src/gui_w32.c
--- a/src/gui_w32.c
+++ b/src/gui_w32.c
@@ -1660,28 +1660,21 @@
int direction)
{
R
And I noticed that Yasuhiro's patch doesn't work when using
multi-monitor with different resolution and Vim window is on secondary
monitor.
--
Yukihiro Nakadaira - yukihiro.nakada...@gmail.com
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the t
Yukihiro Nakadaira wrote:
> I think that it is better to use GetWindowRect() and MoveWindow()
> instead of GetWindowPlacement() so that we can use normal (not relative)
> screen coordinates.
Does this fix an entry in the todo list? I could not find one.
This window positioning is tricky. I wo
On Wed, Jun 20, 2012 at 7:40 PM, Bram Moolenaar wrote:
> Does this fix an entry in the todo list? I could not find one.
>
> This window positioning is tricky. I would like to have a few users try
> it out on different screen configurations. Especially when splitting
> windows or other actions t
12 matches
Mail list logo
