FiveTech Software tech support forums

Antonio, As I said, it's a silly example, but it causes the event to fire repeatedly. In the real world, I have calculations tied to the ON CHANGE clause. The problem is, they run even if the value is already set and unchanged. The fix in my original post solves the problem. My ultimate question, re...

What do you need this clause for ?

Code: Select all  Expand view

...  ON INIT ( oDlg:Refresh(), oDlg:Update() )

try to remove it. Unless I am missing something, I think that you don't need it

Antionio, Here is a modified testrad.prg to demonstrate the problem. It's a silly example, but it demonstrates how many times the bChange block is exectued. See below for the problem id and fix: // Radio Buttons management sample#include "FiveWin.ch"//--------------------------------------...

Please try and review FWH\samples\TestRad.prg

That example uses the ON CHANGE clause and here it works fine

Activate Dialog etc.. On Init SetRadioChange()

Procedure SetRadioChange()
oRadio:bChange := {|| MyFunctionWhenChange() }

Return


[;)]

I am having a problem with the ON CHANGE clause of the Radio class(es). It seems the ON CHANGE event is firing when the dialog or window containing the Radio button is updated, even when the value is unchanged. Is this by design or a bug?

Thanks.

... and if you close your database or recordset with a valid close under certain circumstances .. ( unknown as of yet ) the Windows paint trigger fires and that is where we end up with a problem .. the data or record set is closed and destroyed and when the window tries to re-paint .. the window ...

Hi, can some help me

i have two DBcombo in my dialog,I Populate the second DBcombo on the ON CHANGE event of the first one.
But the problem is when the on CHANGE event of the first DBcombo fires the second DBcombo is populated But the first element is displayed as blank.

Regards,
sajith

... _VehClose(.T.) ), .F. )) Antonio made this suggestion so that the listbox does not repaint .. but for some reason the setado method still fires even after the oRs:Close() .. and that is why we tried to work around that in that method to avoid the nil value of oRs .. :cry: Rick In that ...

... _VehClose(.T.) ), .F. )) Antonio made this suggestion so that the listbox does not repaint .. but for some reason the setado method still fires even after the oRs:Close() .. and that is why we tried to work around that in that method to avoid the nil value of oRs .. :cry: Rick

... everything down nicely and exit the program. Compile the code and cut and past the utilmenu.rc and link .. when you close Utilmenu .. the valid fires and I can trap that .. re-open Utilmenu and then 'x' out of the MDI frame .. and you will notice the Utilmenu valid does not fire .. but the MDI ...

... very wrong here. I am taking my 'listbox' code for an ADO recordset and modifying it for xBrowse. The program compiles .. but when the browse fires ... all I get is a Grey mdichild window .. no data .. just blank. Here is the code : oRs:MoveFirst()DEFINE WINDOW oGRP                 ...

... * New: New clauses ACTION ... [ BITMAP ... ] for GETs. FiveWin automatically creates a themed button on the GET which fires an ACTION, and you can change the GET contents from it too. Please review samples\getbtn.prg and getbtnr.prg. No need to change your current resources ...

It is like Antonio (AHF) says:
>When I drag email messages the FWH does not fires any message to be worked upon. It simply put the forbbiden cursor.
I think DragAcceptFiles() is a API call not a OLE one.
Regards,
Otto

James,

When I drag email messages the FWH does not fires any message to be worked upon. It simply put the forbbiden cursor.

Antonio