Observando o arquivo ChangeLog.TXT no Git do Harbour 3.4, notei essas alterações na GTWVG/GTWVW:
O problema não é entender o inglês... mas queria entender de forma mais detalhada o que realmente mudou internamente. O que seria essa sigla "VF" ?2017-09-09 18:28 UTC Viktor Szakats (vszakats users.noreply.github.com)
* contrib/gtwvg/wvgwing.c
* contrib/gtwvg/gtwvglo.h
* WVG_PREPAREBITMAPFROMFILE(): rewrite to use VF file I/O instead
of CreateFile() Windows API
* contrib/gtwvg/gtwvg.h
* contrib/gtwvg/wvgcore.c
* contrib/gtwvg/wvgcuig.c
* hb_wvt_gtLoadPicture(): rewrite to use VF file I/O instead of
CreateFile() Windows API. [INCOMPATIBLE] for C code that called
this function directly, as the input filename is now a char *
instead of an LPCTSTR. Harbour-level functions affected:
wvg_SetGObjData(), wvg_Image(),
wvt_LoadPicture(), wvt_LoadPictureEx()
* hb_wvt_gtLoadPicture(), hb_wvt_gtLoadPictureFromResource():
define and export these on WinCE too, they will act as dummy
functions on this platform. Previously it remained undefined
instead.
* contrib/gtwvg/wvgcore.c
* hb_wvt_DrawImage(): rewrite to use VF file I/O instead of
CreateFile() Windows API.
Harbour-level functions affected:
wvg_DrawImage(), wvt_DrawImage(), wvt_DrawButton(),
wvt_DrawProgressBar()
* contrib/gtwvw/gtwvwd.c
* hb_gt_wvw_LoadPicture(): rewrite to use VF file I/O instead of
CreateFile() Windows API.
; After these updates, gtwvg/gtwvw no longer accesses the filesystem
directly. All VF filters/features work in filenames passed to them.