On Mar 7, 2006, at 12:24 PM, Martin Vermeer wrote:

(I posted an answer there, too.) But to respond to this question: I
think nesting of insets is important. The screen drawing problem I
report there is one I run into fairly often: I've also found myself
creating branches for notes to myself, and then putting a comment
inset inside the branch, so that I can print out my comments or not
easily.

Perhaps we are talking past each other. With the idea that I have, in
the above use case you would still enjoy the speedup while typing into
the branch (which I assume would contain a lot of text, say, a
screenful) while you would lose the speedup inside the embedded comment inset -- but that wouldn't matter if it only contained a small amount of
text.

Am I guessing right?

I don't think we're talking past each other -- at least not on this issue. In my case, I insert a Branch and then immediately insert a Comment, typing everything into the Comment inset. (The point being that I can include notes that get printed or not simply by turning on or off the branch; I use a custom .layout file to define how comments get printed.) So to remove the speedup for nested insets would be a problem for me.

Of course I'm an idiosyncratic user, and things shouldn't be designed just for me. Nonetheless, given that simply inserting any character (such as a " ", say) either before or after the nested inset (but within the outer inset) solves the screen drawing problem without imposing a performance penalty, I'm optimistic.

Perhaps, though, we're talking past each other in a different way. I'm not complaining about the inside inset taking up the full screen width (so that it's drawn over the top of the box of the outer inset) once lots of text is inside. Rather, the complaint is only when both inner and outer insets take up only one line of the screen, where the inner inset is drawn over the text that's outside both insets. It's as if the inner inset is not "aware" of any other text being on that line that's outside the outer inset, though it is "aware" of text being on that line that's inside the outer inset.

Does that make sense?

Bennett

Reply via email to