| | [ Return to Bugs & Features | Roadmap 1.3 | SVN ⇄ GIT ]
STR #3337
| Application: | FLTK Library |
|---|
| Status: | 2 - Closed w/o Resolution |
|---|
| Priority: | 3 - Moderate, e.g. unable to compile the software |
|---|
| Scope: | 3 - Applies to all machines and operating systems |
|---|
| Subsystem: | Core Library |
|---|
| Summary: | Fl_Text_Display: sometimes selection doesn't work |
|---|
| Version: | 1.3-current |
|---|
| Created By: | greg.ercolano |
|---|
| Assigned To: | AlbrechtS |
|---|
| Fix Version: | Will Not Fix |
|---|
| Update Notification: | |
|---|
Trouble Report Files:
No files
Trouble Report Comments:
| |
| #1 | greg.ercolano
14:30 Oct 01, 2016 |
| I've gotten the editor (in fluid) into modes where it won't do
text selection. Dragging the mouse and/or keyboard selection with
shift-left, shift-right, and shift-end/shift-home. The cursor moves,
but no selection is shown, and seems to act as if it's really not
selected (i.e. not just a display problem).
Unfortunately not sure the cause exactly, or how to replicate,
but citing it as something to investigate. Had to restart fluid
to get it working again. | |
| |
| #2 | greg.ercolano
14:53 Oct 01, 2016 |
| I restarted fluid again, and played around with the code editor.
Got to replicate it quickly at one point, but the same steps didn't
repeat it.
Just before it started happening, I did a double-click-drag with the
mouse, to make a 'word' selection, and after that, it started exhibiting
the no-select behavior. But I figured out a way to recover without
restarting the app.. not sure what that was though, as I was unable
to replicate with the same steps again.
It must be some internal state variable getting into a state
it shouldn't be in.
That's all I have for now.. | |
| |
| #3 | greg.ercolano
16:36 Aug 22, 2020 |
| This was on linux BTW. | |
| |
| #4 | bheesham
20:14 Apr 20, 2021 |
| I was not able to reproduce this. Which version of FLTK/Fluid were you using?
Versions I used:
Fluid: 1.3.5
Distro: Fedora 33
Kernel: Linux neptune.localdomain 5.11.11-200.fc33.x86_64 #1 SMP Tue Mar 30 16:53:32 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux | |
| |
| #5 | greg.ercolano
20:29 Apr 20, 2021 |
| As reported, 1.3.x, the head of the 1.3 branch in git at the time,
which was back in 2016.
It took a lot of use in fluid before it started misbehaving.
I suppose it could be a bug with a wild pointer or some such.
Didn't crash, but it did become practically unusable IIRC. | |
| |
| #6 | AlbrechtS
10:37 Apr 21, 2021 |
| I also tried to reproduce this effect but didn't succeed. I checked out Git commit c8837ffaece82b0 (Date: Sat Oct 1 22:35:37 2016 +0000) and tested on Linux as well. Everything I tried worked fine.
Just to be clear: I used the fluid menu "New/code/code" and edited code in the "Code Properties" window. I tried, as described, to extend the "keyboard selection with shift-left, shift-right, and shift-end/shift-home" but I couldn't find an issue. Neither by dragging the mouse.
----
Greg, I propose to close this STR and to open a new GitHub Issue if this can be reproduced with FLTK 1.4 in a repeatable way. | |
| |
| #7 | greg.ercolano
11:01 Apr 21, 2021 |
| OK, but what if it's not repeatable? (It doesn't seem to be) | |
| |
| #8 | AlbrechtS
11:23 Apr 21, 2021 |
| You could still open a GitHub issue (preferred against 1.4), maybe someone can repeat it or has a clue where to look... | |
| |
| #9 | AlbrechtS
02:38 May 07, 2021 |
| Since this bug is not reproducible I'm closing this STR now. | |
[ Return to Bugs & Features ]
|
| |
