Sorry to be such a bother here, but I just found another "problem" for
me. The selected values from the ComboBox are not returned to the
ListView. If I select an entry, and then mouse click another column
or click Ok, the value in the ListView still has the original value that
was initially loaded. If I escape out of the ComboBox, it appears the
Cancel button is activated as the program ends. Maybe I need to
think of another approach to what I was trying to do here and not
use the ComboBox ?
Art
> Mark,
>
> It appears to work much, much better - thanks. A problem that it
> has for me is if I TAB out of the ComboBox, the program seems to
> lock up in that Ok, Cancel, "x" abort, mouse clicks - nothing seems
> to respond. TAB works okay as long as I do not TAB out of the
> ComboBox. I have not pursued this to attempt to identify which
> change is causing this behavior. Thanks for any ideas. Art
>
>> Hi Art,
>>
>> I was surprised your attachement seemed to make it through the
>> list. I'm attaching your program, a little redone that I think
>> works well.
>>
>>
>> The main thing I did was make the combo box a drop down list
>> combo box:
>>
>>
>> COMBOBOX IMP_CBOX, 15, 35, 40, 12, CBS_DROPDOWNLIST
>>
>>
>> If you use a drop down combo box, the user can type in his own
>> text, but you need to use a different technique. If you do want
>> that behavior, let me know.
>>
>>
>> Some other changes were to use the 'will reply' argument when
>> connecting the list view click events. This helps synchronize
>> the processing of the window messages and is probably important
>> here.
>>
>>
>> Then you can compare the code in onLVSClick() that I have with
>> what you had to see the differences.
>>
>>
>> The behavior maybe is not exactly what you wanted, let me know
>> if that is the case.
>>
>>
>> --
>> Mark Miesfeld
>>
>>
>> On Wed, Oct 23, 2013 at 7:56 AM, Mark Miesfeld
>> <[email protected]> wrote:
>>
>>> Hi Art,
>>>
>>> I worked on this a little bit, but I don't have time to
>>> continue right now. I'll work on it more tonight.
>>>
>>>
>>> --
>>> Mark Miesfeld
>>>
>>>
>>> On Tue, Oct 22, 2013 at 7:57 PM, Mark Miesfeld
>>> <[email protected]> wrote:
>>>
>>>> On Tue, Oct 22, 2013 at 7:13 PM, Art Heimsoth
>>>> <[email protected]> wrote:
>>>>
>>
>>>>> I think I am okay in the single vs double click events.
>>>>> You can
>>>>>
>>>>> try the sample to see if you agree or not.
>>>>>
>>>>
>>>> Yeah, it seems the single-click / double- click works well
>>>>
>>>>
>>>>> If you double click
>> on column 0, I have intended it to work the same as if I single
>> clicked on an item in that column (it is setup for single click
>> operation).
>>>>
>>>>
>>>> Not sure what you mean there. If I single-click or double-
>>>> click the combo box opens.
>>>>
>>>>
>>>>> If you single click on column 2, it only selects the
>>>>>
>>>>> item but does not allow it to be edited. If you double
>>>>> click on
>>>>>
>> the column 2, then you are allowed to edit it.
>>
>>>>
>>>> That looks to work well
>>>>
>>>
>>>>> The problem I
>> am having I think is with the focus on Column 0 with the
>> ComboBox.
>>
>>>>
>>>> The problem I see is that when you have the edit box open and
>>>> click elsewhere the edit box closes and whatever text was in
>>>> the edit box is displayed. That is good and what I would
>>>> expect.
>>>>
>>>> But, when you make a selection in the opened combo box and
>>>> click elsewhere, the combo box will stay open, unless the
>>>> elsewhere is in the same column. If you click elsewhere in
>>>> the *same* column, the comb box closes, but usually shows a
>>>> different selection than the one made.
>>>>
>>>>
>>>> I would expect the combo box to close whenever you click
>>>> outside of the combo box and I would expect the list view
>>>> item to show the selected item in the combo box.
>>>>
>>>>
>>>> Is that the correct problem?
>>>>
>>
>>>>> The sample is attached, to start, click on File
>>>>>
>>>>> and then Import. I did not want the Ok button to be active
>>>>>
>> unless the ComboBox or the EditBox do not have the focus. I may
>> have to add disable/enable logic between the click and the
>> GrandChild and Scroll events to get this to work.
>>>>
>>>>
>>>> I think if I described the correct problem, you should get
>>>> that fixed. Then fixing the Ok button should be relatively
>>>> simple.
>>>>
>>>>
>>>> Let me know if I have the right problem. I'll then take a
>>>> closer look at the program logic.
>>>>
>>>>
>>>> --
>>>> Mark Miesfeld
------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________ Oorexx-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oorexx-users
