|
I think you can reuse you C code in Qt without much problems. Give it a try.
|
|
|
|
|
I'll second Qt - Qt's nice. And you've got QtCreator, which is a nice Qt-centric IDE. Java, Basic, who cares - it's all a bunch of tree-hugging hippy cr*p
CodeProject MVP for 2010 - who'd'a thunk it!
|
|
|
|
|
if you write a qt GUI publish it at Codeproject. Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
of course
|
|
|
|
|
Just in case you have doubts about QT... I would definitely recommend QT!
Regarding development tools, KDevelop[^] is an IDE supporting Qt, GTK and wxWidgets.
But I usually stick with Eclipse[^] for most part of C++ development.
Hope this helps.
|
|
|
|
|
I'll recommend QT. It's surprising how nobody else mentioned it.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
Let us hope somebody would recommend 'qt' as well
|
|
|
|
|
I'd leave it to others.
“Follow your bliss.” – Joseph Campbell
|
|
|
|
|
..................kidding................. If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
CPallini wrote: Big Grin ..................kidding................. Big Grin
You got me there, Pallini
|
|
|
|
|
C'est la vie... If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
[My articles]
|
|
|
|
|
Just to be contrary, I use wxWidgets. It's free, open source, and cross platform. You measure democracy by the freedom it gives its dissidents, not the freedom it gives its assimilated conformists.
|
|
|
|
|
hi,
i want to load menu dynamically to my dialog from dll.hw can i do that?
|
|
|
|
|
|
So having bashed my head against the wall and having done as much reading as possible, I'm still confused.
My understanding from other posts was that char* is an array of single bytes, and that in VS2005, CString is Unicode. But I seem to have a mixture of this...
I'm doing:
void CMyClass::MyFunc()
{
CFile myFile(L"C:\\MyFile.txt", CFile::modeRead);
char* pchContents = new char[myFile.GetLength()];
myFile.Read(pchContents, myFile.GetLength());
CString myString = (char*)pchContents;
myFile.Close();
delete[] pchContents;
}
but myString is strangely spaced out and have odd bits added to the front and back. Does this mean the contents of pchContents got turned into wide characters?
Anyway, the problem is that after a load of other operations, I have to turn myString back into char* . But wcstombs_s fails because it encounters wide characters.
What I really don't get is the fact that this whole thing works if I don't read from file into myString but build it up using MSXML and cast the resulting BSTR into CString . I thought all CString was wide, so how come I seem to be having two different flavours?
=========================================
The long and the short of it is that I now have a working piece of code.
I'm not entirely sure what happened.
Basically, I was reading in a file (xml file) edited using Visual Studio 2005. I rewrote the thing in notepad and it works fine now.
I guess my code was right in the first place, but the file I was reading wasn't.
I'm guessing that Visual Studio added some MBCS into my file outside of what I typed and that was tripping up my wcstombs_s .
Am I right?modified on Sunday, March 14, 2010 11:55 PM
|
|
|
|
|
try
CString myString(pchContents);
or if you use assignment operator first convert pchContents to widechar using mbstowcs like functions and assign resulting widechar pointer to CString obj.
assigning BSTR into CString works as BSTR is defined as WCHAR*.
wcstombs_s will definitly work, provided you use it for unicode string to multi byte converstion.
|
|
|
|
|
Thanks for the suggestion, but the exact same result as before.
|
|
|
|
|
can u explain whats going wrong with some piece of code?
|
|
|
|
|
PaulowniaK wrote: My understanding from other posts was that char* is an array of single bytes, and that in VS2005, CString is Unicode.
CString is Unicode-ready in the Unicode projects only virtual void BeHappy() = 0;
|
|
|
|
|
I suggest this nice article[^] (and the next one). Things will probably be much clearer afterwards.
|
|
|
|
|
Thanks, I have read this.
The trouble is, I don't know how to tell if I'm working in SBCS, DBCS or Unicode...
Or at least I thought I knew but it looks like I don't...
I wonder if it's because CString's constructor takes MBCS and Unicode, so reading from CFile does one version and writing using MSXML does the other? Almost, but not quite, entirely unlike... me...
|
|
|
|
|
CString become CStringW if your project setting is UNICODE and it becomes CStringA if the project settings is Multi-byte.
|
|
|
|
|
I think my little grey cells are just about OK with that...
But, then, what do you think about the fact that I have 2 CString s, one is apparently CStringA and the other is CStringW in the same project, which I am quite certain is Unicode. Almost, but not quite, entirely unlike... me...
|
|
|
|
|
You are free to explicitly declare CStringA or CStringW independent of the project settings.
CStringA csA = "Hello";
CStringW csW = L"Hello";
|
|
|
|
|
Rejeesh.T.S wrote: You are free to explicitly declare CStringA or CStringW independent of the project settings.
The trouble is that I seem to have a string that is both CStringA and CStringW at the same time, depending on how the values are set.Almost, but not quite, entirely unlike... me...
|
|
|
|