|
another thing u can do (which is what i do) is hex encode the data after encryption ... then u know u have a valid ascii data stream
"there is no spoon"
biz stuff about me
|
|
|
|
|
|
Anybody have a suggestion on how I could continue to use MFC/C++ with XML and avoid COM?  I'm looking for a way to exchange XML in a robust, straight-forward fashion between my (server) process and another (server) process.
I like life. Life likes me. ( --Ghost of Christmas Present )
|
|
|
|
|
|
Thanks for trying. Unfortunately, using the CString-class breaks down quickly when a CDATA section is placed in the XML document.
|
|
|
|
|
|
I've been using XML4C quite happily with MFC for a couple years. It handles pretty much everything there is to handle in XML land. Google "XML4C" for more info. You'll find it @ IBM's site.
/ravi
Let's put "civil" back in "civilization"
Home | Articles | Freeware | Music
ravib@ravib.com
|
|
|
|
|
I will giving this a try. Thank you very much. 
|
|
|
|
|
The docs say to include windows.h, but it doesnt help. Compile error with:
MENUITEMINFO miiInfo;
miiInfo.cbSize = sizeof(miiInfo);
miiInfo.fMask = MIIM_FTYPE|MIIM_ID|MIIM_STATE;
error C2065: 'MIIM_FTYPE' : undeclared identifier
Thanks,
ns
|
|
|
|
|
Try MIIM_TYPE
[Edit]
Sorry, I just looked up MIIM_TYPE in Winuser.h and found also MIIM_FTYPE is also defined there, but MIIM_FTYPE is enclosed in a #if(WINVER >= 0x0500) block. So you will have to ensure you are building for W2K or above in order for MIIM_FTYPE to be recognized by the compiler.
[/Edit]
Sonork 100.11743 Chicken Little
"You're obviously a superstar." - Christian Graus about me - 12 Feb '03
Within you lies the power for good - Use it!
|
|
|
|
|
|
Hi There
The scenario:
I got one Java application (server) and multiple C++ clients. The java server is always running and the C++ clients will need to communicate with it as they are started/Stopped. The data communicated is mainly XML. All this is running on the same computer.
The demands:
The communication must be platform independent, at least in the Java application (i.e. no using JNI dlls) because the Java server should run unchanged and be able to communicate with clients implemented on other architectures in the future.
The technique should be easy to work with, i.e. not too low level, and not over complicated (as I suspect CORBA is)
The question:
What communication technique/technology should I use?
The considerations:
CORBA Too complicated for the simple use?
Sockets/Pipes Too much work for the intended simple use?
XML-RPC Current my favourite. But is it too inefficient using HTTP when the communication is local?
JNI Not suited for IPC unless memory mapped files are added...correct?
XYMessenger As presented here. Might be suitable but how is it compared to XML-RPC?
Kind Regards Rene
|
|
|
|
|
My vote: Sockets.
"...Ability to type is not enough to become a Programmer. Unless you type in VB. But then again you have to type really fast..."
Me
|
|
|
|
|
I am using ShellExecute to run a dos command.
How can I tell if the dos command failed ?
I think that WinExec might work for this but I must use ShellExecute since I have to wait for a long command to wait and I am utilizing the :
WaitForSingleObject (sei.hProcess, 0)==WAIT_TIMEOUT
Thanks,
Shay
|
|
|
|
|
Shay
How is it going?
WaitForSingleObj may not be the way to go.
Best Wishes,
Marty
Best Wishes and Happy Holiday's,
ez_way
|
|
|
|
|
I did it in a similar way and it works fine
thanks for the dedication.
|
|
|
|
|
What do you think about using CopyCallback ?
UINT CopyCallback(
HWND hwnd,
UINT wFunc,
UINT wFlags,
LPCSTR pszSrcFile,
DWORD dwSrcAttribs,
LPCSTR pszDestFile,
DWORD dwDestAttribs
);
It is part of
int SHFileOperation(LPSHFILEOPSTRUCT lpFileOp
);
Best Wishes and Happy Holiday's,
ez_way
|
|
|
|
|
Hmmmm, how exactly, can you expand ?
|
|
|
|
|
Hi I modified the mail above. Sorry I forgot to include some stuff!
I will be 55 next week or so I am slipping abit or byte.
Best Wishes and Happy Holiday's,
ez_way
|
|
|
|
|
CListCtrl m_list1;
...
DDX_Control(pDX, IDC_LIST1, m_list1);
...
BOOL CSymbolSelectDlg::OnInitDialog()
{
CDialog::OnInitDialog();
// TODO: Add extra initialization here
CImageList mm;
mm.Create (IDB_SYMBOLS, 16, 1, RGB (192, 192, 192));
m_list1.SetImageList(&mm,LVSIL_SMALL);
CString cc;
for(int i=0;i
|
|
|
|
|
The image list needs to be a member of the class otherwise it will get destructed when the function exits
|
|
|
|
|
Hello all,
I'm doing a small app. using thunking mechanism. However, I did'n have a suitable 16-bit Resource Compiler for marking the 16-bit Dll to version 4.0. What I currently have is a 16-bit RC coming with VC++1.52 (can only mark up to version 3.1) and another 32-bit one. Both of them are useless. The MSDN shows that it's in directory BINW16 of Microsoft Win32 SDK. I can't find this directory although I installed Microsoft Flatform SDK. Actually, I don't where it's exactly located. I mean which publishing date of this Flatform SDK set. How can I get this file? If you succeeded in using thunking mechanism, please give me your suggestions. Your helps are highly appreciated.
Best regards.
|
|
|
|
|
Yes,
This may not be any help whatsoever, but the old Lattice C compiler (1988) now VC was 16 bit.
Look around on the web for it. I used it not long ago for a similar prj and found it on a freeboard in Germany.
Best Wishes and Happy Holiday's,
ez_way
|
|
|
|
|
Hi Guys,
Being new to MFC, is it still ok to use GetDlgItem, SetDlgItemInt etc....?
Cheers
 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
