|
Yes.
I select the text with:
pCombo->SetEditSel(0,-1);
Interestingly, I have found that
pCombo->SetEditSel(0,-1);<br />
pCombo->Clear();
does not work as well as
pCombo->SetEditSel(0,-1);<br />
pCombo->Paste();<br />
pCombo->SetEditSel(0,-1);<br />
pCombo->Clear();
while this is effective - it not cosmetically pleasing.
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
lctrncs wrote: In drop list mode my OnSelchangeCombo function...
What does this method look like?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
What does my OnSelChangeCombo function look like?
It is rather simple:
1. Pointer to the Combobox with assert if NULL,
2. code to return index of selected item in listbox from control directed alpha listing (thank you Chris Losinger!),
3. dirtyflag check of record and associated commit if true,
4. call of the GotoRecord function.
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
Ok, what I have here may help, or it may not since it is not entirely like what you have. I have a CRecordset-derived class that reads from the Employees table of the Northwind database. I have a dialog with a combobox (having the CBS_DROPDOWNLIST style) and listbox. Selecting an item from the combobox will add it to the listbox. The selection in the combobox is then cleared.
BOOL CMyDlg::OnInitDialog()
{
CDialog::OnInitDialog();
CDatabase db;
CSet rs(&db);
rs.Open();
while (! rs.IsEOF())
{
m_combo.AddString(rs.m_LastName);
rs.MoveNext();
}
rs.Close();
m_combo.InsertString(0, "");
return TRUE;
}
void CMyDlg::OnSelchangeCombo1()
{
int nIndex = m_combo.GetCurSel();
CString strItem;
m_combo.GetLBText(nIndex, strItem);
m_list.AddString(strItem);
m_combo.SetCurSel(0);
}Is this close?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Well I got things running like you show here - the Class Wizard info was key - but it still does not clear the edit box in either dropdown or drop list mode - any other suggestions?
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
If you can narrow this project down to just the relevant lines, you can e-mail it to me and I'll take a look.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
Thank you.
I spent some time with it this weekend and got it working.
Thank You!
Your assistance was of great service to me!
Thank you again!
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
Overall, what did you do to finally get it going?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
I am beginning to wonder if my use of the dereference operator rather than the dot operator might be part of my problem.
Being a complete beginner, this is the first time I have tried to instantiate a class and my local resource (an embedded systems programmer) cannot provide much assistance.
The class (CCombobox) and member (InsertString) I am using are overridden.
When I instantiate an instance like this
OverRiddenCombobox w_wndOverBox;
locally in the function where I want to use it (along with
w_wndOverBox InsertString(0,"",0)
, my program compiles and runs fine until I try to open the dialog.
Then I get and exception error, and the debuger shows me a line in afxwin.inl apparently defining the not overridden base class member InsertSting with two arguments (my InsertString has three arguments).
Suggestions?
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
lctrncs wrote: I am beginning to wonder if my use of the dereference operator rather than the dot operator might be part of my problem.
Use -> with pointers, and a . (dot) otherwise. The compiler should warn you of incorrect usage.
lctrncs wrote: w_wndOverBox InsertString(0,"",0)
What's holding w_wndOverBox and InsertString() apart?
lctrncs wrote: Then I get and exception error, and the debuger shows me a line in afxwin.inl...
An exception or an assertion?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
DavidCrow wrote: What's holding w_wndOverBox and InsertString() apart?
A dot operator (sorry about the incorrect post).
DavidCrow wrote: An exception or an assertion?
An assertion:
Debug Assertion Failed...
_AFXWIN_INLINE int CCombobox::InsertString(int nIndex, LPCTSTR lpszString)<br />
{ ASSERT(::IsWindow(m_hWnd)); return (int)::Sendmessage(m_hWnd, CB_INSERTSTRING, nIndex, (LPARAM)lpszString); }
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
lctrncs wrote: An assertion:
Debug Assertion Failed...
_AFXWIN_INLINE int CCombobox::InsertString(int nIndex, LPCTSTR lpszString)
{ ASSERT(::IsWindow(m_hWnd)); return (int)::Sendmessage(m_hWnd, CB_INSERTSTRING, nIndex, (LPARAM)lpszString); }
Which indicates you have a non-existent window. At what point are you trying to populate the combobox?
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
I populate the combobox in OnInitDialog - which is only called upon dialog start and after a change to the database such as adding or deleting a record.
I am trying to clear the dropdown style edit box (drop list style would be preferred due to the static edit box) from my DisplayRecord function (called at the end of OnInitDialog), and this is where I have instantiated m_wndComboBox, and from where I call m_wndComboBox.InsertString(0,"",0).
The control exists on a modeless dialog, which is trying to open at the time of the assert.
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
lctrncs wrote: ...this is where I have instantiated m_wndComboBox...
m_wndComboBox should be a member variable, not local to some function.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
As I said, I have never tried to instantiate a class instance so that I can use the dot operator.
I tried to instantiate it in a number of locations (mainframe.cpp main.c etc.) without success.
So where should I instantiate my m_wndCombobox so that I can use the dot operator as you suggest
m_combo.InsertStinrg(0,"")
?
Why should the dot operator work when a pointer does not?
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
lctrncs wrote: So where should I instantiate my m_wndCombobox so that I can use the dot operator as you suggest
It should belong to the class that owns it (hence the m_ prefix). In my example, m_combo and m_list are both members of CMyDialog.
lctrncs wrote:
Why should the dot operator work when a pointer does not?
Pointer variables use ->, while non-pointer variables use a dot. In reality,
pointer->member is equivalent to:
(*pointer).member See here for more on the member-selection operator.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
So I should right click on CDialog, choose Add Member Function and enter Ccombobox and m_combo to instantiate m_combo as a member CDialog?
"For a successful technology, reality must take precedence over public relations, for nature cannot be fooled." Richard Feynman, Minority Report to the Official Report on the Space Shuttle Challenger Crash
|
|
|
|
|
lctrncs wrote: So I should right click on CDialog, choose Add Member Function and enter Ccombobox and m_combo to instantiate m_combo as a member CDialog?
No. Use ClassWizard (Ctrl+W) to associate a member variable with a control.
"Approved Workmen Are Not Ashamed" - 2 Timothy 2:15
"Judge not by the eye but by the heart." - Native American Proverb
|
|
|
|
|
hi there!
im trying to write a graphing app using the win32 api with MFC...
im trying to figure out how i can represent a decimal number position in a grid of pixels:
i.e.
given y = sqrt(x)
if i calculate with x = 5.7 then y becomes 32.49 which is a bit of a problem because no pixel exists at 32.49, so the line gets drawn at y = 32, so the graph curve is messed up because the curves arent matching up because of the round-off error...
im trying to draw the line using the MoveTo and LineTo functions, and if i can figure out a way to draw the correct pixel corresponding to the equation then i can use a very low incremental value such as 0.1 to make the curve look smooth, though its not really smooth...
but if theres a better way of drawing a graph app (without using bezier curves or whatever) please could u let me know!
hope u can help me out! thx!
|
|
|
|
|
If yu are going to use LineTo to draw your lines, then you are going to have to draw them using very small increments, and the round-ff errors are not going to be that noticeable. If you are trying to draw the curve for squares or square-root values, for example, you need to keep your increments as small as possible to produce a "smooth" effect. Otherwise you are going to have to use some othe mathematical functions expressly written to display curves in a very smooth format. You can get more help on the internet about those than I can explain here. Good luck
John P.
|
|
|
|
|
Hey all,
I've run into a small problem. When Windows generates an HDC on its own (for a paint message) it uses the clip region to determine the update area. If you call GetClipBox() the coordinates start at 0,0. If that region is a portion of a larger window I would need to know where that area is in relation to the entire window.
Is there a function that can translate the HDC coordinate space into one that maps onto the window rect (or some other global space?)
Thanks!
ant
|
|
|
|
|
ClientToWindow or ClientToScreen might help
|
|
|
|
|
Thanks, but it is ambiguous. The window client region will have a 0,0 defined as the upper left corner of the window. The HDC (which is in the same client area) will also have a 0,0 defined which is not necessarily the same location. While ClientToScreen() will convert the point, it will convert it assuming the window coordinate space and not the HDC coordinate space. In order for ClientToScreen to work it would have to take the HDC as an argument.
Thanks for the suggestion, but it didn't work. 
|
|
|
|
|
Screen coordinate space: relative to the screen.
Window coordinate space: relative to the window.
Client coordinate space: relative to the client area of a window (excluding title bar, border, menu, etc.)
For a given HDC, there will be two (potentially different) coordinate systems: device coordinates and logical coordinates.
For device coordinates, the origin, orientation, precision, etc. are determined by the device on which output is to be displayed: for the screen, these are usually relative to the window for which the device context was requested, with (0,0) at the top left, y increasing downwards, with pixel units (contrast with printers, which might have (0,0) at the bottom left, y increasing upwards, units being in something that makes sense for the type of printer). BeginPaint(), for instance, returns a device context for the client area of the window being painted.
Logical coordinates, controlled via SetMapMode(), can have a different origin, orientation, and unit size than those of the device that they eventually map to (MM_TEXT == 1-1 mapping to device units, MM_INCHES == 1" units, bottom left origin, y increases upwards, etc.)
The update region is merely an area within a given window marked as needing to be redrawn. BeginPaint() will set the clipping region to this area and erase it, but it does not determine how coordinates are mapped to the output device - it is useful only as an aid in determining what portion of the window needs to be redrawn (similarly, the clipping region is used to avoid redrawing portions of the screen - initially, it is set to the client area of the window (for client HDCs)).
See also:
Guide to Win32 Paint[^]
|
|
|
|
|
Thanks to everyone who provided insight. In the end I guess my description wasn't clear enough to explain the problem since it is a rather bizarre situation. Mixing MFC/Win32 can give odd results at times and this is one of those times! I'm looking into a workaround right now which is starting to look promising. If however anyone else has suggestions please make them!
Thanks!
ant
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
