Re: [Ql-Users] found unused stuff
Hi, I arrived late, but if RomDisQ is still available, it is fine for me to buy it, please let me know. I am trying since long time to find an Aurora , but so far no success. Maybe Derek will decide to start a batch of new Aurora production..:-) Regards Fabrizio On 19/10/2019 06:16, Kenn Van Hauen via Ql-Users wrote: Thank you Paul for sharing here. Yes, I would be interested in buying the Aurora from you. Please let me know how you???d like to proceed. All my best, Kenn Sent from my iPhone On 19 Oct 2019, at 01:54, paul via Ql-Users wrote: ??? While the mood is with me, I manage to get through a box or 3 that has been tucked away for years. Decided I could tackle the task once again the other day, and after the first box, settled for a smaller one as the last one today. FOUND: Knew I had the stuff, but a 'one of the top 10 life disasters' interrupted the using of these and I never returned to QL'ing like I used to. 1: Aurura COMPLETE, still in its padded envelope 2: ROMdisq, Complete also. Neither of these have been used once bought new. Any market for these? -- Paul Holmgren The history of liberty is a history of resistance. The history of liberty is a history of limitations of governmental power, not the increase of it. - Woodrow Wilson, New York, September 9, 1912 ___ QL-Users Mailing List ___ QL-Users Mailing List ___ QL-Users Mailing List
Re: [Ql-Users] WM_move_mode and Easyptr menu
Op 18/10/2019 om 11:34 schreef pjwitte via Ql-Users: 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 ___ QL-Users Mailing List Hi Per, Thanks for your reply. In my programme WMOW is of course present in line 215. Yes of course, in A. the call is trapped by the system. As for B. I'll have to investigate further. WM_MOVEMODE not working correctly is perhaps due to the menu itself created a long time ago with an older version of Easyptr. Of course, your site is not unknown to me: I visited it more than once. Thanks for your comments! François Van Emelen ___ QL-Users Mailing List
Re: [Ql-Users] WM_move_mode and Easyptr menu
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 : 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
Re: [Ql-Users] WM_move_mode and Easyptr menu
On 19/10/2019 17:00, François Van Emelen via Ql-Users wrote: Op 18/10/2019 om 11:34 schreef pjwitte via Ql-Users: 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 ___ QL-Users Mailing List Hi Per, Thanks for your reply. In my programme WMOW is of course present in line 215. Yes of course, in A. the call is trapped by the system. As for B. I'll have to investigate further. WM_MOVEMODE not working correctly is perhaps due to the menu itself created a long time ago with an older version of Easyptr. Of course, your site is not unknown to me: I visited it more than once. Thanks for your comments! François Van Emelen As Bob mentioned, you should use WMOV#ch; -1. This is supposed to work, but perhaps only with more recent versions of the ptrmen_cde toolkit. The current version is 4.10. However, sometimes EP reverts to the old Wmov method for reasons that are not always obvious (to me, at least). When this happens, it is usually because I did something wrong, ie some bug in my code. Good hunting! Per ___ QL-Users Mailing List
