forums.silverfrost.com

[Bartl]

Hello,
I have no experience with grafic functions.
Is their a possibility to insert grafic functions like
call DRAW_LINE_BETWEEN@(IX1,IY1,IX2,IY2,ICOL)
into the gray field opend with i=winio@(%ca.....) without border?

[LitusSaxonicum]

Johann,

No, it isn't part of Clearwin.

Possible close approximations to what you want are as follows:

1. Do part of the window, then use %bx to draw a 3D horizontal line

2. Choose to create a status bar

3. Use a bitmap as window background, or import a bitmap the full width of the window.

I have used 1. a lot, but was disappointed by 2. Option 3. seemed to me to demand too many big bitmaps.

4. Introduce a big, borderless, %gr area, and draw on that.

Eddie

[PaulLaidler]

DRAW_LINE_BETWEEN@ is a ClearWin+ routine for drawing to a %gr region in a call to winio@.

[LitusSaxonicum]

Here is my example using %bx:

[Bartl]

Hello Eddy,
thank you for your example, this is a good idea.
In the meantime I tried another solution as follows:

[LitusSaxonicum]

Hi Johann,

I think I misunderstood your original question (and so did Paul) - I thought that you wanted a separator in an ordinary window.

What your example shows is that you want to draw a graphic in a borderless region with the same background colour as the rest of the window, and you want to update it. That is always done in a %gr region (or %dw or %og).

[jalih]

[LitusSaxonicum]

I wanted to be first!

Putting your creation of graphics in line with all the other WINIO@ calls is OK when it is simple, but looks clumsy if the image is complex. A better strategy is to put the graphics creation in the callback to a %sc format code.

If your %gr area was a bit smaller (200x200 is large for what I will suggest) AND there were a limited range of pictures you wanted to display, then you could use the IMPORT_IMAGE@ routine, and import images of rather complex detail.

Eddie

[jalih]

[LitusSaxonicum]

Jalih,

If you want to hang screen redraws onto a timer %dl, then the delay has to be quite small. The screen redraw routine then has to operate from a set of variables, some of which are changed by user interaction such as button presses, and in a game, some of which (parameters) are changed by the time-dependent aspects of the game itself.

I prefer to call my screen redraw routine after every user action. This demands an initial draw before there is any interaction - and that is via %sc. My screen redraw routines tend to be quite long, as they contain options that may not be executed every time, just as my graphics callbacks have lots of code to cater for all possible click combinations, including some that are screen location specific.

Eddie

[jalih]

[LitusSaxonicum]

Hi Jalih,

I went away and read your Tetris code. Your timer delay is 1/60 sec, and of course you need this approach because even with no user interaction, the blocks keep falling. In my programs, nothing happens until the user selects a control - more like a game in which the computer and the user take turns.

Your code is elegant and effective. I might not do things the same way. For example where you have a keyboard monitor, and process the small number of key options, I would probably associate a keyboard accelerator %ac with my controlling keypresses. I would not make use of buffered display, but write things to the screen immediately. And so on. Not necessarily better, but an alternative way to do things.

It is almost certain that the original poster was not thinking of anything as sophisticated as your Tetris game!

Eddie

[jalih]

[Bartl]

Hi,
thank you very much for all comments, it's very interesting.
Due to all comments I found exact that what I want, see following code as example:

[LitusSaxonicum]

ENTER is OK, but you can update your rectangle with a callback to each %rd: