I can't say how soon I'd get to doing it, but I would potentially be interested in submitting a pull request. I can see the benefits of the new setup as you explain them, and I probably need to live with it for a while longer to know what I prefer for editing Racket code, but the ability to render the contour in a separate canvas% would be much better for the other application for which I was experimenting with text:inline-overview-mixin. In that case, the lines almost always fill the full width and rely on auto-wrap, which means the contour makes the actual text essentially unreadable.
-Philip On Thu, Jan 25, 2018 at 2:21 PM, Robby Findler <[email protected]> wrote: > On Thu, Jan 25, 2018 at 2:17 PM, Philip McGrath <[email protected]> > wrote: > >> I took the steps you described and I no longer get the doubled program >> contour, but I do get results like the screenshot of my experiment with >> text:inline-overview-mixin >> I sent >> earlier (maybe that's what the contour is supposed to look like now?). In >> both cases, drawing the contour on top of the actual text seems to me to be >> causing a problem: in, for example, line 219 of the following screenshot, >> the overview covers up part of the program source, and I can't scroll to >> reveal the covered part. In the example I sent earlier, auto-wrap is on, >> but wrapping places text under the overview, and again it isn't possible to >> scroll to uncover the text. >> >> Is this the way this is supposed to work now? Is there some way to >> prevent the overview from covering up text in the editor? >> > > Currently the only way is to type cmd-u (temporarily turning it off) or, > of course, making the window wider. > > It would not work well to adapt the current implementation so that > scrolling works. It would be doable, however, to adapt the current > implementation so there was a preference to move it into its own separate > canvas% object that lived beside the text (like the old contour). I opted > for the current setup, as typing cmd-u is fast and because you don't have > to pre-allocate space for the contour that could profitably be used for > lines in, say, only one part of the file. > > That said, I can understand how you migth like to have the option. If you > (or anyone!) has interest in making a pull request, I can provide basic > guidance. > > Robby > > > -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
