Issue 1: "Unindent" (has anyone found the right word for it?)
It would be nice if pressing shift+tab removed all white space up to the previous level of indentation, or up to the last non-white space character or the beginning of the line. In other words, given the following piece of text (| signals the cursor position)
this is a |test
pressing shift+tab should transform it into
this is a |test
and again into
this is a|test
and again would do no more.
Issue 3: Code completion tooltip messing with debugger tooltip
If both tooltips are enabled, trying to see the value of a variable by hovering the pointer on it will display two tooltips, one on top of the other. In all my tests, the code completion tooltip was always on top of the debugger tooltip. Visual Studio solves this issue by completely disabling code completion's tooltip during a debugging session.
Issue 5: Opening files with different encodings
This problem has been discussed, again, recently. Sometimes you try to open a file in CB, but all you get is an empty document. I faced this problem when trying to check the file xmltest.cpp of TinyXML. I was trying different encodings, but I could not find one that would really open the file and display its contents.
Issue 7: Send command to debugger fieldThis is very important for a deep debugging.
I think this one was requested once a long time ago. It would be a seldom used feature, but it would also be handy to have. The debugger output window would be a good place to put it in.
Issue 5: Opening files with different encodings
This problem has been discussed, again, recently. Sometimes you try to open a file in CB, but all you get is an empty document. I faced this problem when trying to check the file xmltest.cpp of TinyXML. I was trying different encodings, but I could not find one that would really open the file and display its contents.
B) Add notion of target, for instance I am developping for Windows CE and we have different SDKThat's why Code::Blocks features the concept of global variables in combination with usual compiler variables.
C) Possibility to associate compiler(s) with a project, for instance I have declared a new compiler and when I am adding a new option,...it never worked different than that.. .unless I don't understand what you mean...?!
B) Add notion of target, for instance I am developping for Windows CE and we have different SDKThat's why Code::Blocks features the concept of global variables in combination with usual compiler variables.
Issue 5: Opening files with different encodings
This problem has been discussed, again, recently. Sometimes you try to open a file in CB, but all you get is an empty document. I faced this problem when trying to check the file xmltest.cpp of TinyXML. I was trying different encodings, but I could not find one that would really open the file and display its contents.
I can't reproduce this with xmltest.cpp downloaded from sourceforge. Can you post the file and/or encoding settings you are having trouble with. Also, what's your locale set to?
Issue 5: Opening files with different encodings
This problem has been discussed, again, recently. Sometimes you try to open a file in CB, but all you get is an empty document. I faced this problem when trying to check the file xmltest.cpp of TinyXML. I was trying different encodings, but I could not find one that would really open the file and display its contents.
I can't reproduce this with xmltest.cpp downloaded from sourceforge. Can you post the file and/or encoding settings you are having trouble with. Also, what's your locale set to?
I tried that with Code::Blocks 5432 in a Dutch version of Windows XP Professional. Just in case, I attach the xmltest.cpp file that always opened as an empty file.
opens fine on my winxp box ("US english"). what are your encoding settings in settings -> editor?
1/ I set my fallback encoding to utf8.
2/ I set utf8, windows 1252, ISO 8859-1 or default as my default encoding.
btw, do you know what the encoding of that file actually is?
SciTE reports 8-bit (means ASCII) for xmltest.cpp attached at previous post...
Index: src/include/editorbase.h
===================================================================
--- src/include/editorbase.h (revision 5611)
+++ src/include/editorbase.h (working copy)
@@ -218,7 +218,7 @@
/** Clear Undo- (and Changebar-) history */
virtual void ClearHistory(){}
-
+
/** Goto next changed line */
virtual void GotoNextChanged(){}
@@ -233,7 +233,7 @@
/** Enable or disable ScrollWidthTracking */
virtual void SetScrollWidthTracking(bool trackWidth){}
-
+
/** Cut selected text/object to clipboard. */
virtual void Cut(){}
@@ -282,6 +282,8 @@
/** Select everything in the editor
*/
virtual void SelectAll() { return; }
+
+ virtual bool IsContextMenuOpened() const;
protected:
/** Initializes filename data.
* @param filename The editor's filename for initialization.
Index: src/sdk/editorbase.cpp
===================================================================
--- src/sdk/editorbase.cpp (revision 5611)
+++ src/sdk/editorbase.cpp (working copy)
@@ -389,3 +389,8 @@
event.Skip();
}
}
+
+bool EditorBase::IsContextMenuOpened() const
+{
+ return m_pData->m_DisplayingPopupMenu;
+}
Index: src/plugins/debuggergdb/debuggergdb.cpp
===================================================================
--- src/plugins/debuggergdb/debuggergdb.cpp (revision 5611)
+++ src/plugins/debuggergdb/debuggergdb.cpp (working copy)
@@ -2495,6 +2495,9 @@
if (!ed)
return;
+ if(ed->IsContextMenuOpened())
+ return;
+
int style = event.GetInt();
if (style != wxSCI_C_DEFAULT && style != wxSCI_C_OPERATOR && style != wxSCI_C_IDENTIFIER)
Yes, you are right...
I mean "ASCII" as non unicode or multibyte...
8-bit equals ASCII if byte value <= 0x7F(127)
If byte value > 0x7F then character can be defined according some encoding (CP1251 or CP1252 [since I'm from Russia] or some else).
There no info about particular encoding is in the file.
applied the patch (rev 5612). Excellent work :-)Yepp - nice catch. ;-)
Issue 7: Send command to debugger field
I think this one was requested once a long time ago. It would be a seldom used feature, but it would also be handy to have. The debugger output window would be a good place to put it in.
QuoteIssue 7: Send command to debugger field
I think this one was requested once a long time ago. It would be a seldom used feature, but it would also be handy to have. The debugger output window would be a good place to put it in.
I second this one, too. Using the "Send user command to debugger" option is just too cumbersome. It's one of the most annoying things in CB for me.
As far As I can remember, this functionality has already implemented, their is a small dialog for you to enter the command directly to GDB. :DThat is correct, but if you want to send a list of commands it's annoying to open this dialog over-and-over again. That's why there should indeed be a "static" input box, e.g. in the debugger's log / whatever window.
...
I want to add another annoying issue:
The tooltips steal the keyboard focus from the editor and the shortcuts are not processed anymore :(
So I have to move the mouse to disable the debugging tooltip, while I'm stepping through the code :(
Where is the problem in wx, cb or gtk? I'm observing this problem on linux (I don't remember if it is pressent on windows)
Issue 7: Send command to debugger field
Is this doable with wx?Certainly. Probably a floating window that makes use of wxPropertyGrid can be used here, too.
Do you have a link to a video that demonstrates the vc10 behaviour?
mixed C++ & ASM debugging (it's actually ASM debugging showing you also the C++ statements), multiple memory views, ...
interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"
The yellow boxes are the new feature in vc10?
The debugger in VC is the only thing they've done right in the IDE... :lol:
Hi Ceniza,mixed C++ & ASM debugging (it's actually ASM debugging showing you also the C++ statements), multiple memory views, ...
One of the most important features for embedded is in my eyes the mixed mode view: intermix ASM and C/C++ source code.
The GNU debugger provides already the information for mixed modeCodeThe passing of --0 or --1 will provide information for mixed mode if it is parsed.interpreter-exec mi "-data-disassemble -f main.cpp -l 2 -- 1"
The only think I do not not if scintilla would be able to display such a content or it would require modifications in the core.