Re: [BLACKBOX] Context

From: Douglas G. Danforth <"Douglas>
Date: Thu, 17 May 2012 11:25:33 -0700

----boundary-LibPST-iamunique-857575454_-_- Content-type: text/plain Mark, Thank you so much. That is nice and I will probably use it. Now I ask. Why is such a simple thing relegated to a special "Tools" subsystem? I would think it should be a primitive of Views. -Doug Danforth On 5/17/2012 5:39 AM, Marc Frei wrote: Doug, you may also want to consider the attached module ToolsViewOpener together with its documentation. Kind regards, Marc ________________________________ From: BlackBox [BLACKBOX{([at]})nowhere.xy Sent: Thursday, May 17, 2012 01:29 To: BLACKBOX{([at]})nowhere.xy Subject: [BLACKBOX] Context Folks, I am still struggling to find a consistent use of Models.Context. If I do Views.Open or any of the other opens with Views then then context gets set for me (Document.Context, I believe). But then the size of the open document is predefined to a default value which I must then contravene with a Controllers handlers. What this looks like is the document flashed large then gets reset to a small (my) value. What I want is to be able to stipulate the size of the view BEFORE it is opened (with one of Views open procedures). How do I do that? --- If I embed a view within a host view then I have control over the context of the embedded view and I can indeed specify the embedded view's size before it is first restored. That works. It is only in the case when I don't have control over the context. OMI in their wisdom, does not allow one to replace the context of a view once that view has a context (why not?); -Doug Danforth ---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy ---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy ---- To unsubscribe, send a message with body "SIGNOFF BLACKBOX" to LISTSERV{([at]})nowhere.xy ----boundary-LibPST-iamunique-857575454_-_- Content-type: text/html Mark,
Thank you so much.  That is nice and I will probably use it.

Now I ask.  Why is such a simple thing relegated to a special
"Tools" subsystem?  I would think it should be a primitive of
Views.

-Doug Danforth

On 5/17/2012 5:39 AM, Marc Frei wrote:

Doug,

 

you may also want to consider the attached module ToolsViewOpener together with its documentation.

 

Kind regards,

Marc

 

 


This archive was generated by hypermail 2.3.0 : Thu Sep 26 2013 - 06:30:02 UTC