Comments by Ernst G. Gruber

Ernst G. Gruber 15-Jun-12 7:08am View

Thanks a lot for the answer! The FINDSTRING method you mentioned was my plan B, but seemed to be not very elegant, for all the information necessary is already available. Additionally one needs an empty entry in the list to take care of empty elements in the array ...
Well, you can't win them all! Thank you again for your help!

Ernst G. Gruber 30-May-12 17:20pm View

Good when you feel this way! As for me - I was and should have been on the right track after your first answer! And not carrying on pestering you unnecessarily ...
Take care! E

Ernst G. Gruber 30-May-12 9:51am View

Just forgot to say - handle to combobox is no problem - it stems directly from CreateWindow ...

Ernst G. Gruber 30-May-12 9:46am View

Thanks again for talking to me!
Trouble is - there is not much more than what you see in my original post. Now the original post has been extented by "get the handle of the edit part" and "set the pointer to the child procedure (and save the original pointer to the parent procedure at the same time)) as shown in my second post. Plus the child procedure for the edit part, which looks pretty much the same as in the example you pointed me to. There is no INITDIALOG or similar, just a main window and a combobox (which doesn't work). What worries me is - now I have two different ways of getting the handle of the edit part (ChildWindowFromPoint (from the example) and your FindWindowEx). Both ways deliver different results ... and both do not give me the WM_CHAR and ....

As a (very) old OS/390 warhorse I just wonder how complicated the use of one of the most common forms of a combobox can be ....

Just drop me a line if you want to have a look at the "total code".

With best regards, Ernst

Ernst G. Gruber 29-May-12 15:32pm View

Thanks a lot for your answer! I feared something like this may turn up as an answer to my question, but the article you pointed me to, looks very solid.

Thanks again and I will post the outcome of my attempts ...

Ernst G. Gruber 18-May-12 5:27am View

Michael, thanks again for your remarks!

ad 1) To get a handle to the listbox is not a problem. It is returned by the CreateWindowEx function when creating the listbox. Unfortunately the handle isn't of any use, because - at least in my understanding - a handle can be anything, but isn't a pointer to the structure I am looking for. Further reading in MSDN documentation revealed another intriguing sentence - "The control structure of a list box and its tab stop settings is allocated from the heap ...", but again no hint how this control structure can be accessed ... :O((

ad 2) This is what I used to think. But - at least the compiler I am using, MS VC++ 2008 - returns from the line <pre lang="c++">listbox1.GridLinesHorizontal = listbox1.BorderThinSolid;</pre> both errors. Hence, I thought, GridLinesHorizontal is already checked and accepted. But you may be right - it's the same error in both cases and they may override other errors ...

Well, one can't win them all ....

Comments by Ernst G. Gruber (Top 6 by date)