News:

As usual while waiting for the next release - don't forget to check the nightly builds in the forum.

Main Menu

cursor is block

Started by thomas18, May 25, 2007, 07:53:39 PM

Previous topic - Next topic

thomas18

Hi,

In all release of Code::Blocks, when I  click in a some orders my mouse,my cursor blocks itself. I can't move them. I must exiting and restart Code:Blocks. I don't know How I block the cursor. I'm not alone with this troubleshooting.

If you don't understand exactly my problem, I explain him http://www.developpez.net/forums/showthread.php?p=2110604&posted=1#post2110604 if you understand french.

thomas18

nobody have the same problem?

Ceniza

Sorry but I don't understand your problem, and I don't know French either.

BTW, are you using Code::Blocks on Linux, Windows or Mac?

Biplab

In the French forum no additional details were given. What I could understand from machine translation is that the mouse cursor gets blocked in some cases.

It would be better if you explain the problem with your system configuration details.
Be a part of the solution, not a part of the problem.

Game_Ender

Maybe you hit the "insert" key?

thomas18

hi,

When I type a succession of keys and click of mouse, my cursor is blocked, it can still move, but the cursor takes a particular form, not the traditional pointer, and I can nothing any more select, to click. My only solution is to leave codeblocks with the Alt+F4 order. I can only use the keyboard. the mouse is then unusable for all the applications.
I use gnu/linux; Ubnuntu 7.04 more exactly. I have this problem since one year roughly! I often updated codeblocks that I downloaded in the forum. Currently I use the version svn 3989.
The particular cursor look lilke that:

I hope that this time you will be able to understand my problem!  :)
I hope too that this time my English is more comprehensible than the last time.  :D

Ceniza

Ah, now I know what you're talking about. That's a well known problem on Linux and has been discussed many times in the forums. Unfortunately it's a bug in wxWidgets, but some people say it has been fixed in wx 2.8.x, but I haven't tried though.

Sorry for the bad and uncertain news.

Biplab

Please specify your wx-runtime version. As Ceniza told this is a wxGTK bug which has been fixed recently. I don't remember the exact version. But you need to upgrade your wx runtime package.
Be a part of the solution, not a part of the problem.

thomas18

It is not a so bad news! Now I know that this bug is known. It is already a good thing. Then, my version of WxWidget is wx2.6.3
I will install a new version, it will be seen well if this bug is always there or not.