Chris: cause of outline artifact?

55 views
Skip to first unread message

Matt Wilkie

unread,
Aug 26, 2019, 10:56:47 PM8/26/19
to leo-e...@googlegroups.com
Hi Chris, i saw this in passing and wonder if it might be the same thing you've been running into with the theme weird outline in outline thing.

"11) Set outline: none; when styling inputs and buttons or they will get an outline like the below when clicked/interacted with:
"
https://dev.to/aduranil/53-learnings-from-writing-a-multiplayer-strategy-game-3ijd

Edward K. Ream

unread,
Aug 27, 2019, 10:09:14 AM8/27/19
to leo-editor
On Mon, Aug 26, 2019 at 9:56 PM Matt Wilkie <map...@gmail.com> wrote:

Hi Chris, i saw this in passing and wonder if it might be the same thing you've been running into with the theme weird outline in outline thing.

"11) Set outline: none; when styling inputs and buttons or they will get an outline like the below when clicked/interacted with:

Thanks for the link.  It's interesting.  The context is different, however. The tip applies to a React style sheet.  Qt style sheets are their own breed of animal, with their own quirks.  Afaik, there is no such thing as an "outline" selector in Qt.

Edward

Chris George

unread,
Sep 8, 2019, 4:25:23 PM9/8/19
to leo-editor
After extensive testing I have determined that my initial conclusions hold.

With all else being equal (this took some effort), if the python environment leois running under is native to the OS the stylesheet is flawless.

If leo is running under a venv of any flavor (including conda) the artifacts appear.

Changing the stylesheet while using the venv doesn't work. Gammaray doesn't help. As far as it is concerned it is the same object with the same properties.


I am stumped.


Chris

Terry Brown

unread,
Sep 8, 2019, 4:49:36 PM9/8/19
to leo-e...@googlegroups.com
Could something else like screen dpi determination be different?

Can you run the OS native version (partially) in the venv? Perhaps
just get Python from the venv not the Qt stuff - you'd have to tell the
venv to use system libs. Then just PyQt from the venv not Python / Qt,
etc. if that pattern makes sense.

Cheers -Terr

Matt Wilkie

unread,
Sep 8, 2019, 4:56:11 PM9/8/19
to leo-editor
With all else being equal (this took some effort), if the python environment leois running under is native to the OS the stylesheet is flawless. If leo is running under a venv of any flavor (including conda) the artifacts appear.

Sounds like time to reach out to a wider community, though I don't know which one. And they'll likely need a Hello World kind of example to play with; no idea how hard that might be.

-matt

Chris George

unread,
Sep 8, 2019, 5:08:40 PM9/8/19
to leo-editor
I am taking a break from this for a bit.

In the meantime I will run Leo "native" under Neon with Python 3.6.8 and PyQt 5.12.3.

Chris
Reply all
Reply to author
Forward
0 new messages