codeblocks : some annoying bugs

[smartmobili]

Hi,

It's been a long time I am following CodeBlocks development and unfortunately I was never enough patient
to use it and to live with some bugs in it.
Recently I had to move to linux for a customer because I need to use a special toolchain targeting windows CE, so
I was wondering how codeblocks had evolved.
So I have installed latest version and first test, I cannot even enter spaces !!!!!!
When I enter a space completion stuff is enabled and show me a list of symbols.
So codeblocks discovery will stop here and is there any alternatives, I mean a bit more friendly than emacs/vi ?

Before I leave this <ironic>wonderful IDE, here is some remarks</ironic>


1) When you modify your source code and you don't save it, if you press build you should automatically save the source because
generally it means you forgot to do it.



Regards

[Jenna]

About the spacebar issue: http://forums.codeblocks.org/index.php/topic,8298.0.html
Hope that helps you , too.

1) When you modify your source code and you don't save it, if you press build you should automatically save the source because
generally it means you forgot to do it.

Sources that belong to the active project will automatically be saved if you start the build.
If not you found a bug, and it would be nice, if you can explain how to reproduce that, so that it can be fixed.

[smartmobili]

Do you plan to fix this keyboard issue, because commenting just because codeblocks doens't work is not a real fix.

[Jenna]

Do you plan to fix this keyboard issue, because commenting just because codeblocks doens't work is not a real fix.

Can you please explain what you mean  ?
My english is normally not so bad, but it is not my mother tongue, so maybe I do not understand correctly, but I really do not know what the second part of your answer means.

Did you really read the thread (and the included links) ?

Either you didn't or your problem is caused by something else.

In any case, your postings lack of information to find a solution.

You write youe are on linux, and I'm sure you know, that there are many linux distros in many different versions.
You don't tell us, which version of C::B you use and whether if is a prebuild binary (who provides it) or if it is self-compiled.

Even the version of wxWidgets C::B is built against can be of interest (see "Help -> About").

[smartmobili]

Do you plan to fix this keyboard issue, because commenting just because codeblocks doens't work is not a real fix.

Can you please explain what you mean  ?
My english is normally not so bad, but it is not my mother tongue, so maybe I do not understand correctly, but I really do not know what the second part of your answer means.

Did you really read the thread (and the included links) ?

Either you didn't or your problem is caused by something else.

In any case, your postings lack of information to find a solution.

You write youe are on linux, and I'm sure you know, that there are many linux distros in many different versions.
You don't tell us, which version of C::B you use and whether if is a prebuild binary (who provides it) or if it is self-compiled.

Even the version of wxWidgets C::B is built against can be of interest (see "Help -> About").

Hi,

here is the information :

Ubuntu 8.10 (32 bits version)
Pre-build codeblocks 8.02-0ubuntu2 Build 24 July 2008 15:22:49 wx2.8.8(Linux, Unicode)

Xorg.conf :
Section "Monitor"
   Identifier   "Configured Monitor"
EndSection

Section "Screen"
   Identifier   "Default Screen"
   Monitor      "Configured Monitor"
   Device      "Configured Video Device"
   DefaultDepth   24
EndSection

Section "Module"
   Load   "glx"
EndSection

Section "Device"
   Identifier   "Configured Video Device"
   Driver   "nvidia"
   Option   "NoLogo"   "True"
EndSection


Update : I found a fix, I went to System->Preferences->Keyboard

Change Using Space-key to input non breakable space character
Space key outputs usual space at any level

[Jenna]

Is there no InputDevice section in xorg.conf ?
If not you might have to set the parameters in a fdi file used by the hald.
Recent xorg versions do not use xorg.conf (or at least only very few parts).
I am on windows on work, so I can not say where and what to change, but googling might help.

See here how to (possibly) fix this issue (inside standard xorg.conf) :

http://forums.codeblocks.org/index.php/topic,8291.msg63824.html#msg63824

[smartmobili]

Is there no InputDevice section in xorg.conf ?
If not you might have to set the parameters in a fdi file used by the hald.
Recent xorg versions do not use xorg.conf (or at least only very few parts).
I am on windows on work, so I can not say where and what to change, but googling might help.

See here how to (possibly) fix this issue (inside standard xorg.conf) :

http://forums.codeblocks.org/index.php/topic,8291.msg63824.html#msg63824

You forgot to read my message completely, I FOUND a fix by changing a keyboard option in Gnome Keyboard handling
No need to modify xorg conf, it seems to be a bug with french keyboard layout.

[Jenna]

It's more or less the same fix libfab used.

By the way I started my posting before you updated yours, so I wasn't able to read it.

[Fabyen]

I fix this issue by changing keyboard layout. (french keyboard)

1 - Menu System => Preferences => Keyboard
2 - Select Tab layout
3 - Click "Layout options..."
4 - Expand last option "Using space key to input non-breakable space character"
5 - Select the last choice "Usual Space at any level"

I know it's not system wide, just for the current user (well I suppose) but...

That's it.