Re: [ql-users] info window colour
Wolfgang Lenerz schreef:
On 5 Jul 2005 at 9:07, François Van Emelen wrote:
(...)
MWINDOW #0,1! : REMark set #0 to size of info window 1
PRINT HELLO
This all seems pretty normal behaviour to me, even though (I stress) I don't
know Easyptr.
Basically, what these commands seem to be doing is printing to a channel
opened 'over' an info window, appsub window or whatever.
It is important to remember that the colours given in the system palettes etc
are ONLY used automatically by the objects drawn by WMAN itself.
Opening a (new) channel over any kind of window and then printing to it is
OUTSIDE of Wman- so the channel doesn't know what colour etc it should be
using.
Why not use
MWINDOW #0,1! : REMark set #0 to size of info window 1
wm_ink#0,hex$('0210')
wm_paper#0,hex$('020F')
Shouldn't that be HEX('0210')?
François Van Emelen
print
That way, you set the colours of that channel to the corresponding syspal
colours.
Hope this helps
Wolfgang
www.scp-paulet-lenerz.com
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
On 28 Jul 2005 at 19:14, François Van Emelen wrote:
wm_ink#0,hex$('0210')
wm_paper#0,hex$('020F')
Shouldn't that be HEX('0210')?
Yup
Wolfgang
www.scp-paulet-lenerz.com
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
Sorry for being incommunicado for a while. Wolfgang Lenerz' response is exactly right. If you want a window to use the system palette colour, simply make a WM_INK/WM_PAPER call with the corresponding system palette colour. What I didn't mention was that I was writing a program to work with and without WMAN2, by having two separate sets of menus in the same program, using the appropriate set of menus depending on whether the program is used on a non-WMAN2 system or not. Why would you want to waste your time doing this? We not only went to great pains updating the old WMAN to be compatible with SMSQ/E's WMAN2, the old PE is even freeware now! Why oh why would anyone still want to support older releases instead of just supplying the newer ones if needed? Marcel ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
See section 11.5 of Easyptr manual: Some Qliberator versions have problems with a separator , \ ! TO at the end of a parameter list (system crashes). Set a 'dummy parameter' (e.g. \0) behind it or look for a new version of Qliberator. I don't know which versions of QLiberator are affected, I tend to always follow the advice and add \0 to any list of parameters in an Easymenu command which ends with a separator. -- Dilwyn Jones - Original Message - From: Wolfgang Uhlig [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, July 06, 2005 8:02 AM Subject: Re: [ql-users] info window colour Am Tue, 05 Jul 2005 21:23:26 +0200 hat Dilwyn Jones [EMAIL PROTECTED] geschrieben: MWINDOW #0,1!\0 : REMark \0 is needed as a dummy extra parameter for QLiberator why is this? I've never heard of that and never used it. Even so my programs seem to run well :-? Wolfgang ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.8.8/37 - Release Date: 01/07/2005 -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.8.8/37 - Release Date: 01/07/2005 ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
Sorry for being incommunicado for a while. Wolfgang Lenerz' response is exactly right. If you want a window to use the system palette colour, simply make a WM_INK/WM_PAPER call with the corresponding system palette colour. Yes, I realised this was the way to do it. Problem solved. What I didn't mention was that I was writing a program to work with and without WMAN2, by having two separate sets of menus in the same program, using the appropriate set of menus depending on whether the program is used on a non-WMAN2 system or not. Why would you want to waste your time doing this? We not only went to great pains updating the old WMAN to be compatible with SMSQ/E's WMAN2, the old PE is even freeware now! Why oh why would anyone still want to support older releases instead of just supplying the newer ones if needed? Marcel Well, doing that will alienate all the people who don't use it at the moment. The Quanta survey showed how many people don't use SMSQ/E never mind modern stuff, but now it's all in place we probably need to go through a transition period to encourage people. My hope is that by providing some programs which will work on both platforms people may well start off using old mode 4 facilities and realise they can experiment with GD2/WMAN2 facilities. It will only be the smaller, less complex programs which do this. It's too much like hard work to catre for both the old and the new! -- Dilwyn Jones -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.8.8/37 - Release Date: 01/07/2005 ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
On 5 Jul 2005 at 20:23, Dilwyn Jones wrote:
(...)
If I can think of a way to ensure that the program does not try to use
wm_ink and wm_paper when using mode 4 menus I'll use this approach,
which is probably the best.
MWINDOW #0,1!\0 : REMark \0 is needed as a dummy extra parameter for
QLiberator
IF WMAN_VER$ = '2.00' THEN
WM_INK #0,$0210 : REMark info window foreground
ELSE
INK #0,0 : REMark for non-wman2 systems
END IF
Rather than checking wman version number it might be better (or an
alternative at least) to check for the existence of the wm_ink or
wm_paper keywords with something like IF EXISTS('WM_INK') THEN or IF
CHECK('WM_INK') THEN
Right, plenty of ideas for me to think about! Thank you everyone.
Ok, so you want to use different colours, depending on whether the systemuses
wman 2 or not.
Perhaps:
is_new%=EXISTS (WM_INK)
(or any similar check)
(...)
WINK #channel%, whatever%
(...)
:
def proc WINK (mychan%,myink%)
if is_new%
WM_INK #mychan%,myink%
else
INK #mychan%,myink%
endif
end def WINK
:
Wolfgang
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
Dilwyn Jones schreef: Can anyone help me with this little problem with Easymenu information windows. Which system palette colour corresponds to the initial ink colour for an info or application window without objects? I'm trying to use an info window for text output. The info window has no info object. Colours are set to system palette (actually using Marcel's colourway_bas, although result is the same with any of the QCoCo themes) I find that whatever the info window foreground or middleground colours are set to, the ink always seems to be white. MWINDOW #0,1! : REMark set #0 to size of info window 1 PRINT HELLO Hello is always white. Although an INK #0,colour statement would set the ink colour, it tends to defeat the object with System Palette, since the info window background might be light or dark, so an explicit INK #0,colour statement for the info window is not really good enough in case you end up with grey or grey or whatever! Hi Dilwyn, You're right. But isn't that the normal behaviour? Info Windows have no 'ink/foreground' attribute. (White is perhaps the colour by default in such a situation). You could solve the problem by creating an Info Object in your Info Window: setup info object text input: 1 space is enough) character size 0,0 (important if you want to use minob) attribute : select the ink/foreground you want In your program you could have this: MWINDOW#3,1! MINOB#3,1,1,'' PRINT#3,'HELLO' 'HELLO' will have the correct ink/foreground attribute. Hope this helps François Van Emelen ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
Francois wrote: You're right. But isn't that the normal behaviour? Info Windows have no 'ink/foreground' attribute. (White is perhaps the colour by default in such a situation). Why would we have all the attributes for information window and subsidiary information window in the system colour table? Wolfgang ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
Wolfgang Uhlig schreef: Francois wrote: You're right. But isn't that the normal behaviour? Info Windows have no 'ink/foreground' attribute. (White is perhaps the colour by default in such a situation). Why would we have all the attributes for information window and subsidiary information window in the system colour table? Wolfgang Well, that's the question/problem. Does EASYPTR recognize a 'Print' statement as an object of its own? Printing to an Application Window shows the same behaviour as printing to an Information Window: ink/foreground is white. Same behaviour with 'minput': ink/foreground is white on a stippled (black/magenta) background, which makes the text unreadable and there is no stipple background in Marcel's colourway_bas AFAIK. Before each 'minput' I have to change the foreground/background with ink#x,x:paper#x,y. Of course, I could be completely wrong here in assuming all this. François Van Emelen ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
On 5 Jul 2005 at 9:07, François Van Emelen wrote:
(...)
MWINDOW #0,1! : REMark set #0 to size of info window 1
PRINT HELLO
This all seems pretty normal behaviour to me, even though (I stress) I don't
know Easyptr.
Basically, what these commands seem to be doing is printing to a channel
opened 'over' an info window, appsub window or whatever.
It is important to remember that the colours given in the system palettes etc
are ONLY used automatically by the objects drawn by WMAN itself.
Opening a (new) channel over any kind of window and then printing to it is
OUTSIDE of Wman- so the channel doesn't know what colour etc it should be
using.
Why not use
MWINDOW #0,1! : REMark set #0 to size of info window 1
wm_ink#0,hex$('0210')
wm_paper#0,hex$('020F')
print
That way, you set the colours of that channel to the corresponding syspal
colours.
Hope this helps
Wolfgang
www.scp-paulet-lenerz.com
___
QL-Users Mailing List
http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
Am Tue, 05 Jul 2005 14:14:37 +0200 hat Wolfgang Lenerz [EMAIL PROTECTED] geschrieben: Basically, what these commands seem to be doing is printing to a channel opened 'over' an info window, appsub window or whatever. Ah yes, sounds logical !! I didn't look at it this way. Wolfgang ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
Well, that's the question/problem. Does EASYPTR recognize a 'Print' statement as an object of its own? Printing to an Application Window shows the same behaviour as printing to an Information Window: ink/foreground is white. Same behaviour with 'minput': ink/foreground is white on a stippled (black/magenta) background, which makes the text unreadable and there is no stipple background in Marcel's colourway_bas AFAIK. Before each 'minput' I have to change the foreground/background with ink#x,x:paper#x,y. Which defeats the object of using the system palette, of course. I have asked Marcel, I'll wait for his reply to see what the official line on this is. In the meantime, I will try your idea of setting a dummy object to alter the ink colour. -- Dilwyn Jones -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.8.8/37 - Release Date: 01/07/2005 ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
[ql-users] info window colour
Can anyone help me with this little problem with Easymenu information windows. Which system palette colour corresponds to the initial ink colour for an info or application window without objects? I'm trying to use an info window for text output. The info window has no info object. Colours are set to system palette (actually using Marcel's colourway_bas, although result is the same with any of the QCoCo themes) I find that whatever the info window foreground or middleground colours are set to, the ink always seems to be white. MWINDOW #0,1! : REMark set #0 to size of info window 1 PRINT HELLO Hello is always white. Although an INK #0,colour statement would set the ink colour, it tends to defeat the object with System Palette, since the info window background might be light or dark, so an explicit INK #0,colour statement for the info window is not really good enough in case you end up with grey or grey or whatever! -- Dilwyn Jones -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.322 / Virus Database: 267.8.8/37 - Release Date: 01/07/2005 ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
Re: [ql-users] info window colour
Which system palette colour corresponds to the initial ink colour for an info or application window without objects? I find that whatever the info window foreground or middleground colours are set to, the ink always seems to be white. You're right, I've never noticed that. Probably Marcel is able to fix this in EPtr, so that this colour is set to system palette information window foreground or perhaps middleground. Wolfgang ___ QL-Users Mailing List http://www.q-v-d.demon.co.uk/smsqe.htm
