C / C++ / MFC

Re: How to enable sharing resources from an extension DLL?

20-Sep-01 11:46

Why do you have GOLInit function? Did you have any problems with CDynLinkLibrary created in DllMain?

Tomasz Sowinski -- http://www.shooltz.com

20-Sep-01 11:53

To allow for both implicitly & explicitly linked DLLs chain correctly.

Anyway, i tried moving the code to DLLMain & also tried doing at both places (DllMain as well as a separate exported function) with the same result. Same strangeness! still Confused | :confused:

subsplitter of splitter

Peter Molnar20-Sep-01 10:11

Peter Molnar

20-Sep-01 10:11

Sirs,

I am about to create an SDI splitter app but
there are some unclear points to me.

First I created a splitter with 1 row and 2 coloums (both coloums
with a CView in them, CFirstView
and CSecondView) by using

m_wndSplitter.CreateStatic and

m_wndSplitter.CreateView

in the CMainFrame::OnCreateClient.

So far so good.

Now I want to create in CSecondView two further
rows, and place a property sheet in one of them.

Problem 1 is that being a view there is no CFrameWnd::OnCreateClient
within CSecondView, where CreateStatic
and CreateView are supposed to be placed.

Problem 2 is how to create a property sheet with
CreateView, or at least a CDialog on
which property pages could be placed.

I also tried (for 1 row 2 cols) deriving
from CFormView instead of CView but
it asserts ("Invalid Dialog Template"
in MFC/ViewForm.cpp). With CPropertySheet also
asserts ("Panes can be a CWnd but are usually CViews"
in MFC/Winsplit.cpp).

By deriving from CWnd
or CDialog it does not even compile (RUNTIME_CLASS:
"classCFirstView is not a member of CFirstView"
in m_wndSplitter.CreateView )

Your experience would be highly
appreciated. Thank you in advance.

Bunburry

Education is an admirable thing but it is well to remember from time to time that nothing that is worth knowing can be taught (O.Wilde)

Re: subsplitter of splitter

Oscar Vazquez21-Sep-01 11:35

Oscar Vazquez

21-Sep-01 11:35

I never trie a Property, but for any other king of view this code work ok.

BOOL CChildFrame::OnCreateClient( LPCREATESTRUCT /*lpcs*/,CCreateContext* pContext)
{
// create a splitter with 1 row, 2 columns
if (!m_wndSplitter.CreateStatic(this, 1, 2))
{
TRACE0("Failed to CreateStaticSplitter\n");
return FALSE;
}
m_wndSplitter.SetScrollStyle( 0 ); //Use frame scroller

// Create view in first splitter Row 0, COl 0
if (!m_wndSplitter.CreateView(0, 0,
RUNTIME_CLASS(CArchivoTreeView), CSize(130, 50), pContext))
{
TRACE0("Failed to create second pane\n");
return FALSE;
}

// Create nested splitter in second col of first splitter
if (!m_wndSplitterRE.CreateStatic(
&m_wndSplitter, // our parent window is the first splitter
2, 1, // 2 rows 1 col
WS_CHILD | WS_VISIBLE | WS_BORDER | WS_HSCROLL, // style, WS_BORDER is needed
m_wndSplitter.IdFromRowCol(0, 1) ))
{
TRACE0("Failed to create nested splitter\n");
return FALSE;
}
m_wndSplitterRE.SetScrollStyle( 0 );

// Create view in first row of second splitter
if (!m_wndSplitterRE.CreateView(0, 0,
RUNTIME_CLASS(CHeaderInfo), CSize(80, 65), pContext))
{
TRACE0("Failed to create first pane\n");
return FALSE;
}

// Create view in second row of second splitter
if (!m_wndSplitterRE.CreateView(1, 0,
RUNTIME_CLASS(CFileView), CSize(0, 0), pContext))
{
TRACE0("Failed to create second pane\n");
return FALSE;
}

// TODO
}

Window paint problem when using CPropertySheet with CComboBox

20-Sep-01 10:07

I've created a CDialog based application from which I call a property sheet containing a single property page. This property page contains a single CComboBox control set in dropdown mode. If I display the property sheet and drag it to a position where it overlaps both the application dialog and the background, a portion of the property sheet is filled with whatever lies in the background. This behavior is seen only the first time the property sheet is displayed(but each time the application is restarted) and when "Show window contents while dragging" option of the Control panel/display setting/plus! is disabled!!!

