Hi Pritpal,
Having said that I propose these constants: HB_GTI_MESSAGE HB_GTM_HWND HB_GTM_SHOWWND HB_GTM_CREATEWND HB_GTM_CLOSEWND HB _GTM_SELECTWND HB_GTM_CENTERWND HB_GTM_PROCESSMSG HB_GTM_INVALIDATE HB_GTM_SETTIMER HB_GTM_KILLTIMER HB_GTM_KEYBOARD HB_GTM_MAXIMIZE HB_GTM_MINIMIZE HB_GTM_SETONTOP HB_GTM_SETASNORMAL HB_GTM_MOUSEPOS HB_GTM_USER These are some specific messages a window can manipulate and these are generic ones. Every GT cn take use of it in some form or the other. Particular GT specific messages will start at HB_GTM_USER + nMessage. For example: Hb_GtInfo( HB_GTI_MESSAGE, HB_GTM_SHOWWND, SW_HIDE ) Opinions, suggestions, restrictions, etc.
To put it shortly: No way. This is my opinions for all the above. Sorry but what you try to implement here _completely_ out of scope of Harbour GT. All the above are direct Windows API interactions, which I believe belongs to hbwhat32, hbw32 or gtwvg but certainly not to core GT. Harbour is a multiplatform project, so anything what is platform specific shouldn't be part of the core. All of the above can be easily added to a contrib library with no side effects at all. Maybe hbwhat32 already have them even. This has been the goal since 1999, ans it hasn't changed since. Brgds, Viktor _______________________________________________ Harbour mailing list [email protected] http://lists.harbour-project.org/mailman/listinfo/harbour
