|
There's some wacky functions in that list. It's nice of Microsoft to give us such a varied list of functions, they've helped me out a lot.
But, there's functions in there that I can't figure a use for...
Like, why would someone use PathUndecorate[^] or PathMakePretty[^]
The other side, there's some great stuff in there too. PathAppend, PathAddBackslash come to mind.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br />
Peter Weyzen<br />
Staff Engineer<br />
<A HREF="http://www.soonr.com">SoonR Inc -- PC Power delivered to your phone</A>
|
|
|
|
|
PathUndecorate could be very usefull when copying files out of the IE cache. PathMakePretty is wierd, mostly because it only works on all uppercase path. I only discoverred this wonderfull collection of functions within the last month, after doing nearly all my path manipulations by hand for 20 years, except for splitpath/makepath from the CRT.
|
|
|
|
|
I need to open some window application ( Form ) from some other application.
I know the name of the other ( father ) window that need to create and open my window - but that all ... i don't know anything else about the other window.
How can i do it ?
Thanks for the help .
|
|
|
|
|
Do you want to show these windows or want to create them of other application?
|
|
|
|
|
I want to create them and show them from the other application.
|
|
|
|
|
If you want different CFormViews in just one Application, this[^] will help you.
If you want an Application to call another application, then you should use ShellExecute or thread functions.
Greetings.
--------
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
|
|
|
|
|
I think he needs to make and show forms of other applications.
|
|
|
|
|
Hi all,
Is there anyone who knows add-in for VC2005 to make snapshot of current project before serious changes made to the project?
Regards,
L.
|
|
|
|
|
How about using a source control system ? That's what they are (partly) made for.
|
|
|
|
|
I agree -- version control is what you need! Most of us can't live without it...
Commonly what you do - is store all of your code and project materials in it's special database. As you make changes, you check-in those changes to the master copy -- which lives on a server.
You can also create branches -- which basically makes a snapshot of the master. You can then work on the snapshot, make changes and check them back in without altering the master.
Once your happy with your changes, you merge them back into the master... incorporating these changes in one transaction.
Within the masters, you can record labels (put down a marker) and also do all kinds of reporting -- like who changed what or when did this change...
There's various products out there -- some of them are more difficult to manage. I currently use SVN... have used CVS and Microsoft SourceSafe.... SVN is the best so far... but any idiot could install a SourceSafe system...
I know there's other choices out there.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~<br />
Peter Weyzen<br />
Staff Engineer<br />
<A HREF="http://www.soonr.com">SoonR Inc -- PC Power delivered to your phone</A>
|
|
|
|
|
Dear all
i have the following class header
#include "stdafx.h"
#include < iostream >
using namespace std;
class test
{
private:
int n1;
int n2;
public:
test(int n1,int n2);
output(std::ostream& outs);
};
VS 2005 display the following error
error C4430: missing type specifier - int assumed. Note: C++ does not support default-int
for
output(std::ostream& outs);
any tips
i searched the net and i didn't find any solutions
thanks all
bye
|
|
|
|
|
you have to have a return type for your class methods.
Use void if there's no applicable type...
class test
{
private:
int n1;
int n2;
public:
test(int n1,int n2);
void output(std::ostream& outs);
};
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
more than 3 hours try to solve this problem and then at the end IT IS VOID LOL
thanks alot
|
|
|
|
|
Adore C++ wrote: more than 3 hours try to solve this problem
Next time try this[^]... where the fourth entry is this[^]
it should prove to be faster.
|
|
|
|
|
Hi Guys
I want to associate a button when clicked to connect to a port so that i can send data to an extenal device. I really don't have the idea even where to start, so if anyone can maybe refer me to a site i can read about that or offer some advice would really save me.
Thanks guys.
Wamuti: Any man can be an island, but islands to need water around them!
Edmund Burke: No one could make a greater mistake than he who did nothing because he could do only a little.
|
|
|
|
|
Wamuti wrote: I really don't have the idea even where to start
This could help[^]
|
|
|
|
|
|
So I have following problem (all of these are Win32 app, all MFCs, Visual 2005 applications, C++)
Application A (third-party) uses two of our dlls (which are plug-ins for A), let's say AppAplug1.dll and AppAplug2.dll. These dlls use another of our dll, Common.dll.
Version 1.0 of Common.dll is installed in AppAplug1.dll's directory, and is loaded using /DELAYLOAD by AppAplug1.dll
Version 2.1 of Common.dll is installed in AppAplug2.dll's directory, and is loaded using /DELAYLOAD by AppAplug2.dll
When I debug into AppAplug1.dll code, some function calls jumps into Common.dll Version 1 and sometimes into Common.dll Version 2.1, which brings upp following problems: some static variables are then initialised by a function call in Version 2.1, and used in Version 1, in which they are then not initilaised -> bad !
I thought processes would have their own memory space, how come I can "exchange" data like this ? How can I avoid that ?
Thanks,
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Do not feed the troll ! - Common proverb
|
|
|
|
|
Rage wrote: How can I avoid that ?
can't the 2 DLLs using Common.dll use the same version, so, mount a one a only version of the DLL ?
|
|
|
|
|
Nope, because customers have different versions of the .dlls.
Plus, this would not solve the problem: I tested it with App2 using the same version of the .dll (but not the same .dll, so two .dlls in two different locations), and it failed, since App1 and App2 seem to access randomly to either the one or the other Common.dll.
C'est la merde.
~RaGE();
I think words like 'destiny' are a way of trying to find order where none exists. - Christian Graus
Do not feed the troll ! - Common proverb
|
|
|
|
|
hum, yes, i was thinking indeed to point to the same and only DLL file (by saying "version")...
Rage wrote: C'est la merde.
bon courage, j'abdique ! lol
|
|
|
|
|
Rage wrote: Dll hell
I read this Dell Hell at first !!
|
|
|
|
|
Now I have a new name for our server graveyard, thanks.
Nothing is exactly what it seems but everything with seems can be unpicked.
|
|
|
|
|
Rage wrote: I thought processes would have their own memory space, how come I can "exchange" data like this ?
You've only mentioned one process. DLLs are not processes -
they are mapped into a process' memory space.
This is truly DLL hell, but it seems like it could have been avoided.
A true "common" dll should be just that - common. Why is there more
than one version, in more than one place?
Mark
Mark Salsbery
Microsoft MVP - Visual C++
|
|
|
|
|
Rage wrote: I thought processes would have their own memory space, how come I can "exchange" data like this ? How can I avoid that ?
As Mark said, they do have unique memory spaces. You only have one app, therefore only one process space. Your problem is that you've managed to get two DLLs with the same names and the same entry points loaded into the same process space. What's a poor OS to do? I'm not surprised it's confused.
The "correct" solution to this is to have one and only one copy of your DLL (version 2.1) on the system (in system32 preferably) and to maintain support for version 1.0 inside your 2.1 DLL by using new names for functions that have changed or been added since 1.0. You know, like all those FunctionNameEx routines in the windows DLLs.
If you have functions with the same names that do different things in your two versions on an existing system, and the two plugin DLLs depend on the different functioning of the same-named functions and are trying to find a fix without making a coding change, IMHO you are up the proverbial creek without the proverbial paddle. You've got to resolve the ambiguity of which DLL / which function is which and I can't see a solution without a code change.
However, your third-party has obviously come across the problem and will be expecting some fix from you so you have the perfect opportunity to make that code change and fix the root issue.
Judy
|
|
|
|