FiveTech Software tech support forums

... There will be a reason for this..... but maybe we can consider a logical Var that toggles this beheavior ? For this specific browse, maybe I can trap the cursor key value and process it to only do a goleft... goright with no processing ? Just thinking, but not able to do it.

Jimmy

Debug is a very handy tool to have .. you can debug also and trap values at runtime with Msginfo() .. you can easily evaluate memory variables, module tracing, etc ....

Rick Lipkin

Found it I think I can trap all e:SubCode errors that are not supported with FW-error, but FW-Errorsystem is still working right ? what is this doing ? : return Eval( bOldErrHandler, e ) Should I close all files, end object, fonts,.... ...

... (b)BUILDMENU( 517 ) I want this error to have a better solution to close the program, but it is standard FW How can I use FW errorsys.prg and trap the errors that are not insite the errorsys.prg. Can I call a extra function for the missing errors ?

Don't know if this is what you are looking for ..

Code: Select all  Expand view

ACTIVATE DIALOG oDlg  ;
            VALID(!GETKEYSTATE( 27 ))
 

Very simple code to trap or exclude the ESC Key

Rick Lipkin

Hello Mod-harbourers; I have started using ModHarbour but so far not so much to build html pages but to trap webhooks. A webhook is a POST request sent to a page from services to notify or transmit certain data. There is something I still can't figure out about Modharbour. ...

... runtime error if the range in the exel file is not good defined. empty colums/rows are the cause, already mentioned in the forum. I would like to trap the error so that the program will popup a message that the range in the exel file should be better determent. Now should I do it in my own errorsys.prg ...

... as subscript out of range. Ahh.. So the program executes the loop before we do the activate ? This can explane why i have spend time in order to trap errors and have been making workarounds :D :D

Rick.
Got it.
Thanks for your kindly.

Francisco

Enrico's solution is much better than mine .. I actually modified the xBrowse.prg code ..

Rick Lipkin

Great! Enrico.
Thanks

Here it is: #include "Fivewin.ch"FUNCTION MAIN()    LOCAL oDlg, oBrw    USE CUSTOMER    DEFINE DIALOG oDlg;           SIZE 800, 600    @ 0, 0 XBROWSE oBrw    oBrw:bChange = { || Test() }    oBrw:CreateFromCode()    ACTIVATE DIALOG oDlg;             ON INIT...

Enrico.
Can you post a litle sample?
Thanks

I faced this problem this days and solved using bChange.

EMG

Hi Rick.
Do you resolved it?
Can share your solution?

Best regards.