Hi Roger,
It seems as dc_progress(0,,500) isn't always working.
If I try the sample from the docs, it gives an error. I suppose it needs a parent to define the position?
dc_progress
Re: dc_progress
why not look into Source C:\EXP19\Source\Dclipx\_dcodd2.prg?skiman wrote:Hi Roger,
It seems as dc_progress(0,,500) isn't always working.
If I try the sample from the docs, it gives an error. I suppose it needs a parent to define the position?
Code: Select all
PROCEDURE dc_progress ( nMode, nValue, nMaxValue, nStRow, nStCol, nEnCol, lBox, cColors )
greetings by OHR
Jimmy
Jimmy
Re: dc_progress
Hi Jimmy,
I lookeded in the sources and there is a row() and col(). These generate the error. They are no parameters.
In the sample in the docs, it is also used without all the parameters.
I lookeded in the sources and there is a row() and col(). These generate the error. They are no parameters.
In the sample in the docs, it is also used without all the parameters.
Re: dc_progress
I haven't used DC_Progress in many years. This is old stuff from my Clipper days.
Have you tried using @.. DCPROGRESS oProgres ...
And then:
DC_GetProgress( oProgress, nCount, nMaxCount )
Have you tried using @.. DCPROGRESS oProgres ...
And then:
DC_GetProgress( oProgress, nCount, nMaxCount )
The eXpress train is coming - and it has more cars.
Re: dc_progress
Hi ROger,
Yes, I'm using @.. DCPROGRESS oProgres for years.
I saw the dc_progress in the manual, and it seemed easier to use.
No problem for me, maybe you can delete it in the docs.
Yes, I'm using @.. DCPROGRESS oProgres for years.
I saw the dc_progress in the manual, and it seemed easier to use.
No problem for me, maybe you can delete it in the docs.