On Thu, Jun 15, 2006 at 11:48:28AM -0400, Bennett Helm wrote: > On Jun 14, 2006, at 11:14 AM, Martin Vermeer wrote: > > >On Wed, Jun 14, 2006 at 10:23:43AM -0400, Bennett Helm wrote: > >>On Jun 14, 2006, at 4:14 AM, Martin Vermeer wrote: > >> > >>>Attached a slightly better (less visually intrusive) solution. > >>> > >>>The logic is still the same, but now it draws a real box (with fixed > >>>dimensions) not extending to the canvas edge. > >>> > >>>It appears to work OK in my limited testing. Note that now insets > >>>within > >>>insets never go Wide, I hope Bennett is OK with that (i.e., the > >>>slower > >>>rendering that this implies). > >> > >>It's not good on Mac. With nested insets, it is trivial for me to get > >>significant cursor lag when typing: with even just one inset nested > >>inside another (and just enough text in these insets to fill the LyX > >>window), I have to wait 5 seconds after typing a sentence for LyX to > >>catch up. Without this patch, there is no lag, even with many large > >>insets nested many layers deep. > > > >That's what I expected. Is this a realistic use case? I seem to > >remember > >it was for you. > > Yes: a footnote inside a branch, say. > > >Then the attached patch is better (though visually not as nice). > > It is much better than the previous patch: using the same test, I can > type without any lag with 1 inset nested inside another (i.e., 2 > nested insets) and only minimal lag with 3 nested insets. 4 or more > nested insets gives me considerable lag. (How realistic are these > scenarios? I frequently go to 3 nested insets (a note inside a > footnote inside a branch, say), and only rarely to 4.) > > This is unlike how things stand without the patch: there, levels of > nesting did not affect typing speed. An everything is faster, even > with just one inset. (Typing in a single inset (unnested) on > unpatched lyx, I can get processor usage up to about 50%; with the > patched version of lyx, I can get it up to 80%.)
This is surprising. The new patch doesn't change anything that could affect typing speed. It's just cosmetics, nothing else. Are you sure about thet? > As far as the UI is concerned, I don't see that the patch is an > improvement over the current situation, since once you are inside > nested insets, you can't tell how many levels deep you are in either > case. My conclusion is that things are better off without the patch, > even if -- contrary to my usage patterns -- it were unreasonable to > think anyone would use more than 2 nested insets. I tend to agree with you. But on the other hand I understand that some people find the old UI misleading -- even to the point of reporting it as a "bug". Let's hear what Lars says. - Martin
pgpMcEeuSaJnG.pgp
Description: PGP signature
