Cursor going to end of entry when clicked for editing vs highlighting the entry

[philipstarkey]

Original report (archived issue) by Shaun Johnstone (Bitbucket: shjohnst, GitHub: shjohnst).

---

There is a subtle difference between the way the text in an entry which is about to be edited is presented in Qt runmanager compared with GTK runmanager:

In GTK, the text is all highlighted as being selected, with no blinking cursor. If you start typing it will replace the highlighted text, but if you hit a sideways arrow, the cursor will appear at that end of the text box.

In Qt, the text is also highlighted, so you can still overwrite an entry by starting to type without selecting a cursor position, however there is a blinking cursor at the right hand end of the text. If you hit the left arrow, the highlight goes away and the cursor moves to the second last position in the text, rather than the start of the text box.

You can still quickly get the cursor to the start of the text box by hitting "home" rather than the arrow key, so this is a very low priority, and more a case of us having to change our habits when editing globals (we often keep old values or notes in the end of a global value as python comments, so generally want to edit the start of the string rather than the end.
Just thought I'd document the fact that there is some slight difference in the behaviour.

[philipstarkey]

Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).

---

That is non standard behaviour, so it would be good to fix, but I can't reproduce. I'll try on Windows tomorrow, otherwise if you could provide more context as to when it does it, that would be good!

[philipstarkey]

Original comment by Chris Billington (Bitbucket: cbillington, GitHub: chrisjbillington).

---

We're using runmanager in the rubidium chip lab over here now, and even though I'm not a seasoned user of runmanager-gtk, this was super annoying. Goes against my muscle memory from everything else. The fact that it is different on Windows and Linux probably means it's a style difference intentionally set somewhere (it's not like Qt to have platform dependent differences that are unintentional, or at least that's my impression of it), so hopefully there's just a little switch somewhere I can toggle for this, I will look for one.