You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please see the attached image below: Geany cannot find the text that obviously is present because there is some more text way to the right in the search box which cannot be seen by the user because of the limited width of the search box which, in consequence, prevents the visible text from being located. Please could you provide an indicator to show the user that the search text extends further to the right than perhaps they anticipate leading to the anomalous situation pictured below? I try to get a new user started with Geany every week because it is such a great editor!
The text was updated successfully, but these errors were encountered:
Geany does not know how wide the text entry is, you can resize the dialog and it grows/shrinks
Geany does not know how wide the displayed text is, its Unicode, so number of bytes != number of code points != number of glyphs and those can be varying widths depending on font and font size chosen
So Geany would have to replicate most of the GTK layout code just to tell if the text exceeded the available width, pretty unlikely to happen, in fact (as best anyone can predict such things) won't ever happen unless its added to the text entry widget in GTK, sorry.
Please see the attached image below: Geany cannot find the text that obviously is present because there is some more text way to the right in the search box which cannot be seen by the user because of the limited width of the search box which, in consequence, prevents the visible text from being located. Please could you provide an indicator to show the user that the search text extends further to the right than perhaps they anticipate leading to the anomalous situation pictured below? I try to get a new user started with Geany every week because it is such a great editor!
The text was updated successfully, but these errors were encountered: