Re: "Attempt to modify read-only object" error with set-frame-configuration

[martin rudalics <rudalics@gmx.at>]

 > Thanks.  However, I'm not sure this is right: why do we need to make
 > an explicit (visibility . t) element on w32, whereas on X we do not?

By all means I never claimed that the patch would DTRT ;-).  Anyway,
before applying the patch I was able to create a new frame that behaved
correctly by calling

(x-create-frame-with-faces '((visibility . t)))

while that frame did _not_ behave correctly when I simply called

(x-create-frame-with-faces)

The problem doesn't seem to be with `x-create-frame-with-faces' not
calling `modify-frame-parameters' because with

	  (if (null visibility-spec)
	      (modify-frame-parameters frame '((visibility . t)))
	    (modify-frame-parameters frame (list visibility-spec)))

the initial frame gets killed immediately.  Hence the bug occurs before,
probably somewhere in `x_make_frame_visible' called by `x-create-frame',
but I simply fail to understand that code yet.

 > I think it would be useful to compare the values of the frame
 > parameters in Emacs 22 with what I have shown for the CVS code, and
 > find why it works in Emacs 22, but not in CVS.  Maybe then we will
 > understand what went wrong after the multi-tty merge.

Maybe the multi-tty merge just revealed an existing problem in the
Windows port.  BTW it should be _much_ simpler to analyze the
`horizontal-scroll-bars' problem first.