FiveTech Software tech support forums

... the keyboard lights say. Possible fixes are: 1) remove the item click at least on Num and Caps (but I would remove it on Ins also). 2) use the appropriate API to correctly change the lights status. For the point 2, the following sample is from Francesco Saverio Giudice: Code: #include "common.ch" ...

Hi everybody,

I am getting an error during compile. ..... gtwin.lib file missing. I am not getting such file in appropriate path. Could any one tell me where is it available?

Arindam

... function always returns zero in response to the WM_GETDLGCODE message, the window procedure for the predefined control classes return a code appropriate for each class. The WM_GETDLGCODE message and the returned values are useful only with user-defined dialog box controls or standard controls ...

... it belongs (xHarbour or FWH) ?. It doesn't matter if I/we use a windows' reserved name, but it's the return value that matters. It would be more appropriate to return the same value as the equivalent 16-bit, and DOS-Clipper, rather than giving me this surprise, realizing that this function was ...

... or for fun. ⋅ If you spend more time doing it than watching TV, people think you’re some kind of freak. ⋅ It’s not really an appropriate topic for dinner conversation. ⋅ There’s not enough taught about it in public school. ⋅ It doesn’t make any sense at ...

... I don't know what code triggers it. I do know that it happens across two different versions of xBuilder ( March 06, and October 05 ) , and their appropriate versions of FWH. The software on the October release has been running since December without a problem and suddenly this error started occuring ...

... this function fails, it returns an HRESULT error code. Remarks When this function is called, the input panel notifies the input method (IM) of the appropriate action to take, which is whether to adopt a hidden or visible state. On devices that have a limited display area, an application can call ...

... the keyboard lights say. Possible fixes are: 1) remove the item click at least on Num and Caps (but I would remove it on Ins also). 2) use the appropriate API to correctly change the lights status. For the point 2, the following sample is from Francesco Saverio Giudice: #include "common.ch" ...

... as on a screen, you likely wouldn't even be able to see individual letters. All we have to do is convert from the point size we want, into the appropriate logical size for the device. In this case the device is the screen, so we get the HDC to the screen, and get the number of logical pixels ...

... It has been a while since i used bcc compiler, i can not help you further. I am sure someone else will help you get the missing files or a more appropriate link to download them. If not, then please post a message on xharbour.org news. Richard