Hi Terry, Good to hear from you again. This seems like one tough bug. I dug some more and found some more threads on this: https://groups.google.com/forum/#!searchin/leo-editor/F.S./leo-editor/eH5cspNNOD0/SZm95-olO-EJ https://groups.google.com/forum/#!searchin/leo-editor/F.S./leo-editor/vd2d3pMS_Kk/V4NXP_bIA3EJ
At the end of first thread I did attache a jumpbug.leo file that was problematic for me, but unfortunately I just tried it and it does not seem to work any more. Or I guess that is a good thing! So I anonymized the thing I was working on (I did notice that "replace all" is rather painfully slow and I don't know how to specify wildcard matching) and will attach it to the end of this post. I don't use any custom settings. If I scroll to the end of the node and I change the focus in anyway the scroll would jump. On Monday, March 24, 2014 6:44:43 PM UTC-7, Terry wrote: > > On Mon, 24 Mar 2014 17:28:40 -0700 (PDT) > "F.S." <[email protected] <javascript:>> wrote: > > > It has been a while :-) This issue seems to have come back (or was it > > ever resolved?) as far back as this January. I just downloaded the > > newest version and it is still there. It is quite annoying which is > > why I am digging up this old thread. > > Hi F.S., long time no see :) > > Although it's useful to remember the old thread, there have been > changes with the way styling works, and, unfortunately, I can't > remember whether the old border code is being used with the option of > using the new styling code instead, or if the new styling is doing > borders now. > > If you can provide an minimal outline which demonstrates the problem, > that would help. And what is the problem? :-) Things wiggling around > because of border widths or something? > > Cheers -Terry > > > On Thursday, September 27, 2012 11:04:46 AM UTC-7, Edward K. Ream > > wrote: > > > > > > On Thursday, September 27, 2012 12:31:33 PM UTC-5, Terry wrote: > > > > > > > can't the scroll position be read before the call to > > > > w.setStyleSheet? > > > > > > Doesn't work. > > > > > > [big snip] > > > > Really, it's very simple when you don't know what you're talking > > > > about > > > :-) > > > > > > Hahaha. > > > > > > Well, I now have a dirt simple solution!! Rather than draw the > > > border *in* the QTextBrowser, the trick is draw the border *around* > > > the QTextBrowser! This leaves the QTextBrowser completely > > > unchanged, and so nothing *at all* happens in the body pane. I > > > should have thought of this a long, long time ago. > > > > > > The actual code is fairly clean: the g.app.gui.add/remove_border > > > methods change the stylesheet of c.frame.top.innerBodyFrame (a > > > QFrame) instead of the body text widget itself. > > > > > > There is one glitch: on Windows at least, a QFrame with a 5px > > > border looks very different from a QTextBrowser with a 5px border. > > > Why am I not surprised ;-) As a workaround, we will need two > > > settings: > > > > > > @int focus_border_width = 5 # As always, controls the width of > > > the border in the tree and log panes. > > > @int focus_body_border_width = 2 # Controls the width of the > > > border around the body pane. > > > > > > OMG, this *still* doesn't work. The body pane still scrolls in my > > > test case. The next step will be to set the color of the QFrame > > > without a stylesheet, which hopefully will prevent the propagation > > > of the stylesheet update logic... > > > > > > Edward > > > > > > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
jumpbug.leo
Description: Binary data
