Re: [Foxgui-users]Re: FXComboBox misfeature

[Hal B. <br...@ll...>]

Jeroen van der Zijp wrote:

>On Thursday 16 January 2003 11:51 am, you wrote:
>  
>
>>I sent this to foxgui-users, but got zip/nada/zilch.
>>I sent this to jeroen@fox-toolkit,org and got zip/nada/zilch.
>>So, now I'm trying this address.
>>    
>>
>
>I got your mail, but I do not always have time to react to 
>everybody's email directly.  I get a *lot* of mail from
>people, and if sometimes it will take time to get around
>to it.
>
>Remember, this is done in my free time.  
>
I do understand - I too have supported stuff in my spare time. I know it 
can be a big
drain and be quite frustrating at times. However, in my following of the 
foxgui-users
list over the past week, I noted you responding to many peripheral (wrt 
FOX itself)
issues leading me to believe that you had the time to respond - at least 
with a "noted".

>>(If you are choose to ignore it, just repond with a simple
>>"go to hell" and I'll go work around the problem.)
>>    
>>
>
>There is no need to use such language.
>
(Sorry about my bad grammar). The "bad" language you refer to was *not*
directed at anyone (except maybe myself, light-heartedly). Nor was it 
distributed
to the list. Strange you objected to it in a private email, then choose 
to CC it to
the list.

>Just because you don't receive a reply, does not mean it is
>forgotten.
>
And, just because I don't receive a reply doesn't mean it arrived, was 
noted,
nor accepted/rejected. It doesn't mean anything - not at all useful for 
making
a decision on how to proceed.

>  Sending emails just to let you know it landed
>in my in-box takes up my time also, during which I can't be 
>working on actual coding.  I usually give a reply when there
>was also a fix implemented already.
>
With a bug/misfeature report, I expected at least a "noted" response, 
particularly
given the list traffic over the past few weeks and your prompt response 
to similar
reports.

>===
>
>The FXComboBox getCurrentItem() API actually reads the 
>getCurrentItem() of the FXList, which was changed to the last 
>item visited in the interaction, which is of course the wrong
>value if the visited item isn't actually chosen in an interaction
>with the FXComboBox.
>
>A temporary workaround (and this is recommended even after the 
>issue is fixed), is to catch SEL_UPDATE messages originating from 
>the FXComboBox.  Then the FXComboBox will update itself to the
>value your application actually knows about.
>
Unfortunately, that doesn't work for me; my application doesn't know. 
Its using
the FXComboBox to store the state. (Since the FXComboBox has state, why 
should I
duplicate/reflect it?) I have a different workaround; I'll use it for now.

>>I believe there is a mis-feature in FXComboBox::getCurrentItem().
>><snipped>
>>    
>>
>I will look into a fix; thanks for the bug report.
>
Thanks.

BTW - we have a good sized application suite that uses FOX. I trying to get
approval to get screen shots to Sander. It may take a while, though.

--
					Hal R. Brand
					br...@ll...