Open GoogleCodeExporter opened 8 years ago
Adding in a checkbox with that functionality would take some major re-coding
efforts, as many core functions depend on the tab widget existing. I tried
adding an option this evening and got something working on a very basic level,
but it introduced too many major bugs that I didn't think would be easy to
track down.
One alternative is simply to hide the tab bar if you only have a single file
open. I can hide the tab bar with some style sheets, but I still need to
figure out how to determine the height of the tab bar (would be different on
different OSes and even different desktop themes). I thought about using the
tabBar() function on the QTabWidget object and getting it's height, but
tabBar() is marked protected, so only friend/child classes can call it; I
really don't want to have to sub-class QTabWidget just for this. If I could
get the coordinates of both the QTabWidget and QsciteEditor relative to the
window frame, the difference of the two's Y-coordinate should be the height of
the tab bar, but I haven't figured out of I can get those values either quite
yet... (Ben, can you see any way of figuring out the height of the tab bar?)
I also saw your comment on the AUR package, however, I'd like to track down a
new crash bug I discovered with QScintilla 2.4.6 before updating the AUR build
script (since the QSciTE build script pulls the latest QScintilla and builds a
static lib to link against).
Original comment by jpsut...@gmail.com
on 1 Mar 2011 at 5:25
Ok, thanks for looking into it... Take your time ;)
P.S. I dunno if it's worth opening a new issue so I'll just ask here as a minor
sidequestion... I saw in other QScintilla projects that it has a feature of
highlighting the line we are currently working on (light blue on white
background). Would it be possible to implement something like that in qscite?
Original comment by karaba...@gmail.com
on 1 Mar 2011 at 8:52
Open a new issue for the highlighting question. I'll see if that can be done.
Original comment by jpsut...@gmail.com
on 1 Mar 2011 at 1:11
Original issue reported on code.google.com by
karaba...@gmail.com
on 28 Feb 2011 at 10:25