|
Hi all,
How can I detect that the network cable is unplugged/plugged? . And I need to find out the network status anytime be it in any like dial-up network and
cable network .
please help me in this regard
pradeep
pradeep
|
|
|
|
|
|
See here. There's also the ISensNetwork interface.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
In addition to the method suggested by David, you can also use InternetGetConnectedState to get the connection state.
Dario: How is "directory" in French? (I mean a file system directory).
John Simmons: "zee file holdaire thingie"
|
|
|
|
|
|
I've created a menu called Tools where in I have created a menu item called Preferences. If we click the Prefernces menu item Preferences Dialog Box will open. In that Dialog Box I have an edit box. The message entered in this edit box is displayed in the second panel of the status bar (i.e) panel no.1.
My Requirement is:
The second panel should be of a default size and it should grow according to the length of the message entered in the edit box.
How can I achieve this in MFC? Can any one help?
I have tried this also. But it didn't work.
CStatusBar::SetPaneInfo( int nIndex, UINT nID, UINT nStyle, int cxWidth );
The function that displays the message is:
void CPerspectiveDoc::OnShowMsg(CCmdUI* pCmdUI)
{
char str1[150];
//int len = message.GetLength();
sprintf(str1, "%s",message.GetString());
pCmdUI->Enable(TRUE);
pCmdUI->SetText((const char *)str1);
//m_wndStatusBar.SetPaneInfo(1, IDS_MESSAGE, SBPS_STRETCH, len);
}
When I remove the comment from the following code, it shows me an exception stating that "Unhandled exception at 0x7c1d71bb (MFC71.dll) in Perspective.exe: 0xC0000005: Access violation writing location 0x00000014."
The commented out line of code is:
//m_wndStatusBar.SetPaneInfo(1, IDS_MESSAGE, SBPS_STRETCH, len);
Any one Please help.
|
|
|
|
|
I have tried with an and this code works.
May be something else is wrong...
CString message;
message = "A LOOOOOOOOOOOOOOOOOOOOONG MESSAGE000000";
int len = message.GetLength();
m_wndStatusBar.SetPaneText(1,(LPCTSTR)message,FALSE);
m_wndStatusBar.SetPaneInfo(1, 1, SBPS_STRETCH, len);
|
|
|
|
|
The method that displays message is:
The function that displays the message is:
void CPerspectiveDoc::OnShowMsg(CCmdUI* pCmdUI)
{
char str1[150];
//int len = message.GetLength();
sprintf(str1, "%s",message.GetString());
pCmdUI->Enable(TRUE);
pCmdUI->SetText((const char *)str1);
//m_wndStatusBar.SetPaneInfo(1, IDS_MESSAGE, SBPS_STRETCH, len);
}
I can't use SetPaneText and SetPaneInfo with this CCmdUI* (pCmdUI) object pointer. If I comment out this: //m_wndStatusBar.SetPaneInfo(1, IDS_MESSAGE, SBPS_STRETCH, len);I got an exeption.
More over we should not initialize the string "message" in the code. We should get it through GetString method for edit box. The status bar pane should grow according to the length of the string.
static UINT indicators[] =
{
0,// ID_SEPARATOR
IDS_MESSAGE,
ID_SHOWFPS,
};
This method is in some other source file. Is this a reason for this error?
|
|
|
|
|
1) There are several status bar articles on CP. Check one of them to see if they have the info you need. I used one that makes it a bit simpler to add custom panes and update them when necessary. In fact, there's one article here that allows better control over the status bar than the default MFC class allows. Try here: http://www.codeproject.com/statusbar/ExtStatusControlBar.asp[^]
2) This comment is based on a complete lack of knowledge where your requirements are concerned - It seems to me that you're approaching this incorrectly. If it were me I'd be setting the status bar pane text when the dialog box exists with IDOK. Handling it in a command update function is beyond funky. If you set the text in the dialog box, there's no reason for it to change in the status bar until you change it in the dialog box again.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
By the way, I think you're going to have to calculate the new size manually and then pass that value into the status bar.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Not only manually, the status bar pane should grow dynamically i.e as and when I enter one character in to the edit box the status bar pane should grow one character length. This way the status pane will have to grow for hundred characters length that is entered via the edit box.How can I do?
|
|
|
|
|
Well, I wouldn't change the statusbar until AFTER the user clicks OK, but that's just me. However...
1) In your dialog box, you would have to handle the EN_CHANGE message for the edit control. Every time the user types a character you have to calculate the new width of the string in pixels.
2) I would send a message to the parent view that contained a pointer to the string, and let the parent view do the width calculations. This message would probably be one you have to define (WM_APP+n) and manually add a handler for in your view.
3) When the view gets the message, it gets the string from the passed-in pointer value and creates a CPaintDC object. This dc object can then provide the width of the string via the GetTextExtent() function. This new width would be passed to the status bar for the appropriate pane, and the text would be applied to that pane.
If you decide to handle the status bar update after the user clicks the OK button in your dialog box, you can skip steps 1 and 2, and just retrieve the string from the dialog box itself, and do step 3.
I assume you're a programmer (and you obviously have access to the internet, so you can look stuff up on your own), so I leave it to you to work out the specifics.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
When I add the EN_CHANGE message the following error occurs.
error C2440: cannot convert from CSize to int
error C2440:'static_cast':cannot covert from 'int(__thiscall CPreferences::*)(void)' to 'AFX_PMSG'
the code I added was,
int CPreferences::OnEnChangeEditmessage()
{
CPaintDC *pDC;
int size;
size = pDC->GetTextExtent(m_strMessage);
return size;
}
The message map I added was,
ON_EN_CHANGE(IDC_EDITMESSAGE, OnEnChangeEditmessage)
The afx message I added was,
afx_msg int OnEnChangeEditmessage();
What to do?
-- modified at 4:00 Tuesday 6th February, 2007
|
|
|
|
|
Did you look on MSDN for documentation on GetTextExtent()? It returns a CSize structure, NOT an int.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Ya! It's true. When I use the following code,
void CPerspectiveDoc::OnShowMsg(CCmdUI* pCmdUI)
{
//char str1[150];
CString strValue;
strValue.Format("%s", message.GetString());
//strValue.SetLength(100);
//sprintf(str1, "%s",message.GetString());
pCmdUI->Enable(TRUE);
pCmdUI->SetText(strValue);
CDC* pDC = m_wndStatusBar.GetDC();
CSize mSize = pDC->GetTextExtent(strValue);
m_wndStatusBar.SetPaneInfo(1, IDS_MESSAGE, SBPS_NORMAL, mSize.cx);
//m_wndStatusBar.SetPaneInfo(1, IDS_MESSAGE, SBPS_STRETCH, len);
}
I got the following exception.
'Unhandled exception at 0x7c1d71bb (MFC71.dll) in Perspective.exe: 0xC0000005: Access violation writing location 0x00000014.'
If I break this exception, it ends in a class barstat.cpp
If I comment out this line,
m_wndStatusBar.SetPaneInfo(1, IDS_MESSAGE, SBPS_NORMAL, mSize.cx);
exception didn't arise.
I have declared m_wndStatusBar variable in some other class.
How do I make this variable visible to this class CPerspectiveDoc.
-- modified at 23:42 Tuesday 6th February, 2007
|
|
|
|
|
Greetings all,
Im trying to send messages to a main dialog, but it seems that the messages does not get received.
extern CListBox* hList;<br />
.<br />
.<br />
.<br />
if (lTotalCols > 0)<br />
{<br />
<br />
SendMessage((HWND)hList, LVM_DELETEALLITEMS, 0, 0);<br />
for (idx=0; idx<lTotalCols; idx++)<br />
{<br />
SendMessage((HWND)hList, LVM_DELETECOLUMN, (int)0, 0);<br />
};<br />
}<br />
Any Suggestions of what to try?
Reinart Laast,
Junior Developer.
Greetings from South Africa
|
|
|
|
|
extern CListBox* hList;
SendMessage((HWND)hList, LVM_DELETEALLITEMS, 0, 0);
(HWND)hList is pointing to a CListBox handle. that means, Message is being sent to the List box.
is that what you intend to do?
Pass the handle of the MainDialog here..
regards,
Haribabu
|
|
|
|
|
Keep in mind that I haven't tried this or looked around on MSDN/web (like you could easily do yourself), so I don't know if this is going to work, but try one of these:
SendMessage(WM_COMMAND, LVM_DELETEALLITEMS, 0);
SendMessage(WM_MESSAGE, LVM_DELETEALLITEMS, 0);
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Thank you, I'll try to find out if i could get it working in that way as well.
|
|
|
|
|
Thanks Haribabu, and that is the intention actually, sorry if i phrased the question wrong
I want to clear the listbox and insert the items from the function im sending the messages from, the listbox is on the main dialog, but when i add an messagebox that should receive LVM_DELETEALLITEMS message, it doesnt work.
As if the messages go somewhere else or nowhere at all.
BOOL frmMenu::OnInitDialog() <br />
{<br />
CDialog::OnInitDialog();<br />
this->SetRedraw(true);<br />
<br />
hList = (CListBox*)(GetDlgItem(IDC_LIST));<br />
<br />
return TRUE;
}
void frmMenu::OnDeleteallitemsList(NMHDR* pNMHDR, LRESULT* pResult) <br />
{<br />
NM_LISTVIEW* pNMListView = (NM_LISTVIEW*)pNMHDR;<br />
<br />
AfxMessageBox(TEXT("Got it"));<br />
<br />
*pResult = 0;<br />
}
-- modified at 6:10 Monday 5th February, 2007
|
|
|
|
|
1) Add a control variable for the listctrl. It will simplify further manipulation of the control, eliminating the need for code like this:
hList = (CListBox*)(GetDlgItem(IDC_LIST));
2) If you want to remove all items from the list control, use this (based on your apparent current code):
hList->DeleteAllItems();
3) There's no need to send a message to the listbox (see item #2 above).
4) Quite frankly, your naming conventions suck. Personally, I would never name a dialog box class something like "frmMenu". If you scan file names and you see frmmenu.cpp, wouldn't you assume that file contains some sort of menu code?
Is the message you're sending coming from outside the dialog box? If so, make a programmer-defined message and handle it that way:
#define UWM_DELETE_ALL_ITEMS WM_APP+1
#include "CustomeMessages.h"
class frmMenu public
{
public:
afx_msg LRESULT OnDeleteAllItems(WPARAM wParam=0, LPARAM lParam=0);
};
{MESSAGE_MAP
ON_MESSAGE(UWM_DELETE_ALL_ITEMS, OnDeleteAllItems)
MESSAGE_MAP}
LRESULT frmMenu::OnDeleteAllItems(WPARAM wParam, LPARAM lParam)
{
lParam;
wParam;
((CListBox*)(GetDlgItem(IDC_LIST)))->DeleteAllItems();
return 1L;
}
This was all done off the top of my head, so you may need to adjust the code to fit/compile, but this should do what you need.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
Thanks, this will work with EVC++ 4.0? Because im doing this for a win ce device. I already have a control variable for the control, should i rather use that?
And the naming convention thing i know, that was a slip from the c# i've done for menu forms.
Only recently started dabbling in c++
|
|
|
|
|
I have no clue if it will work in that environment, but there is little in MFC that doesn't (MSDN sometimes points out CE-specific concerns). My advice is to give it a try. We also have a Windows CE forum here that yo could post CE-specific questions in.
I have some more advice for you. When you ask questions here, provide as much detail on your requirements as you can. It's hard enough to answer ambiguous questions, and not knowing the requirements make sit harder to give you the right answer the first time. For this particular thread, you should have started out with something like this:
Compiler: EVC 4.0
Framework: Windows CE application using MFC
Experience: I'm new at this C++ stuff, so go kinda slow.
And then proceed with a DETAILED description of your problem, and what you've tried to fix it. This will keep us from having to go over stuff you've trie or point you to where you went wrong.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
All my messages come from outside the dlg class, so should i rather define all the messages in a custom message .cpp file?
Not only for delete as well as the populating of the listbox, because at the moment i try to fill it with messages as well with -
<br />
while(lNumRowsRetrieved > 0)<br />
{<br />
for(lCount=0; lCount<lNumRowsRetrieved; lCount++)<br />
{<br />
memset(pBuffer, 0, ConsumerBufColOffset);<br />
pIRowset->GetData(hRows[lCount], hAccessor, pBuffer);<br />
<br />
pitem.mask = LVIF_TEXT;<br />
pitem.iItem = SendMessage((HWND)hList, LVM_GETITEMCOUNT, 0, 0);<br />
pitem.pszText = (LPTSTR)&pBuffer[pBindings[0].obValue];<br />
pitem.iSubItem = 0;<br />
idx = SendMessage((HWND)hList, LVM_INSERTITEM, 0, (LPARAM)&pitem);<br />
<br />
for (lColumn=1; lColumn<lNumCols; lColumn++)<br />
{<br />
pitem.mask = LVIF_TEXT;<br />
pitem.iItem = idx;<br />
pitem.pszText = (LPTSTR)&pBuffer[pBindings[lColumn].obValue];<br />
pitem.iSubItem = lColumn;<br />
SendMessage((HWND)hList, LVM_SETITEM, 0, (LPARAM)&pitem); <br />
}<br />
<br />
lTotalRows++;<br />
};
|
|
|
|
|
I think you're going to have to describe what your app is doing and why you're handling it the way you are.
"Why don't you tie a kerosene-soaked rag around your ankles so the ants won't climb up and eat your candy ass..." - Dale Earnhardt, 1997
-----
"...the staggering layers of obscenity in your statement make it a work of art on so many levels." - Jason Jystad, 10/26/2001
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
