|
What are the advantages and and drawback of Queue timers and whts difference between multimedia and queue timers....
|
|
|
|
|
|
Check out Stuart's links here[^].
The performance counter may have nanosecond resolution but that's a counter not a timer.
Unless you have special hardware, there's no timers on a PC with true 1 millisecond or better resolution,
but the multimedia/queue timers are close 
Mark
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.freetls.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
I have an SDI application, Which i split into 3 views(forms), based on selection of options in one form, want update the data in the other forms?
Any suggestions??
|
|
|
|
|
good morning.
if you use the mfc doc/view architecture pattern. the update of the views comes from the document by calling UpdateAllViews().
what you should do is:
when a form is changed / updated by the user it needs to inform the document about the changes that can then decide of the view updates.
hope this will help.
Franck.
|
|
|
|
|
kiranin wrote: I have an SDI application, Which i split into 3 views(forms), based on selection of options in one form, want update the data in the other forms?
Is it Dialog Frame.. you can use SetDlgItemText api to do so!
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
Never mind - my own stupidity is the source of every "problem" - Mixture
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
Support CRY- Child Relief and You/xml>
|
|
|
|
|
i want to send some messages to a specified subwindow in another process.
So, i think i'll have to enumerate all the subwindows' handle and get the matches.
But, how to enumerate all its subwindows?
regards
|
|
|
|
|
Hi,
I think in the following way... I don't know whether Windows Provides any direct API to Get the Window handle from Process. Just approach in the following way
1. Enumerate All the top level Windows In the system
2. Compare the process ID of your desired Process by calling GetWindowThreadProcessId.
3. Take the Windows handle of the matched process ID
4. Call EnumChildWindows to enumerate all the child Windows.
5. Do the necessary operations
-Sarath.
"Great hopes make everything great possible" - Benjamin Franklin
|
|
|
|
|
thanks. i have tested the method, it worked well.
modified on Monday, December 15, 2008 1:53 AM
|
|
|
|
|
Im on c++ and if i define a BYTE, WORD, DWORD or is there something larger that can hold more bites?
const BYTE NopTwoBytes[2] = {0x90, 0x90};
Now how much could hold word and dword and is there something more larger?
|
|
|
|
|
Your question doesn't make much sense 
The sizes of the Windows data types you mention are:
BYTE 1 byte
WORD 2 bytes
DWORD 4 bytes
DWORD64 8 bytes
The value 0x90 fits in one byte.
Mark Salsbery
Microsoft MVP - Visual C++
![Java | [Coffee]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/coffee.gif)
|
|
|
|
|
thnx for ur good answer it really clears things up
|
|
|
|
|
Probably the most complex but easy to use C++ construct is "sizeof". This little wonder will tell you the size of almost anything except Bill Gate's wallet. For example:
<br />
printf("The size of a BYTE = %d\n", sizeof(BYTE));<br />
<br />
struct MyStruct{<br />
int x;<br />
float y;<br />
char wibble[256];<br />
...<br />
};<br />
size_t MystructSize = sizeof(MyStruct);<br />
Well you get the idea. Quite an amazing little fellow is "sizeof"
Regards
T
|
|
|
|
|
Dear All;
I have a newbie question,
I need to implement a quick application which shows a video to a user. The user should be able to control the video via fairly simple speech commands (i.e. play, stop, go back, slow, fast).
I have no clue where to start from, I have done some programming in MFC and Visual C++.
Can anyone please provide advice, point articles ... ect, Please note that I need to implement the system as soon as possible so efficiency is not an issue.
Any help will be appreciated
Thanks
llp00na
|
|
|
|
|
As a starting point have a look at Microsoft Speech APIs[^]. This article[^] will be useful.
For capturing and showing video, you can use DirectX. Checkout this[^] and this[^] about how to do it. I hope now you have enough stuffs to start. isn't it?  Sorry, i thought you want to capture the video and then show it. Just ignore it.
Regards,
Jijo.
_____________________________________________________
http://weseetips.com[ ^] Visual C++ tips and tricks. Updated daily.
modified on Sunday, December 14, 2008 5:00 PM
|
|
|
|
|
Jijo,
I very much appreciate your help. Nope, I just need to show a video (It's already there). The main point is to control the video via speech commands.
I will give it a go and if I have any questions, I will be back
Many thanks
llp00na
|
|
|
|
|
We all have common modules/classes/includes that we use in various projects, but people structure their code differently. For example, you could:
1) Have folders called Include and Modules, which contain the common code and then add search paths to your development environment so they get picked up.
2) Like (1), but for every project you copy over the includes/modules you require to the project folder (eg. Common\Include, Common\Modules, or just Common), and then use these copies.
(1) has the advantage that any fixes/changes made to the includes/modules are immediately propogated to the projects that use them, without the need for any other work. The downside is that one of these fixes/changes may break a project (eg. due to it relying on certain behaviour)
(2) has the inverse of the pros and cons of (1).
Are there any other ways of working that you use ?
Which model do you follow, and why ?
|
|
|
|
|
My opinion is: Don't copy header files - that's evil. Reference them.
|
|
|
|
|
What about modules/classes ?
|
|
|
|
|
I design my projects so that lower-level, possibly common, modules go into separate DLL projects.
Architecture's the name of the game...
|
|
|
|
|
I'll go for (1) i.e. refer the common header files rather than making a copy of it and use. Because, as you said, if you copy the files, you could avoid crashes or compilation errors during development. But infact you are not avoid it but simply accumulating. All the compilation errors and crash will popup once you start to integrate will the latest common and you'll be in real trouble in sorting out the bugs.
So better refer the common modules and incase of any trouble in latest common source, just get the old version from your version control and work with it until the guys fixes the latest common. 
Regards,
Jijo.
_____________________________________________________
http://weseetips.com[ ^] Visual C++ tips and tricks. Updated daily.
|
|
|
|
|
Hello everyone,
For SetWaitableTimer and CreateWaitableTimer, I have the confusions (even after
Google, I can not find satisfied answers, seems the samples are very few and MSDN
description is fuzzy).
My questions are,
1. For API SetWaitableTimer, what are the meaning and function of parameters
pDueTime and lPeriod?
http://msdn.microsoft.com/en-us/library/ms686289.aspx
2. For API CreateWaitableTimer, what is the function and meaning of parameter
bManualReset (what is the different between setting it to true and setting it to false)?
http://msdn.microsoft.com/en-us/library/ms682492.aspx
thanks in advance,
George
|
|
|
|
|
- Look at this page[^]:
pDueTime is a pointer to a FILETIME that indicates how long (from now) until the timer expires.lPeriod shows the timer's period, i.e. the time between timer expirations
If *pDueTime was set to 10 milliseconds and lPeriod to 5 ms, the timer would fire 10, 15, 02, 25... milliseconds from now. - If a timer has
bManualReset set to TRUE, then you have to call SetWaitableTimer to make it start measuring time again after it expires. If a timer has bManualReset set to FALSE, then it becomes active again once a WaitForSingleObject or WaitForMultipleObjects call has been activated by the timer expiry. As with all these things, why not write a little program to experiment with it? That's the best way to work out what it does if the documentation's not entirely clear.
|
|
|
|
|
Thanks Stuart,
I would like to write simple samples until I understand the concept.
1.
Stuart Dootson wrote: If a timer has bManualReset set to TRUE, then you have to call SetWaitableTimer to make it start measuring time again after it expires.
You mean for example, I set the lPeriod to 5 ms, and then active the timer, then the timer only activate after 5ms once? Not active after 5ms, 10ms, 15ms, etc?
2.
Stuart Dootson wrote: a timer has bManualReset set to FALSE, then it becomes active again once a WaitForSingleObject or WaitForMultipleObjects call has been activated by the timer expiry.
I am confused about what do you mean, could you show some pseudo code or refer some samples? I did not find any good samples from MSDN.
regards,
George
|
|
|
|
|
George_George wrote: You mean for example, I set the lPeriod to 5 ms, and then active the timer, then the timer only activate after 5ms once? Not active after 5ms, 10ms, 15ms, etc
I don't think bManualReset has any effect when you have a non-zero period. Not sure, though. As I said, try it and see!
George_George wrote:
Stuart Dootson wrote:
a timer has bManualReset set to FALSE, then it becomes active again once a WaitForSingleObject or WaitForMultipleObjects call has been activated by the timer expiry.
I am confused about what do you mean, could you show some pseudo code or refer some samples? I did not find any good samples from MSDN.
How about this?[^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
