Op 18/10/2019 om 13:01 schreef Bob Spelten via Ql-Users:
op Fri, 18 Oct 2019 11:34:46 +0200 schreef pjwitte via Ql-Users
<ql-users@lists.q-v-d.com>:
On 18/10/2019 11:17, François Van Emelen via Ql-Users wrote:
Hi,
Can someone confirm what happens in line 220?
In a menu created with Easaymenu (Easyptr) there is a Loose Item to
allow the menu to be moved.
Configuration A: the key for that Loose Item is CRTL E, seems to be
the default value.
Configuration B: I replaced the default key with value 77 (‘M’) for
Move.
….
200 SELect on ObjectHit
205 = -1:Remark do something
210 = -2:Remark do something
215 =- 3:Remark this is the move Loose Item
220 :Remark do something
….
With Configuration A, WM_movemode 0,1,2,3 can be used but line 220
is never executed. Why?
With Configuration B, line 220 is executed but only WM_movemode 0
(the old way, using the “move window” sprite) is available. Why?
Is this a feature, a bug or am I missing something?
Help and explanation are welcome.
François Van Emelen
In A. the Move window call is trapped by the system, so it never
reaches line 220. In B. you need to add the instruction to move the
window, for example WMOV. This gives you the opportunity to carry out
other stuff before and after the the move instruction. The standard
key for this is CF4, tho'.
WMOV has evolved over the years, so make sure youre using the latest
version of ptrmen_cde to get the best. Get it directly from Marcel's.
On my Knoware.no site, for example, there are a number of PE programs
with source code included. They show a variety of ways you can do this.
Per
According to the EP manual (p71) a -1 parameter should also give the
WM_MOVEMODE options to WMOVE.
Bob
Hi Bob,
EP manual (p71)? Are you referring to the Easyptr manual ?
François
_______________________________________________
QL-Users Mailing List