|
Take a look at the ATL string conversion macros. Try something like:
USES_CONVERSION;
CComBSTR bstrText(_T("String to convert"));
TCHAR* asciiText = W2T(bstrText);
Note that this uses TCHAR* instead of char* so that you can compile as unicode. Use W2A if you want to use ASCII explicitly. These functions allocate storage on the stack so don't try to access the converted string outside local scope - copy it if you want to return it from a function.
|
|
|
|
|
|
I am trying to create a type library for a 16-bit dll, but I am getting a compile error from MkTypLib.
The error message is:
fatal error M0001: Syntax error near line 9 column 29: unknown type
According to: http://msdn.microsoft.com/library/books/inole/S111F.HTM, the problem seems to be "caused by mismatched OLE DLLs".
My ODL file is:
#define PASCAL pascal
[uuid(9CE95330-3640-11d4-A110-0000C50D034E)]
library ZAPIlibrary {
[dllname("ZAPI.DLL")]
module ZAPImodule {
[entry("zapiGetVersion")]
DWORD PASCAL zapiGetVersion([in] WORD Component, [out] DWORD *Version);
};
};
The error is in the area near the end of "[entry("zapiGetVersion")]". I have tried other things and the exact position of the error varies depending upon what else is in the line but is always close to but before the closing bracket. I have tried adding other attributes such as helpsting after the entry attribute and the column specifed by the error message moves to the end of the other attributes, indicating that it is not really the entry attribute that is a problem.
I am using the following make file:
ZAPILib.tlb : ZAPILib.odl
MkTypLib /D "WIN16" /win16 ZAPILib.odl
I loaded a fresh copy of NT yesterday and still got the error. If anyone can tell me that my ODL file should work as-is for MkTypLib, then I will know that I need to search further for whatever the problem is in my system.
Thank you.
|
|
|
|
|
Does anyone have any suggestions for the following delayed clipboard rendering problem?
I created a new class derived from COleDataSource and overrided the OnRenderXXX() functions and call the new class' SetClipboard() function to register my formats, specify delayed rendering via DelayRenderXXX() for those formats and then call COleDataSource::SetClipboard(). All seems well at this point (i.e. the formats register properly).
My new class' OnRenderXXX() methods don't get called when I paste from another application. However, they DO get called as soon as I END my application (I set breakpoints in all of the OnRenderXXX()'s to verify this).
I've been following the article by Keith Rule posted at codeguru and I can't see any obvious oversights on my part.
Any suggestions?
|
|
|
|
|
Hello,
Any body knows good links or samples on Pluggable protocols and monikers besides MSDN?
thanks
Mahesh
|
|
|
|
|
Hi,
I saw your posting about APP(Asynchronous Pluggable Protocol).
I'm in same situation. I have a sample on MSDN but I can't make it "RUN" from VC++ 6.0.
It looks working in normal situation, but I can't trace the codes in VC++.
I hope to get advice to trace APP sample or similar sample in VC++.
I'm working in IE 5.5, Windows 2000 with sp1, VS with sp4.
Thanks in advance.
Regards,
Ryan
|
|
|
|
|
Hi all,
I have a dialog which has a static textbox that says "The file c:\foo\bar.txt cannot be loaded. You must decide what to do now." and a few buttons beside the textbox to present the user with the choices. There is no problem with the dialog except when the pathname is really long (i.e. 4095 characters long), then the textbox cannot include the whole sentence. What do I do?
I have think of a few ways already but these won't fix the problem:
1. Use a messagebox(but I need more buttons than just OK and Cancel)
2. Use a ellipsize function. (but I want to present the user with the full filename, that's the whole point of having another dialog box)
3. Use "Resizing text to fit in rect" in an earlier article by Jason Phillips. (but this will result in some really ugly code and break a lot of other codes)
What I'm thinking of is, is there some GUI design techniques that will solve this common problem of long filename?
Thanks in advance.
|
|
|
|
|
Instead of a static text box, I recommend you use a "Read-Only" edit box. This will still chop off the name when it's long, but at least the user will be able to scroll through it with the cursor and even copy it to the clipboard if he/she wants.
Regards,
Alvaro
|
|
|
|
|
Dear eng,
I agree; a read-only edit box is the way to go. Also, you can turn on its "Word-Wrap" style simply by turning of the Auto HScroll and Horizontal Scroll styles.
Then make it so that it looks like a listbox (as in area), so that the filename will wrap and add a Vertical Scroll bar (but turn off Auto VScroll) so theu user can scroll the text. They also get a context menu that they can use to copy text to the cliboard with!
Yours,
Brian Hart
|
|
|
|
|
|
Dude, make it multi line text. use \n inside the text string to tell the static control to show the text in the next line. Also you need to increase the width of the control in order to see the rest of the lines.
I hope this helps.
vance
http://upside.hypermart.net
|
|
|
|
|
Hi
I think you can go for multiline scrollable editbox with readonly attributes.
|
|
|
|
|
First of all excuse my english level, I'm just a begginer with it.
I would like to serialize an array of structures, how should I do it?
Thank you very much for your help.
|
|
|
|
|
Look at how the CStrokeList in the Scribble example is serialized - exactly what you need.
|
|
|
|
|
I would like to be able to edit the subitems of a ClistView that's on a SDI app., could you tell me how should I do it?
Thanks a lot for your attention.
|
|
|
|
|
SetItemText should work.
Regards,
Alvaro
|
|
|
|
|
If you mean that you want to allow the user of your program to edit the data, such as in a spreadsheet perhaps, then there is quite a bit of programming required to do that. I am not familiar with the articles available in this web iste, but there is probably at least one article describing that kind of stuff. I know that the CodeGuru has at least one.
|
|
|
|
|
I'm about to post an article that will show you how to do this. Hassle me in a day or so if it doesn't appear.
- Chris
|
|
|
|
|
Will the version you post be strictly an ATL/WTL version? There are plenty of MFC solutions out there. I'm having trouble with the whole PreTranslateMessage stuff and WTL.
Thanks,
Twain
|
|
|
|
|
Can anyone post a quick sample code on how to use StrecthBlt?
I have a bitmap that I want to resize to its half-size.
Thanks a lot in advance.
|
|
|
|
|
assume your image is in m_bmp, and pDC is a window DC.
CDC memDC = CreateCompatibleDC(pDC);
CBitmap *pOldMemBmp = memDC.SelectObject(&m_bmp);
pDC->StretchBlt(outX, outY, bmpWidth / 2, bmpHeight / 2, &memDC, 0, 0, bmpWidth, bmpHeight, SRCCOPY);
memDC.SelectObject(pOldMemBmp);
--
if you don't know bmpWidth and bmpHeight :
BITMAP bm;
m_bmp.GetObject(sizeof(BITMAP), &bm);
bmpWidth = bm.bmWidth;
bmpHeight = bm.bmHeight;
-c
|
|
|
|
|
Does anyone know of a tutorial or webpage that discusses how to create an app that uses more than one document types? i would be very grateful if someone could help. thanks!
|
|
|
|
|
Just add more document template(s) for your other doc/views
and see what happens when you select File / New. You'll be able to go on from there.
Else the VIEWEX sample that came with Visual Studio does what you want.
|
|
|
|
|
We use a lib and a dll to store our shared dialogs.
At compile time we get the following warning:
i:\eldis3\bib_source\eurodialoge\errdlg.h(19) : warning C4275: non dll-interface class 'CDialog' used as base for dll-interface class 'ErrDlg'
c:\programme\microsoft visual studio\vc98\mfc\include\afxwin.h(2568) : see declaration of 'CDialog'
This warning seems to be really just a warning (We cant find any real problems...
...but...
...a warning is a warning.
Does anyone knows how to get rid of this?
This is how we declare our class:
class LIB_EXPORT ErrDlg : public CDialog
where LIB_EXPORT is:
#ifdef _AFXDLL // Sonderfall MFC-Klassen in DLL
#define LIB_EXPORT AFX_EXT_CLASS
#else
#define LIB_EXPORT __declspec( dllexport )
#endif
#else // UNIX
#define LIB_EXPORT
#endif
|
|
|
|
|
Hi
seems to me that you are using MFC staticaly linked, so CDialog isn't in a DLL but in the lib. Guess youget rid of that warning when you use MFC as a shared DLL.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
