|
I bet $10US that you had the wrong font selected into the DC. ? But yes, please share what was going wrong.
Chris Richardson
|
|
|
|
|
Heh, no. That was the first thing I checked, because I've been burnt by that one before. 
See reply to Gary if you're really interested in how stupid I can be. 
(Jörgen, not logged in)
|
|
|
|
|
Jörgen Sigvardsson wrote:
Nevermind me. I'm an idiot.
Yeah, we all know that  But please tell us what you did this time!
Ryan "Punctuality is only a virtue for those who aren't smart enough to think of good excuses for being late" John Nichol "Point Of Impact"
|
|
|
|
|
Please see my reply to Gary for an insight into the idiot's mind. 
(Jörgen, not logged in)
|
|
|
|
|
I've heard two set of stories each saying the opposite. Which one is true?
If it turns out that both versions can be on the same machine, what's the installation procedure like?
Thanks for any insight into this matter.
William
Fortes in fide et opere!
|
|
|
|
|
There's no conflict between VC6, VS.NET 2002 and VS.NET 2003. Not in my experience anyway.
The installation procedure is nothing special, just the ordinary next, next, next, tweak options, next, finish. Although, I did install the newer versions before VC6, so I can't speak of what happens if you install the newer versions after VC6.
--
Schni Schna Schnappi! Schnappi Schnappi Schnapp!
|
|
|
|
|
I installed 2002 after VC6, no problems at all.
"You're obviously a superstar." - Christian Graus about me - 12 Feb '03
"Obviously ??? You're definitely a superstar!!!" mYkel - 21 Jun '04
Within you lies the power for good - Use it!
Honoured as one of The Most Helpful Members of 2004
|
|
|
|
|
Thanks for replying!
The reason I was told of the incompatibility of both versions, was that the version being installed would overwrite (or partially overwrite) some folders of the previously existing version, which you'll not find out until later when you run certain applications that were created under the previous version.
Because I have hundreds of applications developed under VC6, I would hate to fine out that some of them may experience certain anomalies due to the concurrency of a second version.
William
Fortes in fide et opere!
|
|
|
|
|
Generally speaking, it's OK but there may well be some obscure problems. At the place I left a while back I was told that merely having VC++ 7.1 installed broke their existing VC6 app. However, their app. was very complicated - involvong VC6, COM/ATL, VB, Tuxedo, etc.
Kevin
|
|
|
|
|
Thanks for replying!
I appreciate it.
William
Fortes in fide et opere!
|
|
|
|
|
I've had side-by-side installations of VC6, VS.NET 2002, and VS.NET 2003 on several machines. They coexist nicely, and don't interfere with one another. I've not heard anything one way or another about VS.NET 2005 (the beta).
The only thing to be careful of is that they will upgrade their predecessor's project files if you're not careful, and the upgrade is one way (although there are converters out there, at least to revert from .NET 2003 back to 2002).
Software Zen: delete this;
|
|
|
|
|
Thanks for replying.
Does the upgrade to those project files occur only when you activate those particular applications, or does it happen as part of the installation process (that it upgrades ALL such files)?
Perhaps that's what those people were talking about when they mentioned about files getting written over.
William
Fortes in fide et opere!
|
|
|
|
|
WREY wrote:
Does the upgrade to those project files occur only when you activate those particular applications, or does it happen as part of the installation process (that it upgrades ALL such files)?
The update only occurs when you open the project into the new compiler. It does ask you if you want to update the files however.
Ant.
I'm hard, yet soft.
I'm coloured, yet clear.
I'm fruity and sweet.
I'm jelly, what am I? Muse on it further, I shall return! - David Walliams (Little Britain)
|
|
|
|
|
Thanks for replying, and expressing that bit of clarity.
I appreciate it.
William
Fortes in fide et opere!
|
|
|
|
|
VS.NET 2005 is much smarter than the previous IDEs regarding "conversions". When you double click a solution, it will launch a "version selector". So based on the contents of the solution file, it will start the correct IDE. Very nice feature indeed. It also shows the version number of the IDE used to create the solution file, in the icon label.
I think that happened in Beta 2. Someone in the VS.NET department should get a raise.
|
|
|
|
|
Cool.
William
Fortes in fide et opere!
|
|
|
|
|
Howdy im new at this website witch i visited tnx to a college bud recomendation. Pls forgive my english im from Argentina
Very well this are my questions:
I need help at using qsort algorithm witch is included with borland 5 at stdlib.h
Help says
void qsort(void *base, size_t nelem, size_t width, int (_USERENTRY *fcmp)(const void *, const void *));
so that is basic chineese to me, i dont get this out look:
i call the function with this, example:
qsort( name_of_array , a_number(for what), NumberOfelementOfTheArray, a_wierd_function_IdontGet )
any ideas??
Second, i need any help i could get in how to get a window list working on borland 5, Thanks to anyone who can help. Saludos!
|
|
|
|
|
Look here[^] for an explanation and sample of the qsort algorithm.
"You're obviously a superstar." - Christian Graus about me - 12 Feb '03
"Obviously ??? You're definitely a superstar!!!" mYkel - 21 Jun '04
Within you lies the power for good - Use it!
Honoured as one of The Most Helpful Members of 2004
|
|
|
|
|
tnx that did help, but i still do not understant the last parameter...
|
|
|
|
|
It's the comparison routine that qsort() will call several times during the sort, passing pointers to two array elements on each call.
|
|
|
|
|
Does Microsoft ever advocate changing MFC source code ?
If Yes in what case ?
|
|
|
|
|
What? i don't understand your question...
cya !
|
|
|
|
|
I would not change MFC's source code, anyway, we don't really have to it, only some part of it for debugging purpose.
but again, what is the question ?
Maximilien Lincourt
Your Head A Splode - Strong Bad
|
|
|
|
|
I think it is not a good idea to change MFC library, because it makes your code extremely unportable and maybe unstable.
I think there are several other alternatives like:
1) Derive an object and override some functions
2) Build a new object similar to an MFC object (it is alowed to "learn" by reading MFC source code)
3) Hook some GUI object
4) Etcetera...
Best regards,
Jaime.
|
|
|
|
|
MFC is well tested code, and to the most extent reliable( ignore some of the bugs, because everyone ll do some mistakes). obviously MS encourages you to add extra functionality to the MFC classes by deriving the classes and overriding the classes. It provides the only basic framework. With the standard classes that it provides, its almost impossile to create the look and feel application in the crazy GUI world
VC++ programmer
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
