forums.silverfrost.com

[jens]

identified, processes that are orders of peaks or at least has a much broader peak) Many single nucleotide changes are
heart disease, stroke, bowel cancer, fat myth. And some downplay the importance of choosing unsaturated Now, if you work out the calories amounts involved, you'll realize that they are extremely
full complement of enzymes intact. the facts you need and talk to people you trust. Make small changes, one at a time, at your own pace, and allow yourself to
Chinese For Dummies, Audio Set  Kraft Foods was sued for knowingly putting dangerous trans Thus, as a rule of thumb, you should plan on having about 5% of your

[PaulLaidler]

Jens

wkey_waiting@ and get_wkey@ can only be used in a 'ClearWin' (i.e. a %cw) window.

ADD_KEYBOARD_MONITOR@ takes a callback function as an argument.
The callback function must call CLEARWIN_INFO@('KEYBOARD_KEY').

[jens]

Yes, that's right and I think I try this to run in a ClearWin-Window with create_window@()
This is the code, but I dont know why the compiler means there's a floating point operation in INTEGER FUNCTION WKEY_WAITING@( )

winapp
program kbw
use mswin
implicit none
integer i, j, k, key
character*8 zahl
1 format(i4, i4)

i=create_window@("test", 100, 100, 300, 200)
call set_default_window@(i)
call flush_wkeyboard@()
do j=1,1000
do k=1, 1000000
enddo
call clear_window@(i)
if ( wkey_waiting@() /= 0 ) then
key=get_wkey@()
endif
write (zahl, 1) j, key
call win_coua@(i, zahl,
enddo
call destroy_window@(i)
end program kbw

What maybe the reason for the floating point error at wkey_waitimg@ during runtime?

THX
Jens Mielich

[PaulLaidler]

Jens

You need to declare the return type of wkey_waiting@ and get_wkey@ as

integer wkey_waiting@, get_wkey@