|
Stefan_Lang wrote: Agreed on pretty much anything, except that I consider 100,000 lines rather small
Well C and C++ are pretty concise languages.
Of course you may feel 100,000 'small' (I feel it 'large'), however, probably 10^5 is the right order of magnitude.
Stefan_Lang wrote: and don't see any advantage in using C over C++ <layer>on smaller projects, as long as there are at least two developers working on it. OOP and the stricter syntax of C++ is great for avoiding errors based on misunderstandings of code use.
I think structured programming is better than OOP for small projects.
You may use C++ (as 'better C') with the structured programming paradigm, of course.
Veni, vidi, vici.
|
|
|
|
|
in terms of program output, yes, C can do everything C++ does. but C++ makes OOP much easier.
|
|
|
|
|
you can do all the things in C itself(Constructor, Destructor,
Polymorphism,
Templates every thing is possible in C) -
All the things that performed by compiler you should do by yourself.(for example constructor - init, etc)
Templates may be the thing - that really hard to performed - but generally macro can be used
Why C++ Instead of C - some of the features realized and checked by compiler.
but from the other side for C there are - small footprint,speed and etc.
like assembler and C.
At the end it is binary code.
|
|
|
|
|
C++ is an object oriented (OO) programming language. C isn't.
OO has been widely accepted as a technological idiom hus it can be presumed to have merit. Arguments claiming it is popularity contest ignore the fact that there are many 'popular' technologies that have short runs and which are then abandoned or even outright condemned. So to the extent there is any objective criteria for picking a technology idiom OO seems to accepted as being better.
Although one can program using OO in C it requires a great deal more manual attention to detail and additional code than doing it in C++.
Both of those make it more likely that additional bugs will show up.
Even more worrisome at lot of that additional code will involve pointers. And pointer bugs in C (and C++) are some of the more difficult bugs to find and thus cost more to fix.
Of course one could just use structured programming rather than OO. Although having done OO for many years I find it extremely difficult to think in structured terms for anything more than trivial bits of code. And at one time I used to do structured programming so at least I know how to do it.
|
|
|
|
|
i have i3 processor and windows7 os
i installed dev c++ which not suport graphic while i m devloping some graphical app. plzzzzzzzzzzzzz sugest me what can i do for graphics.
|
|
|
|
|
Brijesh_kumar wrote: i installed dev c++ which not suport graphic
As far as I know that's not true, why do you think so?
Veni, vidi, vici.
|
|
|
|
|
|
In VC++ and MFC:
is it possible to find out that one or more Windows Explorer windows are open?
|
|
|
|
|
I think you could use the EnumProcesses() function as described in this sample[^].
Unrequited desire is character building. OriginalGriff
I'm sitting here giving you a standing ovation - Len Goodman
|
|
|
|
|
I think that normally Explorer is permanently load in memory. My interest is that it opened a window or more windows,
|
|
|
|
|
Here is one way to do this -
Use EnumProcesses to enumerate all running processes.
For each process id returned, call GetProcessImageFileName to check if it belongs to explorer.exe
You will need to do OpenProcess on the process id to get its handle.
After you get the process id of explorer.exe, enumerate all open windows using EnumWindows.
For each window handle returned, use it in the function GetWindowThreadProcessId to check if it belongs to explorer.exe
This process of finding open explorer.exe windows could be time consuming.
Another way to do this would be to write a Browser Helper Object (BHO) which explorer.exe windows will load on startup.
In the BHO you can keep track of open explorer windows and more.
Here is some more information on BHOs - Browser Helper Objects: The Browser the Way You Want It[^]
Here is how to build a BHO using Visual Studio - Building Browser Helper Objects with Visual Studio 2005[^]
|
|
|
|
|
|
Hi,
You could create a ShellWindows object[^] and call get_Count();
Something like this:
INT GetExplorerCount()
{
LONG lCount = 0;
IShellWindowsPtr shell;
shell.CreateInstance(__uuidof(ShellWindows));
shell->get_Count(&lCount);
return lCount;
}
Don't forget to CoInitialize. Also keep in mind that Internet Explorer and Windows Explorer are integrated... you will need to add some code to filter out instances of IE. Control panel windows are also shell windows.
Best Wishes,
-David Delaune
|
|
|
|
|
I have dll where I am creating a dialog whihc is shown from the mfc client application. I loading this dll as an extension dll, then by implementing Do.Modal() function I am showing the dialog which has menus, toolbars,black model visualization screen. When trying to display this screen, it's crashing as debug ASSERT failed, at appcore.cpp
ASSERT(AfeGetThread()==NULL)
My App class is like this in the header file I have the App constructor and in .cpp file I have the construcor and also one instance of ViewApp as below
//MyViewApp.h
[code]
//Inside the class definition
MyViewApp(); //constructor dclaration
//outside the class definition
extern MyViewApp theApp;
[/code]
//MyViewApp.cpp
[code]
MyViewApp::MyViewApp()
{
}
MyViewApp theApp;
[/code]
It's crashing with this code (ASSERT failure in appcore.cpp), and when I am removing this constructor declaration and definition and also removing the one instantiation, then it's not crashing but coming out of the application, My Dialog GUI is not launching.
Please help me whats going wrong in this. Thanks a lot for help in advance.
|
|
|
|
|
My guess would be that you already have a CWinApp derivate instantiated while CWinApp (and so your MyViewApp since it is also a derivate of CWinApp) expects to be the one and only. Sad that in wincore.cpp there seems to be no comment whatsoever around those ASSERT-s to give you some additional information about what's wrong.
I suspect that you have MyViewApp inside the DLL and you are loading it into your application which already has a CWinApp derivate. If so, you should try displaying and handling your dialog in the "context of the original application".
Could this be it?
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> If it doesn't matter, it's antimatter.<
|
|
|
|
|
how can I do that please give me some hint..
I have one api exposed for mfc client called 'runAppli'
[code]
__declspec(dllexport)runAppli(CString fileName)
{
CDlgsViewDlg dlg(fileName, NULL);
dlg.DoModal();
return true;
}
[/code]
Using this I am calling the dll after loading.
So how can I
displaying and handling your dialog in the "context of the original application".
Please give me some hints.
|
|
|
|
|
Hard to say without seeing the whole picture, but...
Am i right that you have an application class instantiated in both the DLL and the app that loads it? If yes, do you need an application class inside the DLL? If yes, why? If no, try to get rid of it and see if it helps.
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> If it doesn't matter, it's antimatter.<
|
|
|
|
|
sujandasmahapatra wrote: It's crashing with this code (ASSERT failure in appcore.cpp)
appcore.cpp is a big place! Whenever you ask for help and say an ASSERT is failing for the love of god paste in the code around the ASSERT statement.
Steve
|
|
|
|
|
Is there any tool which can tell types of control is being used by runing software?
|
|
|
|
|
Not completely sure what you mean but try Spy++, it comes with Visual Studio, you can use it to find out what class windows/controls on windows have.
> The problem with computers is that they do what you tell them to do and not what you want them to do. <
> If it doesn't matter, it's antimatter.<
|
|
|
|
|
|
I made a tool window, and then made a treeview, with the tool window being the parent.
I also have a class, that populates the treeview with folder contents.
How do I access the treeview, to populate it?. What I mean is when I make the treeview in the main window, I can just call the HWND to connect to it, but when the treeview is a child of the tool window, I can't access it.
My goal is to have the treeview a child of the tool window, so they always stay together.
I had trouble creating the tool window successfully for awhile, and then I moved the code below to the main window cpp page. The tool window has it's own WndProc.
tbProjectExplorer = CreateWindowEx(
WS_EX_TOOLWINDOW,
szProjectExplorer_Class,
TEXT( "Project Explorer" ),
WS_POPUP | WS_SYSMENU | WS_THICKFRAME | WS_CAPTION | WS_VISIBLE,
winWidth - tvWidth, 1,
tvWidth, tvHeight,
hWnd,
NULL,
GetModuleHandle(0),
NULL
);
ShowWindow( tbProjectExplorer, SW_SHOW);
tvProjectExplorer = CreateWindowEx(
WS_EX_TRANSPARENT,
WC_TREEVIEW,
TEXT( "Project Explorer" ),
WS_VISIBLE | WS_CHILD | WS_BORDER | TVS_DISABLEDRAGDROP | TVS_TRACKSELECT | TVS_HASBUTTONS | TVS_EDITLABELS | TVS_SHOWSELALWAYS | TVS_SINGLEEXPAND,
0, 0,
tvWidth, tvHeight,
tbProjectExplorer,
(HMENU) IDM_PROJECT_EXPLORER,
GetModuleHandle(NULL),
NULL
);
SendMessage( tvProjectExplorer, WM_SETFONT, (WPARAM) hFont_lbl, FALSE);
ShowWindow( tvProjectExplorer, SW_SHOW);
|
|
|
|
|
I'm going to scape this idea and try something else.
|
|
|
|
|
For what it's worth, the way to achieve this task is to populate the TreeView inside the WindowProc for the tool window.
Just handle the WM_CREATE message of the tool window, then:
- create the treeView
- populate it
|
|
|
|
|
Thanks
I moved the WndProc for the Toolbar Popup, and the Treeview CreateWindow to the Class that populates the Treeview with Folder Contents in a new function. So now I just make the window, position it, and then create the treeview on the fly when loading the folder contents.
Sort of confusing of how it works, but I get it now.
Thanks for giving me the low down on it, was getting frustrated with it.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
