[GUI] Programming without form

Hey people!

Maybe you know the program Ukagaka?
(en.wikipedia.org/wiki/ukagaka)
Or maybe the good old eSheep?

I have a small question about the graphical engine. Both programs work without the normal rectangular windows forms. I know how to show a static unnormal programform (ew... my English..) but I don't know how to program such animated programs. I could imagine an engine with DirectX, but I don't think eSheep uses a big DirectX engine. Ukagaka uses an engine which is even able to draw single pixels on the surface over all other programs...

What I wanna ask is, how can I draw pixels where I want? Even over other programs...

I mean, desktopsidebar is able to do so, too and so on...

WEll, I hope you know what I mean

lol no one cares

with DirectX DirectDraw.

SetWindowRgn and FrameRgn functions may help you

Well? Did any of these suggestions help you? Don't just come and take from /prog/ and not give anything in return.

>>5
He's Japanese, they only leech, that is why we ban them all.

>>6
Troll less

I'm really busy with school, holidays start Friday so I couldn't check the informations so far.

I never wanted to use DirectDraw, because I always thought it could get in trouble with games, you know?

Um so is Ukagaka like that "Amusing Misuse of Resources" (AMOR) program for X?  I have that kitty run around my X desktop sometimes.

>>8

I don't know much about DirectDraw (I'm an OpenGL person because I want to be useful for more platforms than just Microsoft ones), but you shouldn't worry about it.  Running processes that use hardware accelerated graphics have their own drawing contexts, so it won't mess up any games.  At least, it shouldn't.  The last time I ever saw problems caused by multiple programs using hardware-accelerated graphics at the same time was on my old computer with its cheap-ass Riva128 card -- the problems went away when I replaced it with a GEForce2.  And that was back in like 2000 or 2001.  I imagine drivers and hardware these days are now designed around being shared-resource friendly.

Quoth the Tao of Programming:

There once was a master programmer who wrote unstructured programs. A novice programmer, seeking to imitate him, also began to write unstructured programs. When the novice asked the master to evaluate his progress, the master criticized him for writing unstructured programs, saying, ``What is appropriate for the master is not appropriate for the novice. You must understand the Tao before transcending structure.''

Learn those basic forms, kids.

LISP

^{Back to /b/, ``GNAA Faggot''}

Bringing /prog/ back to its people
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy
All work and no play makes Jack a dull boy