Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cursor does not work properly #1371

Closed
zrdai opened this issue Jan 18, 2017 · 10 comments
Closed

Cursor does not work properly #1371

zrdai opened this issue Jan 18, 2017 · 10 comments
Labels

Comments

@zrdai
Copy link

zrdai commented Jan 18, 2017

I am using Geany within Mac, OS Sierra, 10.12.2. The cursor cannot grap the buttons because it should always be higher than the position of the button. This is really annoying. Can I get help? I have already tried to reinstall Geany 1.29. It did not help. Could be an incompatability with Sierra.
Thank you.

@phillc54
Copy link

I have the same problem plus to select text the cursor needs to be two lines above the required text.
macOS Sierra 10.12.4
Geany 1.30.1
I have tried earlier Geany versions back to 1.25 but they all behave the same.

@lukaspirpamer
Copy link

I have the same problem, I have just downloaded the newest version for mac (1.33)
I'm using macOS Sierra 10.12.6
Does anybody have a workaround?
Thanks!!

@elextr
Copy link
Member

elextr commented Aug 27, 2018

@techee ping

@elextr elextr added the macos label Aug 27, 2018
@phillc54
Copy link

I have Geany 1.33 on two iMacs,
It works fine on the iMac16,2 which reports as iMac (Retina 4K, 21.5-inch, Late 2015)
It shows the same faulty behaviour on the iMac14,1 which reports as iMac (21.5-inch, Late 2013)
Both iMacs have macOS High Sierra 10.13.6

@lukaspirpamer
Copy link

lukaspirpamer commented Aug 27, 2018

Thank you for your quick reply!!
I tried to reproduce the bug and it seems that it has something to do with the screen-size. (I'm working at the moment on a macbook air 11")
The error appears when I try to save a document. The popping up "saveas" window however is too small for my display, which can be noticed by the half hidden "save" and "cancel" buttons ("Umbenennen", "Abbrechen", "Speichern" for the German version - see screenshot)
This "bug" can be handled by dragging the window to a new location, it will be resized automatically and the cursor-function works as expected.

window_too_small

@phillc54
Copy link

phillc54 commented Aug 28, 2018

I can confirm it behaves the same here on the iMac14,1.
Manually resizing the window while editing also fixes the cursor problem.

[Edit: duplicates deleted]

@geany geany deleted a comment from phillc54 Aug 28, 2018
@geany geany deleted a comment from phillc54 Aug 28, 2018
@elextr
Copy link
Member

elextr commented Aug 28, 2018

@lukaspirpamer I presume you mean "is too LARGE for the display"?

With very little knowledge and less forethought, this looks like a bug in the GTK/OSX backend when windows don't fit the screen.

@phillc54
Copy link

The window is not too big for the screen.
The cursor problem can be 'fixed' by resizing the window or moving the window.
This needs to be done for each popup window as well e.g. Open, Save etc.
Moving/Resizing by just one pixel is enough...
screen shot 2018-08-28 at 10 42 48 am

@elextr
Copy link
Member

elextr commented Aug 28, 2018

Ok, so GTK and OSX have differing ideas where the window is after popup so they disagree about if the cursor is over a button, but resync after a move/resize.

Somebody should report to the GTK/OSX backend.

@techee
Copy link
Member

techee commented Aug 29, 2018

To me this looks like a duplicate of #1729 - the problems are caused by the extra tab at the top which shouldn't be there. To summarise what you could try to fix the problem:

  1. In macOS Settings set the value of "Dock->Prefer tabs when opening documents" to Manually.
  2. In Geany menu bar try selecting "View->Hide tab bar"
  3. As suggested in Double title bar #1729 you might want to remove a GTK installation from homebrew or some other package manager which might conflict with Geany.

I'm closing this issue as I think it's a duplicate of #1729 and the discussion can continue there. Feel free to reopen this bug report if you think it's not the case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants