[ql-users] CUCPS talk
This might be of interest: http://www.cam.ac.uk/societies/cucps/20012002/ Pity no-one took pictures. Ben in particular enjoyed displaying his Powerpoint slide show using a video projector onto a giant screen. It ended with him playing 'Theme Hospital' on the same screen! Marcel - the HP talk is mentioned with links to detail. -- QBBS (QL fido BBS 2:252/67) +44(0)1442-828255 tony@.co.uk http://www.firshman.co.uk Voice: +44(0)1442-828254 Fax: +44(0)1442-828255 TF Services, 29 Longfield Road, TRING, Herts, HP23 4DG
Re: [ql-users] WMAN progress
In a message dated 03/12/02 05:41:14 GMT Standard Time, [EMAIL PROTECTED] writes: If what you want to achieve is something like the little help windows in FiFi, this was done as follows: The user can determine the time the pointer should hover over the loose item before the help window pops up. Say it is 1 second. I read the pointer witt a very short timeout (2/50th sec) and then, when coming back, check whether the current item is still the same. If it is, I loop around until 1 s has elapsed (25 times in this case) and, if it is still the same LI, I open the help window. Else, I note the new current item number and do it again. I have successfully produced my own explanation windows now by WM.RPTRT on your advice. However, I look to see where the pointer is on a timeout (comparing the pointer position with each of the hit areas of the loose items). If it is a loose item I set its own window. If not I do nothing. Probably there is an easier way of dong this too! George
Re: [ql-users] WMAN progress
In a message dated 02/12/02 17:27:21 GMT Standard Time, [EMAIL PROTECTED] writes: There is a benefit in using iop.rptr I would imagine, that would be keeping it simple in situations you want to read the pointer without actually producing anything on screen (ie by shutting off SCR0 (This can be useful if you want to write custom Aurora 256 mode programs that move a custom pointer sprite instead of the WMAN one--- Of course all that until we finish the GD2 adaptation for Aurora ;-) Phoebus Yes. I use iop.rptr to move an object around the screen. In fact, because I want this to be available on machines without GD2 I only use the old 4-colours. But I could quite easily make the object any GD2 colour. George
Re: [ql-users] WMAN progress
In a message dated 03/12/02 00:31:25 GMT Standard Time, [EMAIL PROTECTED] writes: From your original message I got the impression that perhaps you have an older version of the manual. For example there is no mention of WM.DRBDR on my page 86. In my manual WM.DRBDR is described on p 88 and it correctly says that is vector $44. So perhaps the description in your manual is incomplete too? It says here: To clear the current item, set the msb of WS_CITEM and, if WS_CIACT is clear, call WM.DRBDR, otherwise call the routine pointed to by WS_CIACT and then clear WS_CIACT. To set a current item, set WS_CITEM, WS_CIBRW, WS_CIPAP (to the highlight colour) and the hit area WS_CIHIT. Then call WM.DRBDR. Finally reset WS_CIPAP to the background colour, and Bobs your aunt's live-in lover! Yes indeed! This is exactly (barring BYLL) what's on my page 86. I must be the one whose subs are out of date! Anyway the actual routine still doesn't do what the manual says. <> > As to the use of iop.rptr, this does not put lines around any item and take > them, away. wm.rptr(t) does but you can't mix both. > > It would certainly be nicer if you could use wm.rptrt than iop.rptr. However, > does that also deal with "dragging"? Have you tried: repeat wm_loop wm.rptr if drag_item is hit then repeat iop_loop iop.rptr if not keydown exit iop_loop keep dragging end iop_loop endif end wm_loop I'll certainly try this. Thanks. Its remarkably difficult to get right, but I think it can be made to work. ALL PE is immensely hard! But in TurboPTR I am reasonablr happy. In C it is more of a problem - but I'm getting there. So I'll try that too. Per George
Re: [ql-users] WMAN progress
In a message dated 03/12/02 00:31:08 GMT Standard Time, [EMAIL PROTECTED] writes: I have four pages of updates (also undated) that takes me from wm.erstr to sms.wevt, but no mention of wm.rptrt. The pages QPTR Updates have Addnl Info on WM.ERSTR and WM.LDRAW on page1; additions to IOP.RPTR on page 2; the "new" sms.sevt and sms.wevt on page 3; the "new" WM.RPTRT on page 4. Perhaps Per's page 4 was missing? George
Re: [ql-users] Menu_rext
Thanks Roy ,Please E.mail the updates; I bought DataDesign and it would not work until I removed v7.60 and replaced it with 7.03. I sent for Qmenu not realizing it is Menu_rext. I reinstalled v7.6 and the latest Outln_rext and Datadesign worked. To use it in my boot program I had to include Ext_menu_rext from ProWess files. Every thing seem to be working now. > > > >Arnold Clarke wrote: > >> I am having a problem with Menu_rext 7.60 because it crashes QPC .I > >> can still use Menu.rext 7.03 no problem. Can anyone help?. > > > >Well, I'm using 7.64. I don't know what changes there were but > >probably this helps. > I have been using and selling v7.60 with the software I sell. Jochen has > now updated me and I will pass the updates on for free to anyone who > send me a software disk with a SAE for the return postage. I can email > the update to you Arnie if you want or I will send it from free since > you just got it from me this week. Let me know. > -- > Roy Wood > Q Branch, 20 Locks Hill Portslade. Sussex. BN41 2LB. UK > Tel : +44 (0)1273 386030 Fax : +44 (0)1273 430501 (New number!) > Mobile +44(0)7836 745501 > Web : www.qbranch.demon.co.uk > > >
