|
This thread looks like a rainbow. He he
Love Forgives--Love Gives--Jesus is Love  <marquee direction="up" height="50" scrolldelay="1" step="1" scrollamount="1" style="background-color:'#44ccff'">
--Owner Drawn
--Nothing special
--Defeat is temporary but surrender is permanent
--Never say quits
--Jesus is Lord
|
|
|
|
|
|
I think you should handle the COMMAND events in the view class rather than in the Framewindow class.
-Prakash
|
|
|
|
|
Mr.Prakash wrote: i would say that you might have not designed the app properly, i dont see any reason why a mainframe class is trying to get a refrerence to the document,usally the view class does that.
Agreed. It's approaching a cyclic dependency.
"The words of God are not like the oak leaf which dies and falls to the earth, but like the pine tree which stays green forever." - Native American Proverb
|
|
|
|
|
void ExecuteCommand(ISpPhrase *pPhrase, HWND hWnd)
{
SPPHRASE *pElements;
if(SUCCEEDED(pPhrase->GetPhrase(&pElements)))
{
switch(pElements->Rule.ulId)
{
case VID_Trigger:
{
switch(pElements->pProperties->vValue.ulVal) //here
{
case VID_Read:
PostMessage(hWnd, WM_READ, NULL, NULL);
break;
}
}
break;
}
//free pElements
::CoTaskMemFree(pElements);
}
}
pPhrase is the result of an SPEI_RECOGNITION event.
ExecuteCommand(event.RecoResult(), hWnd);
For some reason, pPhrase isn't passing a value to pElements, but it passes the Rule ID. I tested the grammar with the grammar compiler provided in the Speech SDK, and it appears to be alright.
Grammar file-
<GRAMMAR LANGID="409">
<DEFINE>
<ID NAME="VID_Read" VAL="1" />
<ID NAME="VID_Trigger" VAL="253" />
<ID NAME="VID_Action" VAL="254" />
</DEFINE>
<RULE ID="VID_Trigger" TOPLEVEL="ACTIVE">
<P>
<L>
<P>I'd like to</P>
<P>I want to</P>
</L>
</P>
<RULEREF REFID="VID_Action" />
</RULE>
<RULE ID="VID_Action">
<L PROPID="VID_Action">
<P VAL="VID_Read">read</P>
</L>
</RULE>
</GRAMMAR>
maybe I'm adding my grammar as a resource the wrong way, I'm not sure (compiled, added the .cfg as a custom resource of type SRGRAMMAR)
anyone know what i'm missing here?
-- modified at 3:57 Thursday 5th January, 2006
|
|
|
|
|
In embedded systems there is a use of function pointer
But where can we use this in VC++.
Vikas Amin
Embin Technology
Bombay
vikas.amin@embin.com
|
|
|
|
|
CALLBACK's
Love Forgives--Love Gives--Jesus is Love  <marquee direction="up" height="50" scrolldelay="1" step="1" scrollamount="1" style="background-color:'#44ccff'">
--Owner Drawn
--Nothing special
--Defeat is temporary but surrender is permanent
--Never say quits
--Jesus is Lord
|
|
|
|
|
vikas amin wrote: In embedded systems there is a use of function pointer
But where can we use this in VC++
C++ virtual functions employes virtual table, which contains pointers to the virtual functions.
Think broadly, functions pointers can be designed and used in C/C++ and not neccessarly in Embedded system.
Callback functions are an example, Windproc is another example, many Win32 enumeration APIs employ function pointers.
-Prakash
|
|
|
|
|
Can u tell me some example application
where i can implemt such things.
Vikas Amin
Embin Technology
Bombay
vikas.amin@embin.com
|
|
|
|
|
vikas amin wrote: Can u tell me some example application
where i can implemt such things.
google them 
-Prakash
|
|
|
|
|
k thanks
Vikas Amin
Embin Technology
Bombay
vikas.amin@embin.com
|
|
|
|
|
Could someone please explain me the actual differences? My colleague says its possible for one to get the entire source code of an application if the debug mode output is shipped. MSDN says the compiler will generate Debugging symbols. What are they? Why it will ship the source code with the output? What happens internally when I change the active configuration (debug to release and vice versa) and build the project?
Many thanks,
Aljechin Alexander
|
|
|
|
|
release mode'd be the optimized one. while you are in development phase, you can use debugg mode. but once the program is perfectly ready , you shoud choose "release" mode. it will bring down the size completely.
>"My colleague says its possible for one to get the entire source code of an application if the debug mode output is shipped"
that's not true.
Check this one^
"But your mind is very complex, very tricky. It makes simple things complicated. -- that's its work. And for centuries it has been trained for only one thing: to make things so complicated that your life becomes impossible."- Osho
<marquee scrollamount="1" scrolldelay="1" direction="up" height="10" step="1">--[V]--
|
|
|
|
|
Thank you for reply. Quite an informative article.
Aljechin Alexander
|
|
|
|
|
Better to do development in Release mode only. In case any issues change to Debug and correct then back to Release. as the code base increases and an error occurred at the end of development when changed to Release mode ONLY....What you do?
Anilkumar
|
|
|
|
|
that's why then and there i take a copy of my project and test it with the Release Mode, mostly to check its size. and if i ever have problem in it. we have people here who can solve it at any point of time.so i never worry
"But your mind is very complex, very tricky. It makes simple things complicated. -- that's its work. And for centuries it has been trained for only one thing: to make things so complicated that your life becomes impossible."- Osho
<marquee scrollamount="1" scrolldelay="1" direction="up" height="10" step="1">--[V]--
|
|
|
|
|
T-1000 wrote: we have people here who can solve it at any point of time.so i never worry
Where ?
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
here means, only CP!! and mostly people lik you 
"But your mind is very complex, very tricky. It makes simple things complicated. -- that's its work. And for centuries it has been trained for only one thing: to make things so complicated that your life becomes impossible."- Osho
<marquee scrollamount="1" scrolldelay="1" direction="up" height="10" step="1">--[V]--
|
|
|
|
|
|
anilFirst wrote: error occurred at the end of development when changed to Release mode ONLY....What you do?
Testing, that’s how you solve this problem. You should be testing the code base as you add features.
In other words at the very least stop development every once and a while and build a release version. Test all of features possible to insure everything works.
ZeePain! wrote: This seems like one of those programs that started small, grew incrementally, building internal pressure, and finally barfed all over its source code sneakers. Or something.
thedailywtf.com[^]
|
|
|
|
|
When you're developing an application it is generally done using a debug build. The developer should build a release build from time to time to make sure no weird stuff is going on (release mode only bugs). Obviously the QA department should be testing the release builds. If you get a release only bug I have found that often the cause is related to the fact that in a debug build uninitialized locals are initialized to 0xCCCCCCCC (interestingly 0xCC in an __asm int 3 which is a breakpoint) but in release build no initialization is performed. The /GZ compiler option (Catch Release-Build Errors in Debug Build) can be a big help. Among other things this suppresses the 0xCCCCCCCC fill. This often makes the release only bugs show up in debug builds.
Steve
|
|
|
|
|
Hi,
does anybody know how I can setup a DLL having its own Dialogprocedure?
I have tried with LoadLibrary/GetProcadress etc. I am able to call any functions that
are within the DLL. But when i Try to do a DialogBox(....) it seems to be rather "complicated".
I keep getting the 1814 error (The specified resource name cannot be found in the image file)
I have tried to have all files available in same directory. No Luck. My Code looks like this:
HINSTANCE hDll;
FARPROC aDll;
int rc;
hDll = LoadLibrary((LPSTR)"test.dll");
if ((int)hDll < HINSTANCE_ERROR)
{
ErrMsg();
return(0);
}
aDll = GetProcAddress(hDll, (LPSTR)"TestDialog");
if (aDll==0)
{
ErrMsg();
return(0);
}
rc = DialogBox(hInst, (LPCTSTR)IDD_TEST_DIALOG, hWnd, (DLGPROC) aDll);
if (rc==-1)
ErrMsg();
And i have tried to use the MAKEINTRESOURCE instead. No luck.
Seems to be something with in connection with the Resourcefile, but I am not able to find the one thing that might help me.
We are using Visual C++ 6.0. But we are not using any C++ related programming at all.
It is all pure C-code but with exentsion of *.cpp
Rgds
Torben
|
|
|
|
|
torbeli wrote: rc = DialogBox(hInst, (LPCTSTR)IDD_TEST_DIALOG, hWnd, (DLGPROC) aDll);
try changing to
DialogBox(hDll , (LPCTSTR)IDD_TEST_DIALOG, hWnd, (DLGPROC) aDll);
-Prakash
|
|
|
|
|
Tried it. AND IT WORKED. for (i=0; i<1000; i++) Thanks!
One of those 2 days problem solved within 5 minutes having somebody else looking at it!
I, for some reason got confused about the explanation of the DialogBox.
"Handle to application instance". I saw that as the handle to my .exe and not the new DLL
But now I can see that it make sence to use the new handle that I just created with LoadLibrary.
int DialogBox(
HINSTANCE hInstance, // handle to application instance
LPCTSTR lpTemplate, // identifies dialog box template
HWND hWndParent, // handle to owner window
DLGPROC lpDialogFunc // pointer to dialog
Many thanks
Rgds
Torben
|
|
|
|
|
torbeli wrote: int DialogBox(
HINSTANCE hInstance, // handle to application instance
LPCTSTR lpTemplate, // identifies dialog box template
HWND hWndParent, // handle to owner window
DLGPROC lpDialogFunc // pointer to dialog
I think the documentation assumed that the dialog resource would be in the application.
Since in this case the dialog is in the dll, the the instance handle of the dialog should have been passed to the API.
torbeli wrote: for (i=0; i<1000; i++) Thanks!
You are welcome, I am glad that your problem is solved.
-Prakash
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