====How to reproduce===
Ok, here's the "for dummies" procedure.

1) Create an MFC AppWizard project named "test"
2) Make it dialog based and keep all other default settings
3) Open the dialog
4) Remove the OK/CANCEL buttons and the "TODO:..." static
5) Set the dialog size to 500x250 (yes, if too small, problem won't show)
6) Insert a new button (IDC_BUTTON1)
7) In class Wizard, add a onButton1() function in CTestDlg
8) Insert an IDD_PROPPAGE_MEDIUM dialog in your project
9) Delete the "TODO:..." static of the property page dialog
10) Add a combo box control to the property page dialog
11) In class wizard, create the new class "cproppage" based on CPropertyPage and dialog IDD_PROPPAGE_MEDIUM
12) Using class wizard, create a new class "cpropsheet" based on CPropertySheet.
13) In the TestDlg.h file, add #include "cproppage.h" and #include "cpropsheet.h"
14) In the TestDlg.h file, add private member "cproppage proppage" to class CTestDlg
15) In the TestDlg.cpp file, in the onButton1() function, add:
cpropsheet lDlg("test");
lDlg.AddPage(&proppage);
lDlg.DoModal();

16) That's it! Compile it, run it.
17) Do not move the application dialog
18) Press the button (the property sheet is displayed)
19) Drag the property sheet such that it overlaps the dialog border (try half/half)
20) Release mouse button
21) Voila! Portion of property sheet refreshed with background!!!!

If a control other than the Combo box is used, there is no problem...

What is happening?

Thanks to all!

==Carl==

Strange CTreeCtrl behavior

Ken Goguen20-Sep-01 9:16

20-Sep-01 9:16

I have a strange one.

I have my own CTreeCtrl for doing multi-select. When build/run a debug version it works just fine. When I build/run a release version, my tree nodes get populated, but I do not see any + on the parent nodes and cannot expand them to see the children. But I can do all that in the debug version without a problem.

Any Ideas? Eek! | :eek:

-kg

// *** TreeView
CMulSelTreeCtrl* pMyTree = (CMulSelTreeCtrl*) GetDlgItem(IDC_TREE1);
ASSERT(pMyTree != NULL);
pMyTree ->DeleteAllItems();
pMyTree ->ModifyStyle(NULL, TVS_HASBUTTONS | TVS_HASLINES | TVS_LINESATROOT | TVS_SHOWSELALWAYS);

// Associate the image list with the tree control.
pMyTree ->SetImageList(pilMyTree, TVSIL_NORMAL);

TVINSERTSTRUCT tvInsert;
tvInsert.hParent = NULL;
tvInsert.hInsertAfter = NULL;
tvInsert.item.mask = TVIF_TEXT | TVIF_CHILDREN;

// *** TreeView
tvInsert.item.pszText = _T(buffer);
HTREEITEM hTreeItem = pMyTree ->InsertItem(&tvInsert);

Ken Goguen
Principle Design Engineer
EMC Corporation

Michael Dunn20-Sep-01 9:28

Michael Dunn

20-Sep-01 9:28

Init your structs to zero before using them:
TVINSERTSTRUCT tvInsert = {0};

--Mike--
http://home.inreach.com/mdunn/
Ford: How would you react if I said that I'm not from Guildford after all, but from a small planet somewhere in the vicinity of Betelguese?
Arthur: I don't know. Why, do you think it's the sort of thing you're likely to say?

Ken Goguen20-Sep-01 9:50

20-Sep-01 9:50

Good practice, but didn't resolve the problem.

-kg

Ken Goguen
Principle Design Engineer
EMC Corporation

Tomasz Sowinski20-Sep-01 9:29

20-Sep-01 9:29

The code you've posted only inserts a root item. And TVIF_CHILDREN flag is ignored during inserts. It works when you're getting information about the item with GetItem.

BTW: why are you using a InsertItem overload that takes TVINSERTSTRUCT - there are more convenient versions.

Tomasz Sowinski -- http://www.shooltz.com

Ken Goguen20-Sep-01 9:53

20-Sep-01 9:53

