Terry,
I am trying to understand QT Styles as they relate to the focus colour
problem.
Currently, the outline pane and the log pane both get the blue focus line
when you hover over them. The body pane does not. The outline pane and the
log pane both take on the blue focus when clicked into, but never lose it
until the session is restarted. The body pane never gets the blue focus
line at any point. EXCEPT: Interestingly, when I create an add-editor pane,
it has both the desired hover behaviour (blue line) and the desired focus
behaviour (blue line until loss of focus, then back to neutral).
Here is the existing configuration as found in the leoSettings.leo
/* focused pane border highlight */
QTextEdit#log-widget, LeoQTreeWidget#treeWidget, QTextEdit#richTextEdit {
border-style: @focused-border-style;
border-width: @focused-border-width;
border-color: @focused-border-unfocus-color;
}
QTextEdit:focus#log-widget, LeoQTreeWidget:focus#treeWidget,
QTextEdit:focus#richTextEdit {
border-style: @focused-border-style;
border-width: @focused-border-width;
border-color: @focused-border-focus-color;
}
And here is what I changed it to to get the blue focus line to "work" in
the body pane. It still does nothing for the Outline pane or the Log pane,
and it broke the hover highlighting for the outline pane, the log pane and
the add-editor "pane". If I wanted to use the @focused* lines to play
around, where and how would I define them? And is this experimentation
likely to get me any closer to solving for the desired behaviour? ie. Is
this a misconfiguration or a bug?
>From myLeoSettings.leo
/* focused pane border highlight */
QTextEdit#log-widget, LeoQTreeWidget#treeWidget, QTextEdit#richTextEdit {
border-style: solid;
border-width: 2px;
border-color: white;
}
QTextEdit:focus#log-widget, LeoQTreeWidget:focus#treeWidget,
QTextEdit:focus#richTextEdit {
border-style: solid;
border-width: 2px;
border-color: cyan;
}
Chris
On Friday, November 8, 2013 7:35:53 AM UTC-8, Terry wrote:
>
> On Fri, 8 Nov 2013 07:12:48 -0800 (PST)
> [email protected] <javascript:> wrote:
>
> >
> >
> > On Friday, November 8, 2013 4:08:27 PM UTC+1, Jacob Peck wrote:
> > >
> > > On 11/8/2013 10:00 AM, [email protected] <javascript:> wrote:
> > >
> > > On Friday, November 8, 2013 2:26:58 PM UTC+1, Edward K. Ream wrote:
> > >>
> > >>
> > >> On Friday, November 8, 2013 7:00:44 AM UTC-6, [email protected]:
> > >>
> > >> > I totally agree. In fact, these were the changes that I immediately
> > >> made. Especially, the font size was way too small.
> > >>
> > >> This bad first impression may have turned a lot of people away from
> Leo
> > >> right at the start. Correcting this could make a surprisingly big
> > >> difference.
> > >>
> > >> I have now disabled @data qt-gui-plugin-style-sheet in
> > >> myLeoSettings.leo. The result is that I am now continuously testing
> the
> > >> corresponding setting in leoSettings.leo.
> > >>
> > >> Edward
> > >>
> > >
> > > Even better than this, could you please make some of those settings
> more
> > > accessible? For instance, you could make the font size of the main
> panes
> > > accessible from the menu. From my very limited experience (just a few
> > > days), Leo's settings are terribly complicated, and entering into
> those
> > > setting files is like entering into a jungle. It is very discouraging!
> > > I had to post help requests on this forum just for changing the font
> type
> > > and sizes. This does not look right. It is far from user-friendly.
> > > My request concerns only the most commonly used settings, of course.
> > >
> > > Perhaps something like:
> > >
> > > @string body-font-face = DejaVu Sans Mono
> > > @string body-font-size = 14pt
> > > @string log-font-face = DejaVu Sans Mono
> > > @string log-font-size = 14pt
> > > @string outline-font-face = DejaVu Sans Mono
> > > @string outline-font-size = 14pt
> > >
> > > Should be handled by the @data qt-gui-plugin-style-sheet parsing code?
>
> > > That would be awesome, in my opinion -- actually, allowing any
> > > '@yoursettinghere' (which searches for either a @color or @string) in
> > > qt-gui-plugin-style-sheet would make the stylesheet wayyyy more usable
> and
> > > Leonine.
> > >
> > > -->Jake
> > >
> >
> > Well, to be even more explicit, I would prefer (as a newbie) not having
> to
> > do at all with something called @data qt-gui-plugin-style-sheet!! What I
> > mean is that SOME all those highly technical entries in the settings
> file
> > should be made accessible from the menus in a humanly understandable
> way.
>
> So the simplest would be menu entries which directly solicit font names
> and sizes from the user.
>
> But it would take a new pathway to push those into the settings system.
>
> What about menu entries which:
>
> - create myLeoSettings.leo, if needed
> - copy the relevant subtree from leoSettings.leo to myLeoSettings.leo,
> if needed
> - contract everything in myLeoSettings.leo except the relevant parts,
> and present those to the user.
>
> So, after selecting the "Font sizes" menu option, the user sees
> something like the attached image? Not as simple as a typical piece of
> software, but also a gentle nudge into the Leo way of doing things,
> that isn't too complicated, so the user can change their font sizes at
> least.
>
> As a first step. Then we can see if there's a clear path for
> avoiding the restart piece, for example.
>
> Also, using @string and @color settings in the theme machinery is
> doable, but not currently done, and needs a little more thought.
>
> Cheers -Terry
>
>
--
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/groups/opt_out.
