|
Did you receive any kind of file access error code?
Make sure you are using a path in this form:
//ComputerName/RemotePath/FileName
Also, make sure you have the remote path shared and having the correct access permissions. If you are using XP, you will have to setup Security permissions as well.
Like it or not, I'm right.
|
|
|
|
|
I have used that way before,and I can access to that disk driver in the explore so I have correct access permission.
When I use my ATL COM server to load a jpg in the localdisk,it works well.But
when I want to load it from a network disk driver,no matter which way I choose,(//ComputerName/RemotePath/FileName or mapped disk label),I got nothing.
|
|
|
|
|
Hi,
Look at the code below
#define MAKEINTRESOURCE(i) (LPTSTR) ((DWORD) ((WORD) (i)))
If it's a type casting, I feel it's terrible.
My question is: Inside memory, what the variable i look like after this terrible type casting
Any information concerned is appreciated.
Thank you
Best regard.
I confess that I am a stubborn guy, but why not put things thoroughly, logically and systematically clean. One concrete prolem is worth a thousand unapplied abstractions.
|
|
|
|
|
The high word of 'i' will be cleared, since the WORD type cast will remove it.
The DWORD type adds a high word of zero's. The LPTSTR does just change the type of the DWORD to a character pointer, with no effects on the bits in memory.
|
|
|
|
|
Where's Christian?? He won't like that c-style cast one little bit
Signature space for rent. Apply Within.
|
|
|
|
|
If you dont try to modify the pointer returned from MAKEINTRESOURCE, things are okay.
Anyhow MSDN has this warning :-
"The return value from MAKEINTRESOURCE should be passed only to the Win32 resource-management functions"
Nish
Regards,
Nish
Native CPian.
Born and brought up on CP.
With the CP blood in him.
|
|
|
|
|
Yes, this is type casting.
Because the compiler verifies that all computations in your program use compatible datatypes, type casting becomes necessary when you have two data types in a calculation that are not compatible by default.
The MAKEINTRESOURCE macro is a very useful macro, that does serve a good purpose, and is not considered terrible. It allows you to refer to a resource in your module by either a NULL terminated string, or a resource ID.
This type of cast, where you place the target data type in ( ), is called a C-style cast. This is equivalent to the reinterpret_cast operator in C++. It tells the compiler to disregard the format of the data that you are type casting from, and think of it as another, possibly incompatible format.
So this type-cast operation does not change anything inside of memory, it just makes the compiler think of your type-cast variable as another format so that it will not complain that you are trying to form a calculation with two incompatible types.
Build a man a fire, and he will be warm for a day Light a man on fire, and he will be warm for the rest of his life!
|
|
|
|
|
answer:
Pointer to a null-terminated string of 16-bit Unicode characters.
Aizik Yair
Software Engineer
|
|
|
|
|
Hi,
When I´m in Run mode, my ActiveX displays my IPicture object without problem, but, when I want to print or go to design mode ( using MS-WORD), then it only shows some part of the metafile..
My rendering code is:
CComQIPtr<IPicture> _Pict;
HRESULT OnDraw(ATL_DRAWINFO& di)
{
T* pT = static_cast<T*>(this);
RECT& rc = *(RECT*)di.prcBounds;
RECT r = rc;
long lPicWidth = 0;
long lPicHeight = 0;
BOOL bRunTime = FALSE;
Rectangle(di.hdcDraw, 0, 0, rc.right, rc.bottom);
if(_Pict) {
_Pict->get_Width(&lPicWidth);
_Pict->get_Height(&lPicHeight);
SIZE szPic;szPic.cx = lPicWidth;szPic.cy = lPicHeight;
SIZE szCanvas; szCanvas.cx = rc.right; szCanvas.cy = rc.bottom;
SIZE ScaledSize = ScaleCoordinates(szPic, szCanvas);
HRESULT hres = _Pict->Render(di.hdcDraw, 0, 0, ScaledSize.cx, ScaledSize.cy, 0, lPicHeight, lPicWidth, -(lPicHeight), &r);
}
return S_OK;
}
Is there anything wrong ? Or maybe trying to draw a metafile from IPicture to another metafile, doesn´t work ( shiiit !) ?
Thanks in advance, greetings
Braulio
|
|
|
|
|
Hi,
Sorry for the second post.. but this is due to the
reason that some may have misunderstood my problem.
I don't neccessarily require an API or something..
but i've heard that you can have a document FAXed
bt AT commands also.
Please if someone knows, put some light on it
Thanx
Sameer
|
|
|
|
|
It depends on the modem. What modem are you using?
Michael
|
|
|
|
|
Hi,
My MODEM is a Class 1 and 2 Compatible. So please
if you have some idea, let me know
Sameer
|
|
|
|
|
|
Does anybody have classes, that allows to read (or maybe update) dates into DBF files ?
thanks a lot !
|
|
|
|
|
|
Re:
Does anybody have classes, that allows to read (or maybe update) DATAS (!) into DBF files ?
|
|
|
|
|
Hi,
I´m having and ActiveX control that hold an IPicture object to show a diagram.
When the object is active, all works fine ( the controls i'ts drawn with any problem), but if I go to design mode, or if I try to print it, then the IPicture is not well rendered. Do you know any solution for this ?
Thanks in advance,greetings
Braulio
|
|
|
|
|
Hi,
I want to make a small component that can fax a document
to some particular fax machine.
Can somebody give me some information on how to
go about it.
To start with, just fax a normal TXT file.
Sameer
|
|
|
|
|
Its not easy, especially with all the different modems out there.
I'd look into one of the third party fax components or look on the platform SDK for Fax Service.
Michael
Communication is the first step towards enlightenment.
|
|
|
|
|
Hi,
I am reading Window95: A Developer's Guide and encounter a function in Dialog box procedure function.
switch(uMsg){
adgHANDLE_DLGMSG(hwnd, WM_INITDIALOG, keyCount_OnCommand);
...
}
My question is, I can't find the function adgHANDLE_DLGMSG in WIN32 API, why???
Best regard.
I confess that I am a stubborn guy, but why not put things thoroughly, logically and systematically clean. One concrete prolem is worth a thousand unapplied abstractions.
|
|
|
|
|
NicholasCougar wrote:
My question is, I can't find the function adgHANDLE_DLGMSG in WIN32 API, why???
It must be a user defined function. Look further into the source code.
Nish
Regards,
Nish
Native CPian.
Born and brought up on CP.
With the CP blood in him.
|
|
|
|
|
Hi,
The follows are another copy from Programming Application for Microsoft Windows, Fourth Edition .
There is a function similar with the previous one: chHANDLE_DLGMSG
By now, I have not found any function defined as chHANDLE_DLGMSG in source file.
INT_PTR WINAPI Dlg_Proc(HWND hwnd, UINT uMsg, WPARAM wParam, LPARAM lParam)
{
switch(uMsg)
{
chHANDLE_DLGMSG(hwnd, WM_INITDIALOG, Dlg_OnInitDialog);
chHANDLE_DLGMSG(hwnd, WM_TIMER, Dlg_OnTimer);
chHANDLE_DLGMSG(hwnd, WM_COMMAND, Dlg_OnCommand);
}
return (FALSE);
}
Best regard.
I confess that I am a stubborn guy, but why not put things thoroughly, logically and systematically clean. One concrete prolem is worth a thousand unapplied abstractions.
|
|
|
|
|
Is this the Jeffrey Richter book? If so look at the last, or the 2nd from last chapter. It may even be part of the appendix. He has his own custom header files with his own custom functions and macros
Nish
Regards,
Nish
Native CPian.
Born and brought up on CP.
With the CP blood in him.
|
|
|
|
|
Hi,
You are right!!!
Following is the Macro Jeffrey Richter wrote.
// The normal HANDLE_MSG macro in WINDOWSX.H does not work properly for dialog
// boxes because DlgProc's return a BOOL instead of an LRESULT (like
// WndProcs). This adgHANDLE_DLGMSG macro corrects the problem:
#define adgHANDLE_DLGMSG(hwnd, message, fn) \
case (message): return (SetDlgMsgResult(hwnd, uMsg, \
HANDLE_##message((hwnd), (wParam), (lParam), (fn))))
And this Macro is collected in Win95adg.h which is included in source file.
Thank you
Best regard.
I confess that I am a stubborn guy, but why not put things thoroughly, logically and systematically clean. One concrete prolem is worth a thousand unapplied abstractions.
|
|
|
|
|
I'd like to make WM_MOUSEWHEEL message scroll line by line in my control.
Changing delta value in OnMouseWheel() didn't help.
Any help is appreciated, thanks.
|
|
|
|
|