|
Dear Bartosz
Will you pleasee explain it in detail.I am new also to VC and i have to cutomize a product which has dlls.
I have tried WM_KEYDOWN:
if (wParam)
case:VK_F1:
ExitAppliaction();
return(0);
case: VK_ESCAPE:
ExitApplication();
return(0);
It is working for F1 key but it is not working with Escape key.
So kindly give me the explanation.
Thanking you in advance..
With Regards,
Adarsh
I
|
|
|
|
|
Try this (SDI assumed):
BOOL CMainFreame::PreTranslateMessage(MSG* pMsg)<br />
{<br />
if(pMsg->message == WM_KEYDOWN && pMsg->wParam == VK_ESCAPE)<br />
{<br />
PostMessage(WM_QUIT);<br />
return TRUE;<br />
}<br />
<br />
return CFrameWnd::PreTranslateMessage(pMsg);<br />
}
Regards,
BB
|
|
|
|
|
Hey,
I've made a toolbar for IE but I have one problem. I don't know how to add tooltips to my buttons. Could anyone point me in the right direction??
Thanks.
|
|
|
|
|
Create the toolbar with the TBSTYLE_TOOLTIPS style, then handle the TTN_GETDISPINFO notification to provide the text for the tooltip.
--Mike--
Yeah, payin' the bills with my mad programming skillz.
Defraggin' my hard drive for thrills.
Homepage | RightClick-Encrypt | 1ClickPicGrabber
"You have Erica on the brain" - Jon Sagara to me
|
|
|
|
|
here is a bit code I just threw together.. ofcouse you would want to check the id of each controll and return a different string (either in the 80bytes allocated, or a pointer to one)
<br />
case WM_NOTIFY:<br />
{<br />
LPNMHDR pnmhdr = (LPNMHDR)lParam;<br />
switch (pnmhdr->code)<br />
{<br />
case TTN_GETDISPINFO:<br />
{<br />
LPNMTTDISPINFO lpnmtdi = (LPNMTTDISPINFO) lParam;<br />
if (lpnmtdi->hdr.idFrom == IDC_XXXX)<br />
{<br />
strcpy(lpnmtdi->szText, "hello");<br />
lpnmtdi->uFlags = TTF_DI_SETITEM;<br />
}<br />
}<br />
break;<br />
}<br />
}<br />
break;<br />
hope it helps
|
|
|
|
|
Michael Dunn wrote:
Yeah, payin' the bills with my mad programming skillz.
Defraggin' my hard drive for thrills.
Calm down Mike. 
-Nick Parker
|
|
|
|
|
I'm writting one for fun and i've only just began to realize that it's quite a tricky process. The implementation i have used is probably not the best(nor is it finished) so i would like to here how maybe more experienced programmers have tackled similar tasks.
(is my lingo correct???)
I basically parse the statement into the following token categories:
1) Command token (SELECT, CREATE, etc)
2) Fields token (mytable.name, etc)
3) Tables token
4) Expression token (mytable.name = 'test')
5) Misc token(s) (ORDER BY, LIMIT, etc)
Once the statement is parsed into the following categories some tokens are further parsed by another parsing engine, like expression tokens will later be passed to an Expression evaluator where again it will be broken down into smaller tokens like < = > + * /, etc...
Anyways, from whats been said, does it sound like i'm on the right track???
Oh yeah, heres another important part:
I start parsing by extracting the COMMAND from the original string
So: SELECT * FROM temp WHERE name = 'Test'
Becomes: * FROM temp WHERE name = 'Test'
This is accomplished using the function CParse::ExtractCommand()
Then I would call CParse::ExtractFields() and so on...
Is there another way to accomplish this???
Any ideas???
Thanks
"Two wrongs don't make a right, but three lefts do!" - Alex Barylski
|
|
|
|
|
I have written parsing routines a couple of years ago to parse circuit descriptions, and let me tell you that it gets really tricky. At that time I remember that I started doing some readings on parsers, compilers, etc and they would use graph theory which I must say I have no clue how to use it. I mean I kind of know the basics from my math classes but that's about it. However, the approach that you are using for your SQL parsers is something that works just fine because most of us (my friends and I) followed the same logic to parse circuit descriptions.
// Afterall I realized that even my comment lines have bugs
|
|
|
|
|
Interesting...
"Two wrongs don't make a right, but three lefts do!" - Alex Barylski
|
|
|
|
|
little question.
is there a chance to get a pointer back to the application.
and to use the functions of the application?
or to get data from the application.
or is the only way to send messages?
how could i communication between the dll and the application.
i could call a dll function.
but how is it if a export a view and wanna call a function from the mainframe or from
the document class?
any ideas?
|
|
|
|
|
The DLL has a message queue. Handle the incoming message.
Kuphryn
|
|
|
|
|
Well you can pass a pointer from the app to the DLL and then it can use that. If the functions are in your CMainFrame class et.all. then you can use MFC functions in your DLL to get a ptr to these.
Another alternative is "Calling an Exported Function in an EXE from Within a DLL" http://codeguru.earthweb.com/dll/ExportingFromExe.html[^]
Neville Franks, Author of ED for Windows. www.getsoft.com
Make money with our new Affilate program
|
|
|
|
|
As you import functions from DLL to your application, and not the other direction, application-defined classes should not be called by the DLL.
Use MFC extension DLL to export a view class for your app's framework.
Regards,
BB
|
|
|
|
|
thats ok, and how did i got a pointer back to my app? and (myApp*) AfxGetApp() ??
|
|
|
|
|
1. Thou shalt not include CMyApp definition in a DLL.
2. You may use AfxGetApp() to send messages to your app, but I personally don't like such solutions - this is not what DLLs are for. 
Regards,
BB
|
|
|
|
|
i know it.
but i need to get pointers back to my app.
and messages are a bad way. but the only way that i know
|
|
|
|
|
Another question. How can I get the ethernet card number of a computer because I've read somewhere that that number is unique and I would like to explore the possibility of using it at a unique identifier to protect my software. That's why I want to read BIOS info too, because I can get the motherboard number etc. I have seen DiskId32 but that was too confusing and frustratting enough for me I couldn't find any of the macros, data structures, and functions used by the software.
// Afterall I realized that even my comment lines have bugs
|
|
|
|
|
Check this out:
http://tangentsoft.net/wskfaq/examples/getmac-netbios.html
They also show 2 other methods that don't rely on having NetBIOS.
|
|
|
|
|
Thank you very very much Philnessosity.
// Afterall I realized that even my comment lines have bugs
|
|
|
|
|
Can someone direct me to a website where I can learn how to read BIOS information using API or MFC, or even Win32 Assembly, please?
// Afterall I realized that even my comment lines have bugs
|
|
|
|
|
I'm not totally sure, but I think under WIN32 you would raise an exception when you tried to access BIOS while running under protected mode. Protected mode is what applications all run under. When apps need resources like perhaps what your requesting, a device driver is needed and a task switch is performed (i believe) where for a small period of time the device driver code gets to run in a un-restricted environment (Starting with the 80x386/286??? CPU's could run in several different states, virtual, protected, etc...it's been a while since I glanced at my assembly books please forgive any technical discrepancies )
Anyways...I recall reading in a book once that bios parameters were accessed using the IO asm instructions IN/OUT and for some reason PORT 78h or something rings a bell...so you might wanna check that out.
I'll dig through my library and try and find the book i have that actually shows you how to read from the bios, however it will only work under DOS.
Cheers
"Two wrongs don't make a right, but three lefts do!" - Alex Barylski
|
|
|
|
|
Thank you Hockey. I just needed a confirmation. I had tried in the past to access hardware directly by using interrupts but I learned the hard way that that is impossible in Windows, while in DOS that's easy. I just wanted to make sure that there are no BIOS data structures provided by MS, because I have seen some source code where they use IOCTL (I think) macros which don't seem to exist anywhere. And they would access the hardware. I really don't know anything about windows devices so for now I guess I will have to postpone my BIOS reading project, until I develop some skills in VxD.
// Afterall I realized that even my comment lines have bugs
|
|
|
|
|
Toni78 wrote:
I guess I will have to postpone my BIOS reading project, until I develop some skills in VxD.
This will only work in windows 9X. Windows NT, 2000 and XP will use device driver .sys
John
|
|
|
|
|
John M. Drescher wrote:
This will only work in windows 9X. Windows NT, 2000 and XP will use device driver .sys
I am confused...
// Afterall I realized that even my comment lines have bugs
|
|
|
|
|
Toni78 wrote:
I guess I will have to postpone my BIOS reading project, until I develop some skills in VxD.
I was just saying that a VXD will only work in windows 9X.
John
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
