This is a little programming challenge I left with George Gwilt at the Quanta
workshop this weekend.
I’d like to create something which can behave a bit like an “auto-hide” Windows
taskbar, using the pointer environment.
If the pointer rests at the bottom of the screen (or any edge for that
On 16 Apr 2013, at 14:03, Dilwyn Jones wrote:
This is a little programming challenge I left with George Gwilt at the Quanta
workshop this weekend.
I’d like to create something which can behave a bit like an “auto-hide”
Windows taskbar, using the pointer environment.
If the pointer
Op Tue, 16 Apr 2013 15:03:28 +0200 schreef Dilwyn Jones
dil...@evans1511.fsnet.co.uk:
This is a little programming challenge I left with George Gwilt at the
Quanta workshop this weekend.
I’d like to create something which can behave a bit like an “auto-hide”
Windows taskbar, using the
I was asked to resolve a QPC problem with a boot program at the Quanta event
this number. We managed to resolve it, but are not sure how.
The member concerned had (mistakenly) used WM_INK and WM_PAPER to try to set
24-bit colour numbers after using a COLOUR_24 command. The computer concerned
On 16 Apr 2013, at 14:03, Dilwyn Jones wrote:
If the pointer rests at the bottom of the screen (or any edge for that
matter) for a couple of seconds, the program or taskbar (or whatever you use
it for) pops up, even if it was buried under other windows.
Sounds simple: might be simple,
I've just written a small program which has no window that you can see, has no
loose items, or indeed anything at all, except that it picks master basic (ID
= 0) when the pointer is moved to the top band of the screen. So yes it seems
simple.
Of course you would have to supply to this
On 16 Apr 2013, at 16:42, tobias.froesc...@t-online.de wrote:
how did you manage to detect where the pointer is without a window?
By having an invisible window by setting the MSbit of its attributes in the
window definition. This stops the window being cleared so that you see what's
beneath
By having an invisible window by setting the MSbit of its attributes in the
window definition. This stops the window being cleared so that you see what's
beneath it. Ie it's invisible.
Very elegant. A 0 sized window will probably do as well.
Wolfgang
Hi George,
By having an invisible window by setting the MSbit of its attributes
in the window definition. This stops the window being cleared so that
you see what's beneath it. Ie it's invisible.
Does the invisible window cover the whole screen by any chance? If so,
what happens to any
100 COLOUR_24
110 WM_PAPER #0,$FF : REM trying to set white
120 WM_INK #0,$FF : REM trying to set blue
In these lines, the top word will be ignored, even though he won't get
blue but some kind of stippled colour in line 120.
(the $ff will be trated as $, i.e. a 15 bit rgb
- Original Message -
From: Norman Dunbar
I remember a program I wrote for Dilwyn some years ago (I can't remember
the name of it though!) which opened a full-screen window for some
reason, which effectively disabled using the pointer to pick the other
running programs.
Same with
On 16 Apr 2013, at 17:10, Norman Dunbar wrote:
Does the invisible window cover the whole screen by any chance? If so, what
happens to any other program running beneath the invisible window when you
attempt to click on it with the mouse to pick it to the top of the pile?
The window
Bob Spelten wrote:
It's been done before.
In Cuedark you can assign a corner to act as On switch.
Move the pointer there and the screen saver will be invoked in a few
seconds.
The principle is the same, don't know how it's done however.
It directly checks pt_pos in the CON linkage block
Wolfgang Lenerz wrote:
100 COLOUR_24
110 WM_PAPER #0,$FF : REM trying to set white
120 WM_INK #0,$FF : REM trying to set blue
In these lines, the top word will be ignored, even though he won't get
blue but some kind of stippled colour in line 120.
Most likely that's incorrect memory
Op Tue, 16 Apr 2013 20:59:04 +0200 schreef Dilwyn Jones
dil...@evans1511.fsnet.co.uk:
(...)
130 WM_BORDER #0,3,??? : REMark a 3D border
(??? because I can’t remember the value used)
Darn - it would be a good idea to find out.
I'd bet that is the problem.
Have had problems with some 3d
On 16/04/2013 20:59, Dilwyn Jones wrote:
Wolfgang Lenerz wrote:
100 COLOUR_24
110 WM_PAPER #0,$FF : REM trying to set white
120 WM_INK #0,$FF : REM trying to set blue
In these lines, the top word will be ignored, even though he won't get
blue but some kind of stippled colour in line
16 matches
Mail list logo
