FiveTech Support Forums

Hi,

in my program the key VK_F2 has a general function. Generally it works perfectly. But since the upgrade to fwh1005 I get a message "oCol:bOnPostEdit not defined" when a x-browse window is opened an I press the F2-key.

I made following efforts to handle this change of behaviour:
- I found in the TxBrwColumn-class a data lOnPostEdit which doesn't seem to have any effect on this.
- Also I found the method nEditType which I called with oCol:nEditType(0) which doesn't show any effect as well
- Also I found in the xbrowse-class a data lEditMode. If I manually override it to lEditMode := .t., then the message won't be shown again. But the Key F2 is still not being evaluated... Besides, I think this information should not be changed manually.

Has anyone an idea how pressing F2 will evaluate the standard set for the whole program without xbrowse having any effect on it?

Gilbert

Since fwh 10.5 Xbrowse is behaving like excel and therefore f2 is assigned to edit a cell

I had the same surprise as my app uses also F2

As a work around, you needd to change the xbrowse.prg

search for keydown method and comment the relevant f2 code

Hth

Richard

Richard,

thanks a lot for your answer. I did it like you said and it works.

Antonio,

have you planned to introduce something like a switch, so you can switch on/off excel-like behaviour?
Because in our application F2, SHIFT+F2 and CTRL+F2 are being used for other purposes.

Gilbert, Richard,

We could add a new

DATA nEditKey INIT VK_F2

so from your app you could easily set a oBrowse:nEditKey = nAnotherValue

does it seem fine for you ?

I prefer F2 to be disabled by default. Actually I'd prefer any new feature introduced to be off by default to avoid being caught by surprise. It's a lot of work having to recheck all the modules to insert a new line just to be sure whatever was working will still continue to do so every time some new feature is added.

Hua,

Yes, you are right and thats the way it should be. It was our mistake to implement that functionality without asking about it in advance. Our apologizes about it.

This is why we want to fix it now and make it fully configurable, optional, etc.

Thank you

Antonio,

thank you very much, your proposal should work fine for me.
Please let us know as soon as you have completed this feature

Gilbert,

We have already implemented it and we will include it in next FWH 10.6 this same month