On 30/06/17 04:06, Wolf via Ql-Users wrote:
Hi,
There seems to be 2 differences between PAUSE and WAIT.
PAUSE needs channel #0, WAIT doesn't.
True
PAUSE can be interrupted with a keypress, WAIT can't.
True
Wait comes from the outptr toolkit (on my QLStuff webpage, pointer
tools). It
Hi,
There seems to be 2 differences between PAUSE and WAIT.
PAUSE needs channel #0, WAIT doesn't.
True
PAUSE can be interrupted with a keypress, WAIT can't.
True
Wait comes from the outptr toolkit (on my QLStuff webpage, pointer
tools). It just suspends the calling job for x ticks : W
Does WAIT suspend a Job? If so, it is different from PAUSE, maybe no
matter in this case.
Dilwyn has used a similar thing from my extensions to make a new
Keyword to suspend a Job.
The extension Ralf referred to here is called SUSPEND.
Available on Toolkits page at http://www.dilwyn.me.uk/tk/
Of course, as it is used to suspend the job.
Am 29.06.2017 um 19:48 schrieb François Van Emelen via Ql-Users:
Op 29/06/2017 om 17:11 schreef Ralf Reköndt via Ql-Users:
Does WAIT suspend a Job? If so, it is different from PAUSE, maybe no
matter in this case.
Dilwyn has used a similar thing fr
Op 29/06/2017 om 17:11 schreef Ralf Reköndt via Ql-Users:
Does WAIT suspend a Job? If so, it is different from PAUSE, maybe no
matter in this case.
Dilwyn has used a similar thing from my extensions to make a new
Keyword to suspend a Job.
Am 29.06.2017 um 12:58 schrieb Wolf via Ql-Users:
S
Does WAIT suspend a Job? If so, it is different from PAUSE, maybe no
matter in this case.
Dilwyn has used a similar thing from my extensions to make a new Keyword
to suspend a Job.
Am 29.06.2017 um 12:58 schrieb Wolf via Ql-Users:
Sorry, yes it is.
On 29/06/2017 12:04, Derek Stewart via Ql
Sorry, yes it is.
On 29/06/2017 12:04, Derek Stewart via Ql-Users wrote:
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HO
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit you
On 28/06/17 10:12, Wolf via Ql-Users wrote:
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit you
Hi Derek,
100 DEFine PROCedure p
110 ERT HOT_KEY('g',CHR$(27))
120 EX RAM1_Dm5_Obj
130 WAIT 20
140 HOT_DO('g')
150 WAIT 20
160 HOT_DO('g')
170 WAIT 20
180 HOT_DO('g')
190 ERT HOT_REMV('g')
200 END DEFine p
Adjust the key, timings and drive to suit your system.
At least you won't have to type in
On 27/06/17 13:01, Marcel Kilgus via Ql-Users wrote:
Derek Stewart via Ql-Users wrote:
Does anyone know of any contact for PM_DATA, to see if the DM5 source
code can be released, to correct the problem.
He would if he could, but apparently he doesn't have the sources anymore.
Marcel
___
Derek Stewart via Ql-Users wrote:
> Does anyone know of any contact for PM_DATA, to see if the DM5 source
> code can be released, to correct the problem.
He would if he could, but apparently he doesn't have the sources anymore.
Marcel
___
QL-Users Mai
Hi,
I have been looking at the problem with Disk Mate 5 on QPC2 &
SMSQmulator and every time I load Disk Mate 5 I am prompted for the
current date.
Since the Year is only 2 digits this is causing a problem, since we are
now in 2017. I think the programme must be thinking the date is 1917
ra
Op Fri, 13 Jan 2017 06:41:10 +0100 schreef Wolf :
Hi,
there ae 2 versions of DM : DM5_obj and DM5_int_obj , the problem only
seems to arise on the..int version, use the other one instead.
Minor point is that only the _int_ version has been patched for GD2.
I just installed both versions in
Wolf wrote:
>> Do you think the source ocde could be released.
> It would be nice, but I presume the author would aready have done so by now.
Problem is, even the author doesn't have the source code anymore.
Marcel
___
QL-Users Mailing List
Hi,
I tried both and give the same date problem.
Here, they both protest that the date is wrong, but only the ...int
version crashes QPC, the other works OK..
The file Extensions_cde looks like it is DIY Toolkit extensions, Phil
Borman's WIN Tools. Which I doubt have any problems.
This
Hi,
I tried both and give the same date problem.
The file Extensions_cde looks like it is DIY Toolkit extensions, Phil
Borman's WIN Tools. Which I doubt have any problems.
In the updates_doc, there was an issue with v5.05 getting the months
wrong, maybe the invalid date is connected to this.
Hi,
there ae 2 versions of DM : DM5_obj and DM5_int_obj , the problem only
seems to arise on the..int version, use the other one instead.
Wolfgang
On 12/01/2017 17:47, Martyn Hill wrote:
Hi Bob
Just to confirm that I too have been unable to run DM5 on QPC (v4) and
saw oddities around the da
Bill,
Feeling fine now and traffic looks OK, so see you there.
Dave.
Sent from my iPad Pro
Tel: +44 (0)1707 652791
Mobile: +44 (0)7999 218953
> On 12 Jan 2017, at 16:47, Martyn Hill wrote:
>
> Hi Bob
>
> Just to confirm that I too have been unable to run DM5 on QPC (v4) and saw
> oddities a
Hi Bob
Just to confirm that I too have been unable to run DM5 on QPC (v4) and
saw oddities around the date before it would hang QPC.
I didn't investigate to the same depth, but it appears to match your
experience.
Martyn.
On 12/01/2017 15:35, Bob Spelten wrote:
Hi All,
I was trying to ge
Hi All,
I was trying to get DiskMate5 to run in QPC2/QLE but ran into a serious
problem.
It reported a wrong date but while the suggested date was correct my PC
clock had been reset in the background to 18-Jan-2053, causing problems on
the W$7 side.
In my QPC2/QLE this also froze SMSQ/E bu
21 matches
Mail list logo