There is additional code that adds the other nodes, but using message windows I've been able to determine that the expand problem occurs on the first insert.

Only using the overload as it was part of an old example I began with. Do you think this could be part of the problem?

-kg

Ken Goguen
Principle Design Engineer
EMC Corporation

Tomasz Sowinski20-Sep-01 9:57

20-Sep-01 9:57

There are many fields in TVITEM struct, which is a member of TVINSERTSTRUCT. You may have overlooked one of them. Give other overloads a try - they are easier to use and understand.

Tomasz Sowinski -- http://www.shooltz.com

Ken Goguen20-Sep-01 10:12

20-Sep-01 10:12

I simplified as follows and it seems to have done the trick. Thanks.

HTREEITEM hTreeItem = pMyTree->InsertItem(_T(buffer),0,0,NULL, TVI_LAST);

Big Grin | :-D

-kg

Ken Goguen
Principle Design Engineer
EMC Corporation

DLL Question

#realJSOP20-Sep-01 9:03

#realJSOP

20-Sep-01 9:03

I'm working on a non-MFC DLL (that doesn't have a DllMain). I need to get the HINSTANCE of this DLL (for use inside the DLL). How do I do that?

I can't use AfxGetInstance().

Re: DLL Question

Tomasz Sowinski20-Sep-01 9:15

20-Sep-01 9:15

If your DLL doesn't have DllMain, it must have other entrypoint with identical set of parameters. 1st param is HINSTANCE you're looking for - just store the value in global variable.

Tomasz Sowinski -- http://www.shooltz.com

OleAutomation

duggie20-Sep-01 8:43

duggie

20-Sep-01 8:43

I am new to OleAutomation. I am trying to execute an Access macro from VC++. I believe I am missing something. It doesn't work. The code is attached below.

_Application oAccess;
IDoCmd cmd;
LPDISPATCH lpDisp;

/////////////////////////////////////////////////////////////////////////////
// CTemp1App initialization

BOOL CTemp1App::InitInstance()
{
// Initialize OLE libraries
if (!AfxOleInit())
{
AfxMessageBox(IDP_OLE_INIT_FAILED);
return FALSE;
}

if (!oAccess.CreateDispatch("Access.Application"))
{
AfxMessageBox("Couldn't CreateDispatch on Access");
}

oAccess.OpenCurrentDatabase("S:\\Ses\\User\\VKaruppiah\\Upfitter97.mdb", FALSE);

COleVariant macroName = "GMDIDProcessing";
COleVariant repeatCount = "";
COleVariant repeatExp = "";
cmd.RunMacro(macroName, repeatCount, repeatExp);

cmd.ReleaseDispatch(); // Release the object-IDispatch binding.
oAccess.ReleaseDispatch();
cmd = NULL; // Destroy the object references.
oAccess = NULL;

}

Any help would be greatly appreciated.

Thanks,
Confused | :confused:

Michael P Butler20-Sep-01 10:34

Michael P Butler

20-Sep-01 10:34

Which bit of code fails? Have you put any try and catch code around the COM calls to access.

Michael Smile | :)

duggie20-Sep-01 10:52

duggie

20-Sep-01 10:52

The code does not fail anywhere. But it doesn't run the macro either. The line that is giving me trouble is

cmd.RunMacro(macroName, repeatCount, repeatExp);

If I put a watch on cmd after executing this line, m_lpDispatch value = "Error expression cannot be evaluated".

Any ideas/suggestions would be appreciated.

Thanks,

Michael P Butler20-Sep-01 10:55

Michael P Butler

20-Sep-01 10:55

put a try and catch around the RunMacro and see what error it returns

try
{
cmd.RunMacro(macroName, repeatCount, repeatExp);
}
catch(CException& e)
{
}

Carlos Antollini20-Sep-01 10:53

Carlos Antollini

20-Sep-01 10:53

Yes you need to acces to the CommandInterfase from the database interfase.
Something like this

lpDisp = oAccess.GetCommands(); //Get an IDispatch pointer. I think 
                                //that Here is your problem
ASSERT(lpDisp);            
cmd.AttachDispatch(lpDisp);

Note: I don't know if the method is GetCommand or something like this.

Best Regards!!!

Carlos Antollini.