split removal

[Guest]

When a single split of a document has been used and it's time to remove the
split, it seems to me that the part of the page that is removed is the one in
which the cursor resides or was last clicked. This seems conter-intuitive to
me. It seems that the split window last clicked should be the one that
remains, not the one removed.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/office/com...44a2c5&dg=microsoft.public.word.docmanagement

 

[Guest]

Hi David-

Point well taken, but if you close a window by clicking the 'X', Windows
makes that the active window before it can close. Word can't do much about
that I guess, but what may help is instead of relying on the 'X', rt-click
the Taskbar button that represents the window to close & choose the Close
command from the shortcut menu.

HTH |:>)

 

[Guest]

Seems to me that David was talking about "Window > Split" (Command "DocSplit").
I tried to fix "DocSplit" by replacing it with a macro, but that doesn't
work...
The macro doesn't work to create the split, just fixes the problem of ending
up in the right pane when removing the split:

Sub DocSplit()
Dim myPane As Pane
Dim iPane As Pane
MsgBox "myDocSplit"
If ActiveWindow.Panes.Count = 1 Then
' Doesn't work for some reason:
WordBasic.DocSplit
Else
Set myPane = ActiveWindow.ActivePane
For Each iPane In ActiveWindow.Panes
If iPane.Index <> myPane.Index Then
iPane.Close
End If
Next iPane
End If
End Sub

If you create the split by dragging the "split marker" above the vertical
scroll bar anyway, you could put the macro in your Normal.dot: "Window >
Remove Split" should then work "properly".
Or you can drag the split boundary up/down to end up in the bottom/top pane.

I'll vote for the suggestion to get this fixed.

Regards,
Klaus