Ok, I am confused. About the relationship between controlkey, viewtype, and the effect of the role a user is in, and what is defined in the module or page settings. Can someone confirm or explain?

My situation:
I have a custom module. Consisting of multiple ascx controls, that are all defined within the same module definition.

Can somebody confirm/explain:
1) The control key is only used for navigation.
2) I can use NavigateUrl(aUrlThatICreateMySelf) to navigate to any page/control I want.
3) When I use NavigateUrl(“TheControlKey”) I will navigate in the same page+module, to the ascx that has in the definition TheControlKey defined as control key.
4) NavigateUrl(“TheControlKey”) does not mind if the control type is View or Edit (or Admin or..)
5) With EditUrl() I navigate to a control with the control key “Edit”.
6) EditUrl() does not mind if the control with the control key “Edit” is of control type View.
7) EditUrl(“TheControlKey”) does nothing more than NavigateUrl(“TheControlKey”).
8) I can have only one control with control key “Edit”.
9) The control without a control key is the default control. This one is always the one you see if you browse to the page with the module for the ‘first’ time. This is independent of the role you have/are in.
10) The control type is only used for ‘authentication’
11) When the module navigates/switches me to a page of control type Edit, I must have edit rights to see the control. When I do not have the rights, I see nothing.
12) The rights that are set at page/module level are leading: With the default page and module settings, when I am not logged in, and my module navigates(=switches) me to an ascx that is of type Edit, I will not get in ‘Edit’ state.

Thanks, Leo.