FAQ-Issues and Workarounds - Revision history

Mgimenez: /* Q: I cannot find any text in my Code::Blocks logs? */ Make forum URL absolute

2022-12-26T19:45:54Z

Q: I cannot find any text in my Code::Blocks logs?: Make forum URL absolute

← Older revision		Revision as of 19:45, 26 December 2022
Line 93:		Line 93:
	==== Q: I cannot find any text in my Code::Blocks logs? ====		==== Q: I cannot find any text in my Code::Blocks logs? ====

	'''A:''' On MS Windows, wxWidgets sometimes does not show the content of logs at first; scrolling in the log will bring the text to visibility. Please note that this is a known wxWidgets bug in wxWidgets v2.8.x. See more details in [/index.php/topic,15940.msg108421.html#msg108421 refresh issue in wx2.8.12]		'''A:''' On MS Windows, wxWidgets sometimes does not show the content of logs at first; scrolling in the log will bring the text to visibility. Please note that this is a known wxWidgets bug in wxWidgets v2.8.x. See more details in [https://forums.codeblocks.org/index.php/topic,15940.msg108421.html#msg108421 refresh issue in wx2.8.12]

	==== Q: Scrolling causes gray areas/distortions to obscure my code in the editor? ====		==== Q: Scrolling causes gray areas/distortions to obscure my code in the editor? ====

Mgimenez: /* Q: Using Code::Blocks with high dpi screens and windows */ Make URL absolute

2022-12-26T19:44:56Z

Q: Using Code::Blocks with high dpi screens and windows: Make URL absolute

← Older revision		Revision as of 19:44, 26 December 2022
Line 112:		Line 112:
	==== Q: Using Code::Blocks with high dpi screens and windows ====		==== Q: Using Code::Blocks with high dpi screens and windows ====

	'''A:''' /index.php/topic,21119.msg145906.html#msg145906		'''A:''' https://forums.codeblocks.org/index.php/topic,21119.msg145906.html#msg145906

Bluehazzard: Adding the question about high dpi screens and windows

2017-02-09T13:21:53Z

Adding the question about high dpi screens and windows

← Older revision		Revision as of 13:21, 9 February 2017
Line 109:		Line 109:

	Open ''Settings->Editor...->Keyboard shortcuts''. The command ''Ctrl-Alt-.'' is assigned to ''Menu bar->Search->Open include file'' by default. Changing or removing this shortcut should resolve the problem.		Open ''Settings->Editor...->Keyboard shortcuts''. The command ''Ctrl-Alt-.'' is assigned to ''Menu bar->Search->Open include file'' by default. Changing or removing this shortcut should resolve the problem.

			==== Q: Using Code::Blocks with high dpi screens and windows ====

			'''A:''' /index.php/topic,21119.msg145906.html#msg145906


	----		----

	Return to '''[[FAQ]]'''.		Return to '''[[FAQ]]'''.

Bikepunk: /* Hal Solution (Ubuntu 8.10 and above): */

2013-04-16T09:09:20Z

Hal Solution (Ubuntu 8.10 and above):

← Older revision		Revision as of 09:09, 16 April 2013
Line 27:		Line 27:
	===== ''Hal Solution (Ubuntu 8.10 and above):'' =====		===== ''Hal Solution (Ubuntu 8.10 and above):'' =====

	Note : Hal is now [~~deprecated~~ https://wiki.ubuntu.com/Halsectomy]		Note : Hal is now [https://wiki.ubuntu.com/Halsectomy deprecated]

	For Ubuntu (and other gnome desktops), another simple solution for the current user is to change a preference.		For Ubuntu (and other gnome desktops), another simple solution for the current user is to change a preference.

Bikepunk: /* Q: Sometime, in the text editor, space bar triggers Code Completion, how do I fix that? */

2013-04-16T09:04:08Z

Q: Sometime, in the text editor, space bar triggers Code Completion, how do I fix that?

← Older revision		Revision as of 09:04, 16 April 2013
Line 7:		Line 7:
	==== Q: Sometime, in the text editor, space bar triggers Code Completion, how do I fix that? ====		==== Q: Sometime, in the text editor, space bar triggers Code Completion, how do I fix that? ====

	'''A:''' ~~Information found on~~ the ~~forum~~.		'''A:''' '''The problem is solved in the version 12.11.'''

	~~It's possible to fix this issue editing the keyboard entry in /etc/X1/xorg~~.~~conf file. However~~, ~~some recent distribs use HAL, therefore xorg.conf is empty (since Ubuntu 8.~~10 ~~for instance)~~. ~~It's also possible~~ to ~~use a setxkbmap tool~~.		On Ubuntu 12.04 LTS, version 10.05 from the official repos makes this space bar problem, upgrading to codeblocks 12.11 solved the problem.

	~~===== ''Problem solved in version 12~~.~~11'' =====~~		For earlier versions, there are (at least) 3 working fixes :
			* [[#setxkbmap_Solution: \| setxkbmap]]
			* [[#Hal_Solution_.28Ubuntu_8.10_and_above.29: \| Hal]]
			* [[#setxkbmap_Solution: \| xorg.conf]]

	~~On a ubuntu 12~~.~~04 LTS~~, ~~version 10~~.~~05 from~~ the ~~offical repos makes~~ this ~~space bar problem, upgrading to codeblocks 12.11 solved the problem.~~		Information found [/index.php/topic,8291.0.html on the forum]

			===== ''setxkbmap Solution:'' =====

			run this command before running Code::Blocks (works fines for KUbuntu)
			setxkbmap -option nbsp:none
			if it's not enough you can try:
			setxkbmap -option nbsp:none -model pc 105 -layout fr -variant latin 9

	===== ''Hal Solution (Ubuntu 8.10 and above):'' =====		===== ''Hal Solution (Ubuntu 8.10 and above):'' =====

			Note : Hal is now [deprecated https://wiki.ubuntu.com/Halsectomy]

	For Ubuntu (and other gnome desktops), another simple solution for the current user is to change a preference.		For Ubuntu (and other gnome desktops), another simple solution for the current user is to change a preference.
Line 56:		Line 68:
	It seems that KUbuntu requires the following line:		It seems that KUbuntu requires the following line:
	Option "XkbOptions" "nbsp:none"		Option "XkbOptions" "nbsp:none"

	~~===== ''setxkbmap Solution:'' =====~~

	~~run this command before running Code::Blocks (works fines for KUbuntu)~~
	~~setxkbmap -option nbsp:none~~
	~~if it's not enough you can try:~~
	~~setxkbmap -option nbsp:none -model pc 105 -layout fr -variant latin 9~~

	==== Q: IDE is drawing the text from Right to Left? ====		==== Q: IDE is drawing the text from Right to Left? ====

Bikepunk: /* Q: Sometime, in the text editor, space bar triggers Code Completion, how do I fix that? */

2013-04-16T08:48:53Z

Q: Sometime, in the text editor, space bar triggers Code Completion, how do I fix that?

← Older revision		Revision as of 08:48, 16 April 2013
Line 10:		Line 10:

	It's possible to fix this issue editing the keyboard entry in /etc/X1/xorg.conf file. However, some recent distribs use HAL, therefore xorg.conf is empty (since Ubuntu 8.10 for instance). It's also possible to use a setxkbmap tool.		It's possible to fix this issue editing the keyboard entry in /etc/X1/xorg.conf file. However, some recent distribs use HAL, therefore xorg.conf is empty (since Ubuntu 8.10 for instance). It's also possible to use a setxkbmap tool.

			===== ''Problem solved in version 12.11'' =====

			On a ubuntu 12.04 LTS, version 10.05 from the offical repos makes this space bar problem, upgrading to codeblocks 12.11 solved the problem.

	===== ''Hal Solution (Ubuntu 8.10 and above):'' =====		===== ''Hal Solution (Ubuntu 8.10 and above):'' =====

Ollydbg: /* Q: I cannot find any text in my Code::Blocks logs? */ add links about this issue

2012-04-14T00:36:33Z

Q: I cannot find any text in my Code::Blocks logs?: add links about this issue

← Older revision		Revision as of 00:36, 14 April 2012
Line 84:		Line 84:
	==== Q: I cannot find any text in my Code::Blocks logs? ====		==== Q: I cannot find any text in my Code::Blocks logs? ====

	'''A:''' On MS Windows, wxWidgets sometimes does not show the content of logs at first; scrolling in the log will bring the text to visibility. Please note that this is a known wxWidgets bug in wxWidgets v2.8.x.		'''A:''' On MS Windows, wxWidgets sometimes does not show the content of logs at first; scrolling in the log will bring the text to visibility. Please note that this is a known wxWidgets bug in wxWidgets v2.8.x. See more details in [/index.php/topic,15940.msg108421.html#msg108421 refresh issue in wx2.8.12]

	==== Q: Scrolling causes gray areas/distortions to obscure my code in the editor? ====		==== Q: Scrolling causes gray areas/distortions to obscure my code in the editor? ====

MortenMacFly: /* Q: I cannot find any text in my Code::Blocks logs? */

2012-03-23T23:01:14Z

Q: I cannot find any text in my Code::Blocks logs?

← Older revision		Revision as of 23:01, 23 March 2012
Line 84:		Line 84:
	==== Q: I cannot find any text in my Code::Blocks logs? ====		==== Q: I cannot find any text in my Code::Blocks logs? ====

	'''A:''' On MS Windows, wxWidgets sometimes does not show the content of logs at first; scrolling in the log will bring the text to visibility. Please note that this is a known wxWidgets bug in ~~wx 2~~.8.x.		'''A:''' On MS Windows, wxWidgets sometimes does not show the content of logs at first; scrolling in the log will bring the text to visibility. Please note that this is a known wxWidgets bug in wxWidgets v2.8.x.

	==== Q: Scrolling causes gray areas/distortions to obscure my code in the editor? ====		==== Q: Scrolling causes gray areas/distortions to obscure my code in the editor? ====

MortenMacFly: /* Q: I cannot find any text in my Code::Blocks logs? */

2012-03-23T23:00:54Z

Q: I cannot find any text in my Code::Blocks logs?

← Older revision		Revision as of 23:00, 23 March 2012
Line 84:		Line 84:
	==== Q: I cannot find any text in my Code::Blocks logs? ====		==== Q: I cannot find any text in my Code::Blocks logs? ====

	'''A:''' On MS Windows, wxWidgets sometimes does not show the content of logs at first; scrolling in the log will bring the text to visibility.		'''A:''' On MS Windows, wxWidgets sometimes does not show the content of logs at first; scrolling in the log will bring the text to visibility. Please note that this is a known wxWidgets bug in wx 2.8.x.

	==== Q: Scrolling causes gray areas/distortions to obscure my code in the editor? ====		==== Q: Scrolling causes gray areas/distortions to obscure my code in the editor? ====

MortenMacFly: /* Q: Syntax highlighting is broken; how do I fix it? */

2012-03-23T23:00:01Z

Q: Syntax highlighting is broken; how do I fix it?

← Older revision		Revision as of 23:00, 23 March 2012
Line 76:		Line 76:
	==== Q: Syntax highlighting is broken; how do I fix it? ====		==== Q: Syntax highlighting is broken; how do I fix it? ====

	'''A:''' Code::Blocks cannot know how to highlight your code unless it knows what lexer to use. This is normally automatically determined by the file extension, so it is important to save the file and name it correctly (<tt>.c</tt> or <tt>.cpp</tt> for C and C++ code). It is also possible to activate syntax highlighting on a temporary basis. Open ''Edit->Highlight mode'' and select the language the current file is using.		'''A:''' Code::Blocks cannot know how to highlight your code unless it knows what lexer to use. This is normally automatically determined by the file extension, so it is important to save the file and name it correctly (for example, <tt>.c</tt> or <tt>.cpp</tt> for C and C++ code). It is also possible to activate syntax highlighting on a temporary basis. Open ''Edit->Highlight mode'' and select the language the current file is using. Alternatively add the extension to the lexer configuration in the editor options. This will permanently apply the chosen syntax highlighting for all files with this extension.

	==== Q: I posted on the forums that Code::Blocks was not working, but no one could help me? ====		==== Q: I posted on the forums that Code::Blocks was not working, but no one could help me? ====