Using the latest nigthly 5432 in a Windows XP SP3 environment I'm observing the following strange behaviour.
Using ISO-8852-1 as "Use encoding opening file" and havign all my source code encoded in that encoding I'm getting:
1) With "As fallback encoding" selected -> OK
2) With "As default encoding" -> no characters are present in editor when I open a file.
Using the option 2) the Edit->File Encoding menu is showing (correctly) ASCII(ISO-8859-1) but no characters are present.
I think is a bug of the latest related feature added just before the nightly.
Dear All,This bug still exists in this nightly build. I have reported in this thread:
Using the latest nigthly 5432 in a Windows XP SP3 environment I'm observing the following strange behaviour.
Using ISO-8852-1 as "Use encoding opening file" and havign all my source code encoded in that encoding I'm getting:
1) With "As fallback encoding" selected -> OK
2) With "As default encoding" -> no characters are present in editor when I open a file.
Using the option 2) the Edit->File Encoding menu is showing (correctly) ASCII(ISO-8859-1) but no characters are present.
I think is a bug of the latest related feature added just before the nightly.
Hope this helps.
Max
Index: src/sdk/encodingdetector.cpp
===================================================================
--- src/sdk/encodingdetector.cpp (revision 5435)
+++ src/sdk/encodingdetector.cpp (working copy)
@@ -13,6 +13,7 @@
#include <wx/file.h>
#include <wx/string.h>
#include "manager.h"
+ #include "logmanager.h"
#include "configmanager.h"
#endif // CB_PRECOMP
HexEdit plugin: Make use ..., Make sure the entry in the "File" menu is not at the bottom
Using the option 2) the Edit->File Encoding menu is showing (correctly) ASCII(ISO-8859-1) but no characters are present.
I think is a bug of the latest related feature added just before the nightly.
Patch to fix Windows NON-PCH compile.
This bug still exists in this nightly build. I have reported in this thread:
http://forums.codeblocks.org/index.php/topic,9986.msg69449.html#msg69449
And in the dialog the option 2 "As default encoding" button is beyond it's static box of "Use this encoding".
(http://forums.codeblocks.org/index.php?action=dlattach;topic=10040.0;attach=3108)
No changes to the project templates (for e.g. wxWidgets) yet, unfortunately.
No changes to the project templates (for e.g. wxWidgets) yet, unfortunately.
Are you referring about the update I was working on?? If yes, then I must apologise to all as I could not finish it due time constraint and personal commitments. :)
No changes to the project templates (for e.g. wxWidgets) yet, unfortunately.
Are you referring about the update I was working on?? If yes, then I must apologise to all as I could not finish it due time constraint and personal commitments. :)
Specifically I meant so that the wxWidgets template would work out-of-the-box on Leopard.
Specifically I meant so that the wxWidgets template would work out-of-the-box on Leopard.
Please specify exactly what is required in order to support it on Leopard. I don't have a Mac and I need your help to fix it. Any help is appreciated. Good night. :)
a bug:
when open a file with some chinese character,
the edit window show nothing.
This situation happend on me:That's not a bug. C::B does exactly what you tell him to do:
editor show nothing.
You provide an ANSI file with "non-ANSI" characters.
Choose the right encoding in the first place (when you create the file) I'd say.
I read the latest commit
...
Basically, regardless of any windows default or verification, the programmer should have the capability to force CB using any encoding the programmer likes (IMHO).
...
Revision 5439 - mortenmacfly
Letzte Ă„nderung: Revision 5439 - 2009-02-04 15:35:09 GMT
Logeintrag: - encoding detector: make fallback solution optional (to explicitely force a user to enable the fallback solution)
I roll back the c::b to prior version: svn 5382, and open the main.cpp again.I found c::b (5382) can detect the file's encoding is "Windows 936" (yes, it is 'code page' for gb2312).The same question. so i have to use SVN 5431!
Then, I update the c::b to svn 5432 again. and Set the "Encoding" to "WINDOWS 936" and "As fallback encoding". And I open the main.cpp again. I found the status bar show "utf8". and editor show nothing yet .
svn 5432: see also : (http://forums.codeblocks.org/index.php?action=dlattach;topic=10040.0;attach=3123;image)).
svn 5382 : see the attach.
Index: src/plugins/contrib/wxSmith/wxwidgets/wxscontainer.cpp
===================================================================
--- src/plugins/contrib/wxSmith/wxwidgets/wxscontainer.cpp (revision 5440)
+++ src/plugins/contrib/wxSmith/wxwidgets/wxscontainer.cpp (working copy)
@@ -215,7 +215,7 @@
Codef(_T("%sFit(%O);\n"),ChildAccessPrefix.c_str());
}
- Codef(_T("%sSetSizeHints(%O);\n"),ChildAccessPrefix.c_str());
+ //Codef(_T("%sSetSizeHints(%O);\n"),ChildAccessPrefix.c_str());
}
}
Log message: * encoding detector: using system locale as backup-solution has returnedDon't worry: This "feature" is optional. I don't like it, too because it "fixes" nothing but just tries to help the "dumb user" to get the right encoding. For professionals this can be turned off in the settings.
When the detecting is failing I do believe that the best choice is to use the encoding "preferred" by the programmer, not the system locale.
I can't set size. it's not work.You should report this bug here wxsmith development thread:
I found it's always call 'SetSizeHints'.CodeIndex: src/plugins/contrib/wxSmith/wxwidgets/wxscontainer.cpp
===================================================================
--- src/plugins/contrib/wxSmith/wxwidgets/wxscontainer.cpp (revision 5440)
+++ src/plugins/contrib/wxSmith/wxwidgets/wxscontainer.cpp (working copy)
@@ -215,7 +215,7 @@
Codef(_T("%sFit(%O);\n"),ChildAccessPrefix.c_str());
}
- Codef(_T("%sSetSizeHints(%O);\n"),ChildAccessPrefix.c_str());
+ //Codef(_T("%sSetSizeHints(%O);\n"),ChildAccessPrefix.c_str());
}
}
Hi guys,Uncheck "Use an already running instance instead of starting a new one (if possible)" also, or start C::B with parameter "-ni" (linux) or "-nd" (windows).
Thank you for the efforts making the CodeBlocks perfect.
I've found one bug here, ->
The CodeBlocks can't run more than one instance even though the option (Allow only one running instance) has been removed.
When we are going to have a new relize with automatic update? :?
When we are going to have a new relize with automatic update? :?
Hi guys,Uncheck "Use an already running instance instead of starting a new one (if possible)" also, or start C::B with parameter "-ni" (linux) or "-nd" (windows).
Thank you for the efforts making the CodeBlocks perfect.
I've found one bug here, ->
The CodeBlocks can't run more than one instance even though the option (Allow only one running instance) has been removed.
Hi guys,Uncheck "Use an already running instance instead of starting a new one (if possible)" also, or start C::B with parameter "-ni" (linux) or "-nd" (windows).
Thank you for the efforts making the CodeBlocks perfect.
I've found one bug here, ->
The CodeBlocks can't run more than one instance even though the option (Allow only one running instance) has been removed.
Hi guys,Uncheck "Use an already running instance instead of starting a new one (if possible)" also, or start C::B with parameter "-ni" (linux) or "-nd" (windows).
Thank you for the efforts making the CodeBlocks perfect.
I've found one bug here, ->
The CodeBlocks can't run more than one instance even though the option (Allow only one running instance) has been removed.
I think this should be considered as a bug.
Is it intended to have the DDE server blocking a second instance of C:B? Is there any good reason for it?
I remember it was working before the changes to the DDE server (i.e. Code::Blocks 8.02), and those changes were made to fix other problems.
Regards, XayC
The DDE-Server on windows still works as before, if you uncheck "Use an already running instance instead of starting a new one (if possible)", at least on my system.
So I think it's not a bug.
Maybe the option can be disabled by default, but that's more or less a matter of taste.
In new build don't work commands from custom makefile. Bug?What exactly do you try, and what does not work ?