|
Maybe the abc.cpp is still in the solution explorer?
In the solution explorer, open your project, open "Source", mark abc.cpp and hit the "del"-key.
Do the same under "Headers".
Let's think the unthinkable, let's do the undoable, let's prepare to grapple with the ineffable itself, and see if we may not eff it after all.
Douglas Adams, "Dirk Gently's Holistic Detective Agency"
|
|
|
|
|
Yes, yes I did that also, no abc.h and abc.cpp is not displayed in the work space
|
|
|
|
|
how come? right click on error list then choose go to location, this should bring you to the error location...
couldn't be like that... a bit strange...
|
|
|
|
|
What is the difference between a timer and a thread ?
Thanks,
Appu..
"Never explain yourself to anyone.
Because the person who likes you does n't need it.
And the person who dislikes you won't believe it."
|
|
|
|
|
a timer is a component that raises an event after a certain interval has passed and runs on the main thread. It just goes of somewhere and then after the specified inteval runs code that you would have specified.
A thread on the other hand is something totally different. A thread simply put is a process of execution. All applications execute on at least one thread.
Somethings seem HARD to do, until we know how to do them.
 _AnShUmAn_
|
|
|
|
|
Thanks.. Can i have a detailed description.
Appu..
"Never explain yourself to anyone.
Because the person who likes you does n't need it.
And the person who dislikes you won't believe it."
|
|
|
|
|
What do you need excatly?
|
|
|
|
|
_AnShUmAn_ wrote: a timer...runs on the main thread.
Timers are not limited to the main thread. They run on whatever thread they were started in.
"Love people and use things, not love things and use people." - Unknown
"The brick walls are there for a reason...to stop the people who don't want it badly enough." - Randy Pausch
|
|
|
|
|
 It is almost impossible to answer the question because they are two completely different things. That's a bit similar as asking "What's the difference between a table and an apple ?"
A timer is something that is fired at regular intervals and a thread is something that lets you execute code in parallel.
|
|
|
|
|
Thanks..
I got it.
Suppose If I have timer that gets fired every 1000 ms.
and the timer is calling a Sleep() for 10000 ms.
How this is going to behave ?
Appu..
"Never explain yourself to anyone.
Because the person who likes you does n't need it.
And the person who dislikes you won't believe it."
|
|
|
|
|
If you have only one single thread, it means that your application will hang when you are sleeping. If it is a user interface, it will be frozen during 10 seconds and each time new sleep messages will be put in the queue. It means that it won't react anymore (or very slowly, every 10 seconds, just the time to process the messages that are in the queue).
|
|
|
|
|
My question here is
Suppose in a timer function that gets fired every 1000 ms, another function fun() gets called,which takes some 10000ms to finish execution.
How this is handled ?
Every 1 s, the fun() gets called or it continues the previous execution every 1 s.
Thanks
Appu..
"Never explain yourself to anyone.
Because the person who likes you does n't need it.
And the person who dislikes you won't believe it."
|
|
|
|
|
No, I already answered your question: it will be called every 10 msec because you have only one single thread. A timer only post a message to your application message queue, which is handled in your main thread. It means that if your main thread is stuck 10 seconds in a specific function, no messages will be processed from the queue (even your timer message). So, your function will be called every 10 seconds only. There's no magic: if there's only one thread, you can only have one piece of code executed at a given time.
|
|
|
|
|
Ok.. I got it..
It is now clear.
Thanks
Appu..
"Never explain yourself to anyone.
Because the person who likes you does n't need it.
And the person who dislikes you won't believe it."
|
|
|
|
|
NiceNaidu wrote: Suppose If I have timer that gets fired every 1000 ms.
and the timer is calling a Sleep() for 10000 ms.
How this is going to behave ?
Why not write a program and find it out? 
Many are stubborn in pursuit of the path they have chosen, few in pursuit of the goal - Friedrich Nietzsche
.·´¯`·->Rajesh<-·´¯`·.
[Microsoft MVP - Visual C++]
|
|
|
|
|
How can I change the text of a menu item run-time if I have a CMenu* pointer?
There is sufficient light for those who desire to see, and there is sufficient darkness for those of a contrary disposition.
Blaise Pascal
|
|
|
|
|
UINT id = m.GetMenuItemID(0);
m.ModifyMenu(ID_FILE_NEW32771, MF_BYCOMMAND, ID_FILE_NEW32771, _T("Hello"));
|
|
|
|
|
Thanks 
There is sufficient light for those who desire to see, and there is sufficient darkness for those of a contrary disposition.
Blaise Pascal
|
|
|
|
|
You're welcome.
|
|
|
|
|
Hi @ all,
i´m trying to send an RTP Packet to a Server. My Packet Structure looks like this:
struct rtppacket
{
unsigned int version:2;
unsigned int padding:1;
unsigned int extension:1;
unsigned int csrcccount:4;
unsigned int marker:1;
unsigned int payloadtype:7;
unsigned int sequencenumber:16;
u_int32_t timestamp;
u_int32_t ssrc;
u_int32_t csrc[1];
void* datap;
int datalen;
};
that´s my way to fill and send the structure:
m_rtpPack.version = 2;
m_rtpPack.sequencenumber = 1;
m_rtpPack.csrc[0] = 0;
m_rtpPack.csrcccount = 0;
m_rtpPack.extension = 0;
m_rtpPack.marker = 1;
m_rtpPack.payloadtype = 0;
m_rtpPack.padding = 0;
m_rtpPack.ssrc = 0;
m_rtpPack.timestamp = GetTickCount();
...
...
m_rtpPack.datap = szBuffer;
m_rtpPack.datalen = sizeof(szBuffer);
nSend = sendto(m_Socket, (char*)&m_rtpPack, sizeof(m_rtpPack), 0, (SOCKADDR*)&m_saRemote, sizeof(SOCKADDR));
That doesn´t work. If I take a look of the RTP flow with packetyzer it can read the header information of rtp and the server can´t do something with incoming.
The structure padding compiler option is Zp1. What I do false?
Greetzs
Crazydogg
|
|
|
|
|
The problem is that you will send the pointer to the data (datap) and not the data itself. A pointer is 4 bytes (depending on the platform) that points to the data. Thus, when you send your structure, you will send the header correctly but for the data, you will send only the 4 bytes of the pointer. Same problem with calculating the size of the structure: it is always the same, no matter how large the buffer is (its not in the structure, it is only pointed by a member of your struct).
To fix the problem, you need to send it separateley: first the structure, as you already did (don't care about the data pointer yet), then the data buffer. On the receiver side, when you receive the data, you create a new buffer (in datap) and copy the data in it.
|
|
|
|
|
Ok I understand the problem, but I can´t influence the server side. It´s an extern Asterisk server. Because of that I have to send header and data together.
|
|
|
|
|
Is the buffer a fixed size buffer (e.g. always 1024 bytes) ?
If yes, then simply declare the buffer inside the structure:
struct MyStruct
{
...
...
unsigned char datap[1024];
...
};
|
|
|
|
|
The buffer is smaller in most cases but maximum is 1024.
I will try it so. Thank you
|
|
|
|
|
It also depends of what the serve epxects. But as the datasize field is after the data, it probably means that the server always expects 1024 bytes because it is impossible for it to know where the data field stops and where the datasize field starts.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
