no mouse wheeling with txborowse in fwh9.08

[Detlef Hoefner]

Dear all,

since i updated to fwh 9.08 the users of my programs are upsetly missing scrolling a txbrowse by mousewheel.
Therefore they have kinetic scrolling which they don't like at all.
Is there way to get back the 'old' browse behaviour?

It would be nice to have new features with an additional switch like
@ 2, 5 TXBROWSE ... KINETIC ...
and keep the normal handling as it's used to be before.

Regards,
Detlef

[Ariel]

Detlef,

http://forums.fivetechsupport.com/viewt ... =6&t=16671

Regards.

[Detlef Hoefner]

Ariel,

thanks for your link.
Does this mean i have to rebuild the complete fivehc.lib after correcting the Clt2Scr.c?
This is something i don't know how to do.

Could you give me some more info please?

Thanks and regards,
Detlef

[Ariel]

Detleft,

Not, simply to add it at the end of your principal program. If you update your version of fwh deberas to see if already this incorporated and of being like that to extract it.

Regards

[Detlef Hoefner]

Ariel,

many thanks for your support.
I got it working now.

But i still find it no good idea to switch off the TxBrowse mousewheel scrolling without announcement and have a 'kinetic' navigation suddenly .

Just my 2 cents,
Detlef

[Otto]

Hello Detlef,
What exactly did you change to get the old behaviour.
Drag & drop for me is no longer working.
Best regards,
Otto

[Detlef Hoefner]

Hallo Otto,

i added the following code at the end of my program:

Code: Select all

#pragma BEGINDUMP

#include <hbapi.h>
#include <windows.h>

HB_FUNC( SCREENTOCLIENT )  //  ( hWnd, aPoint ) --> aPoint
{
   HWND hWnd = ( HWND ) hb_parnl( 1 );
   POINT pt;

   pt.x = hb_parvnl( 2, 2 );
   pt.y = hb_parvnl( 2, 1 );

   ScreenToClient( hWnd, &pt );

   hb_reta( 2 );
   hb_storvnl( pt.x, -1, 2 );
   hb_storvnl( pt.y, -1, 1 );
   hb_storvnl( pt.x,  2, 2 );
   hb_storvnl( pt.y,  2, 1 );
}
#pragma ENDDUMP
 

It's ugly that i have to do it in every program
May be it helps to resolve your problem.

Best regards,
Detlef

[Antonio Linares]

Detlef,

That change is a must cause recent harbour/xharbour changes.

But current FWH 9.09 includes all those changes, so there is no need to add such code to your app.

[Otto]

Hello Antonio,

I added the C-code. Now the mouse-wheel is working.
But drag & drop is still broken.

Best regards,
Otto

Application
===========
Path and name: C:\xWinhotel\xwinhotel.EXE (32 bits)
Size: 4,348,928 bytes
Time from start: 0 hours 0 mins 26 secs
Error occurred at: 24.09.2009, 12:00:31
Error description: Error BASE/1082 Argument error: -
Args:
[ 1] = U
[ 2] = N 23

Stack Calls
===========
Called from: .\source\classes\WBROWSE.PRG => TWBROWSE:LBUTTONUP(1260)
Called from: => TWINDOW:HANDLEEVENT(0)
Called from: .\source\classes\CONTROL.PRG => TCONTROL:HANDLEEVENT(1453)
Called from: .\source\classes\WBROWSE.PRG => TWBROWSE:HANDLEEVENT(1643)
Called from: .\source\classes\WINDOW.PRG => _FWH(3333)
Called from: => WINRUN(0)
Called from: .\source\classes\WINDOW.PRG => TMDIFRAME:ACTIVATE(952)
Called from: C:\develop8\WH_Fwh\XWINHO~1\WINHOTEL.PRG => MAIN(1132)

[James Bott]

Antionio,

I agree with Detlef:

>It would be nice to have new features with an additional switch like
>@ 2, 5 TXBROWSE ... KINETIC ...
>and keep the normal handling as it's used to be before.

That kinetic mousewheeling should be an option and that xbrowse should default to the original mousewheel behavior. This prevents current code from being affected (unless you want it to).

James

[Antonio Linares]

James,

Yes, we are going to turn the kinetic behavior into an optional behavior

[James Bott]

Antonio,

Great. Thanks.

I wonder if this would be a good use of classdata? Then you could just add one line to the start of your program and all xbrowses would get the kinetic behavior.

TXBrowse():lKinetic := .t.

This seems like the kind of property that you would want all instances of xbrowses in an app to have one way or the other. I can't imagine why you would want some one way and others different.

Anyone have comments on this?

James

[Antonio Linares]

Optional kinetic:

http://forums.fivetechsupport.com/viewt ... 669#p87669

[James Bott]

Antonio,

Very good, but I would still suggest that ::lKinetic default to .F. otherwise it breaks existing code. Programmers that want this behavior can still add it simply.

James