I was trying to have a better view at the output, so I decided to full screen the console. The problem is it now took over the entire monitor and the title disappear. So I can't turn it back. I already change the properties in command prompt but nothing change. I also uninstall codeblocks using revo uninstaller and then clean with cccleaner. After I reinstall it's still the same. I really don't know what else to do. BTW I'm using it on windows 7.
Thanks in advance.
Quote from: cotaku on August 30, 2015, 12:55:43 AM
I was trying to have a better view at the output, so I decided to full screen the console. The problem is it now took over the entire monitor and the title disappear. So I can't turn it back. I already change the properties in command prompt but nothing change. I also uninstall codeblocks using revo uninstaller and then clean with cccleaner. After I reinstall it's still the same. I really don't know what else to do. BTW I'm using it on windows 7.
Thanks in advance.
This is a Windows Question and NOT on topic for this site; please read the rules before your next post. http://forums.next.codeblocks.org/index.php/topic,9996.0.html (http://forums.next.codeblocks.org/index.php/topic,9996.0.html)
Solution below
Find a short cut to the cmd.exe
Right click on short cut
Select options tab
Change display option to window.
Tim S.
I'm sorry if I misunderstood the problem. And think it's code block related. But even the solution you gave does not work too. And it's actually the reason I think it is somewhat codeblock fault.
If it is a CB issue the solution is likely to delete (or rename) the CB config file(s).
In folder %APPDATA%\Roaming\CodeBlocks
The file name is normally "default.conf".
Edit: I was able to re-create your problem; but, deleting the CB config failed to fix it.
I still say the solution is a Windows solution; but, I can see why you think it should have a CB based solution.
Tim S.
Found the solution; but, it is NOT newbie friendly.
And, it is a Windows problem; but, one that it would be nice to have a CB fix or workaround.
When you changed the cmd.exe windows it resulted in a register entry under windows 7 32 bit for me.
HKEY_CURRENT_USER\Console\C:_Apps32_cb_release_cb_console_runner.exe
My CB is installed in this path
C:\Apps32\cb_release
Deleting the entry fixed the problem; but, it is not something you want a windows newbie to do.
If you are a Windows advanced user; I have given you enough info to fix the problem.
But, that is NOT likely to be true. I will see if I can find a safe way for normal windows users to fix the problem.
Tim S.
Link to fix for Windows 7 32 bit. https://github.com/stahta01/stahta01.github.io/blob/master/CodeBlocks/CB_Windows_fixes/delete_Console_cb_console_runner.reg (https://github.com/stahta01/stahta01.github.io/blob/master/CodeBlocks/CB_Windows_fixes/delete_Console_cb_console_runner.reg)
Could NOT duplicate the problem under Windows 7 64 bit.
If you still have the problem I can likely guess on the fix; but, I need to know the CB installation path to do so.
Follow link and click on raw button to download reg file.
Edit2: In Firefox, I next used saved page to save the file.
Then, run reg file it should fix the issue if your Code::Blocks installation folder matched mine.
Edit: Double clicking on the reg file should run it.
Tim S.
Quote from: stahta01 on August 30, 2015, 11:55:31 AM
Found the solution; but, it is NOT newbie friendly.
And, it is a Windows problem; but, one that it would be nice to have a CB fix or workaround.
When you changed the cmd.exe windows it resulted in a register entry under windows 7 32 bit for me.
HKEY_CURRENT_USER\Console\C:_Apps32_cb_release_cb_console_runner.exe
My CB is installed in this path
C:\Apps32\cb_release
Deleting the entry fixed the problem; but, it is not something you want a windows newbie to do.
If you are a Windows advanced user; I have given you enough info to fix the problem.
But, that is NOT likely to be true. I will see if I can find a safe way for normal windows users to fix the problem.
Tim S.
Thank you so much for all your response. Everything is fine now. Thanks to this solution ^_^.