... the above line like this. oDtpFirst:bchange := { | oDtplast, oGrs1 |( oDtpLast:SetRange( dFirst ), oGrS1:Update() ) } James, NO, this is not the piece that didn't work but the piece that didn't work is this: @ 20,100 DTPICKER oDtpFirst VAR dFirst SIZE 200,28 PIXEL OF oGrS1 ; ...
... see on this topic http://forums.fivetechsupport.com/viewtopic.php?f=3&t=40344&sid=096b78133ff43210636e86df0f01f042#p240896 I inserted the piece of the two controls above a ribbonbar as created by Nages (changing only the position coordinates of the controls) always makes me the same ERROR ...
... Is the second way the way it should be done in order to use ALL options in FWH or is it the same ? Not exactly. Remember you need to write each piece of code only once . Thus, define a class for each database like the sample below. I put all the database classes into one PRG. Now your database ...
... is supported by FiveWin by the TCalendar class. What I saw, trying the testcal sample is the some animations are missing, I fixed it adding these pieces of code on the sample (and on every use) // my fix __objDelMethod(oCal, "HandleEvent" ) __objAddMethod(oCal, "HandleEvent", ...
Hi Otto, see this piece of code: bDraw := {|hDC,x,y| FW_DrawImage(hDC, oMarker, {y-30,x-10,y,x+10},.t.) } oMap:AddMarker(13.7025,42.6582,30,bDraw) The method AddMarker has parameters: Longitude, ...
... the standard FWH version. It looks like your own adaptation and you need to look for answers yourself. Mr. Rao, I think that a original old code piece of fivewin. Regards Even in the older versions, this code was applicable to 16-bit Clipper only but never to 32-bit FWH. Taken from FWH 08.02 ...
... found any sample of Xbrowse that is used this way (I would like a sample :D :D ) I am not sure if this is what you want. Please try this small piece of code: USE CUSTOMER XBREPORT oBrw DATASOURCE "CUSTOMER" ; COLUMNS "FIRST","CITY","SALARY" ...
... This reduces the chance of bugs, makes writing code using the class easier, etc. oLotto := TLotto():New() Short, and easy to read. Write each piece of code only once. I know it on gif you can see is a tdatabase version on this app I use only two archives I tried also with your tdata and I ...
... This reduces the chance of bugs, makes writing code using the class easier, etc. oLotto := TLotto():New() Short, and easy to read. Write each piece of code only once.
... a problem I fix it as soon as I can. TData was designed to handle as much of the repetitive coding as possible. The philosophy was to write each piece of code only once. So, in this case, it handles all scatter and gather routines, record locking, buffering, loading and saving the data all done ...
Nages, I tried another piece of source search on this forum a topic "problem with tdatabase" where Uwe answered me. The source i insert on first message run ok with tdata But not with tdatabase . Then i resolved with the help ...
... to C++. You must add Emf2Pdf.cpp to your project, adding the define __HARBOUR__ to c compiler (with command line -D__HARBOUR__) in this way this piece of code at end of emf2pdf.cpp will be compiled: #ifdef __HARBOUR__#include <hbapi.h>#include <hbhpdf.h>HB_FUNC(HPDF_ADDEMF) ...
Uwe, I had only copied a piece of my source back this is the original WITH OBJECT oApp():oGrid :nRowHeight := 40 WITH OBJECT oApp():oGrid:aCols[ 1] ...