|
I would suggest option 3, a standard C-style DLL. Your VB.NET code can then access the functions through the P/Invoke mechanism[^].
Veni, vidi, abiit domum
|
|
|
|
|
#include<stdio.h>
#include<iostream.h>
void main()
{
cout<<"cout is executed"<
|
|
|
|
|
This is most probably a result of buffering of the output streams. I would bet that depending on the scenario/platform/compiler you could get different results with this very same code. Don't write such code or flush the streams if you want to guarantee write order.
|
|
|
|
|
Why are you trying to use both functions at once ? Is there any advantage ?
"If A is a success in life, then A=x+y+z. (Work is x; y is play; and z is keeping your mouth shut.)"
|
|
|
|
|
If you're using a standard C++ compiler then the cout should happen first. However as you're not using a standard compiler (cout and printf are members of the std namespace for a standard compiler) then all bets are off. Get a new compiler and see if you have the same problem.
|
|
|
|
|
What if you called "flush" at the end of each? Does it make a difference?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
Hi,
I have problems with 'WindowStateChange' events in my QWidget.
I have created a simple test widget with 3 buttons, to set window state:
Normal: showNormal();
MAX: showMaximized();
FullScreen: showFullScreen();
and trace window state events (QEvent::WindowStateChange).
When I change 'normal' <-> 'max' there is no problem (altough i receive twice 'max' event), BUT when i change 'max' <-> 'fullscreen' i receive this events:
'max' --> 'fullscreen'
----------------------------
0 No State
4 FullScreen
'fullscreen' --> 'max'
---------------------------
6 Maximized
4 FullScreen
6 Maximized
2 Maximized
with code like this:
state = windowState();
if ( state & Qt::WindowMaximized )
qDebug() << state << "Maximized";
So my widget has in both cases a strange flickering. That is, when 'max' --> 'fullscreen', it has an 'intermediate' "normal" state (0), and when 'fullscreen' --> 'max', it has several 'intermediate' states...
In my application, I must show/hide things when app is normal/maximized/fullScreened, so this flickering is really a problem.
Is it possible to do anything?
Thanks in advance,
Diego
|
|
|
|
|
When changing states in this way it is often best to suppress window updating during the transition, to avoid such flickering.
Veni, vidi, abiit domum
|
|
|
|
|
hello.,
I am new to visual studio.And I am trying to develop "how to send a mail from mfc dialog based application by using c++ language".So any body can tell me how to develope this project
|
|
|
|
|
|
|
See here.
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
|
Dear Friends,
I have been Updating CListCtrl very second. Now problem is, I can't able to drag scroll bar down. Every time List control gets updated and scroll automatically goes up. Can you anyone help me to come out from this problem
Thanks and Regards,
S.Shanmuga Raja
|
|
|
|
|
|
Writing a program to compute n series of Fibonachi (Recursive and No Recursive )
I wrote this for non recursive
#include <iostream>
using namespace std;
int Fibo(int number);
int _tmain(int argc, _TCHAR* argv[])
{
int i,sum,n,a1,a2;
cout<<"enter number : "<<endl;
cin>>n;
i=3;
sum=0;
if(n==1)
cout<<"1";
else if(n==2)
cout<<"1,1";
else
{
cout<<"1 ,1 ,";
a1=1,a2=1;
while (i<=(n))
{
sum=a1+a2;
cout<<sum<<" , ";
a1=a2;
a2=sum;
i++;
}
}
return 0;
}
And this for Recursive mode
int _tmain(int argc, _TCHAR* argv[])
{
int ii=1,nn=0;
cout<<"enter number:"<<n;
cin>>nn;
while(ii<=nn)
{
cout<<"\t"<<Fibo(ii);
ii++;
}
int Fibo(int number)
{
if((number==0) || (number==1))
return number;
else
return Fibo(number-1) + Fibo(number-2);
}
buw my question how can I compare these two methods for memory usage and their speed?
|
|
|
|
|
messages wrote: buw my question how can I compare these two methods for...their speed?
How about calling time() before and after?
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
No its not a programming project.its about data structure lesson an I have to compute it myself.
|
|
|
|
|
|
I have to compute it myself on the paper without any program. but I cant do it,could you help me please?
|
|
|
|
|
Then you are probably wanting to compute Big O notation, and you can find a really great answer here:
http://stackoverflow.com/questions/3255/big-o-how-do-you-calculate-approximate-it[^]
Big O notation was developed to give a machine independent view of the performance of a piece of code. Since "performance" depends greatly upon what you run it on (your code would be slow on a 386 but fast on a i7-4ghz), there needs to be a way to calculate relative performance. That is what Big O was designed for and it is a very difficult concept to grasp.
|
|
|
|
|
in first program you use more variable
|
|
|
|
|
Hello gurus,
I have posted few questions here basically pussyfooting around the real issue and hoping to learn more about Windows events in the process. So this is almost a re-post. Sorry.
The real issue is with waveOutWrite and assertion of the header flags _ particularity the “loop” WHDR_DONE flag.
I can use event but have no idea how it actually works.
I just cannot believe that the only “option” is plain while / do time wasting loop.
I am looking for this flag to signal end of audio in a few seconds, so I feel doing while loop for such long time is really goofy.
while((pcm[i].whdr.dwFlags & 1) != 1)
{
TRACE("\nWaiting.. %i ",mSeconds );
;
}
I am open to any other solution.
Thanks for your help.
Cheers
Vaclav
|
|
|
|
|
Vaclav_Sal wrote: I can use event but have no idea how it actually works.
...
I am open to any other solution.
Any other solution such as? 
"One man's wage rise is another man's price increase." - Harold Wilson
"Fireproof doesn't mean the fire will never come. It means when the fire comes that you will be able to withstand it." - Michael Simmons
"Show me a community that obeys the Ten Commandments and I'll show you a less crowded prison system." - Anonymous
|
|
|
|
|
I guess I was looking for "magic".
I will combine timer and the while loop and call it good.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
