Commit b95375a
1 parent 048db93 commit b95375a
File tree
2 files changed
+2
-2
lines changed- src/gui/layout
2 files changed
+2
-2
lines changedLines changed: 1 addition & 1 deletion
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
35 | 35 |
| |
36 | 36 |
| |
37 | 37 |
| |
38 |
| - | |
| 38 | + | |
39 | 39 |
| |
40 | 40 |
| |
41 | 41 |
| |
|
Lines changed: 1 addition & 1 deletion
Original file line number | Diff line number | Diff line change | |
---|---|---|---|
| |||
36 | 36 |
| |
37 | 37 |
| |
38 | 38 |
| |
39 |
| - | |
| 39 | + | |
40 | 40 |
| |
41 | 41 |
| |
42 | 42 |
| |
|
7 commit comments
elpaso commentedon Jun 8, 2018
Why? How does it look on hidpi?
nyalldawson commentedon Jun 8, 2018
@elpaso it's a follow up to #7192
elpaso commentedon Jun 9, 2018
Wouldn't be better to create a variant of
QgsApplication::Cursor::CrossHair
and make part of the theme?nyalldawson commentedon Jun 9, 2018
@elpaso I might be mistaken, but I thought using the qt standard cursors avoided all issues with hidpi and scaling?
elpaso commentedon Jun 9, 2018
I'm not sure, it may depend on Qt versions + platform + your screen, on my screen I find the standard cross cursor a bit too thin but maybe it's just me.
For sure we loose control over it, I would prefer to use our custom cross-hair in all occasions or we are back to the previous situation that led to the introduction of our themable cursors in the first place.
So, this is what I suggest:
This of course would also apply to #7192
nyalldawson commentedon Jun 9, 2018
I'm fine with always using a custom one, so long as we're consistent with it and never use the standard one
elpaso commentedon Jun 9, 2018
👍 just be consistent.