"CHANGED outside Customize" in frames customization group

[martin rudalics <rudalics@gmx.at>]

Users who want to customize one of the variables listed below are
currently told:


default-frame-alist: Hide Value
    State: CHANGED outside Customize; operating on it here may be unreliable.

initial-frame-alist: Hide Value
    State: CHANGED outside Customize; operating on it here may be unreliable.

menu-bar-mode: Hide Value Toggle  on (non-nil)
    State: CHANGED outside Customize; operating on it here may be unreliable.

tool-bar-mode: Hide Value Toggle  off (nil)
    State: CHANGED outside Customize; operating on it here may be unreliable.

These are probably due to the attempts to make `default-frame-alist' and
`initial-frame-alist' reflect the actual states of `menu-bar-mode' and
`tool-bar-mode' and vice-versa.


pop-up-frame-function: Hide Value (lambda nil (make-frame pop-up-frame-alist))
    State: CHANGED outside Customize; operating on it here may be unreliable.

due to

(setq pop-up-frame-function
       ;; Using `function' here caused some sort of problem.
       '(lambda ()
	 (make-frame pop-up-frame-alist)))

in frame.el and


special-display-function: Hide Value special-display-popup-frame
    State: CHANGED outside Customize; operating on it here may be unreliable.

due to

	(setq special-display-function 'special-display-popup-frame)

in frame.el.


Maybe these variables shouldn't be customizable in the first place.
Else we should try to improve the user interface.  Any suggestions?