Entry screeshot current window to a file

[Eugene Lutsenko]

Now will do.

PS
I can Still say that if you remove the commands associated with the rotation of the image, the image itself of course it turns out not like what I would like, but it is recorded normally. And after the rotation somehow doesn't work like main menu (linear and flowing).

[Eugene Lutsenko]

=1
Once in the cycle

[rdonnay]

When you use WTF .. PAUSE, it stops program execution.

At that time, you should still see your screen image as visible.
Is it still visible to you?
If it is not, then DC_Scrn2ImageFile() would not work.

[Eugene Lutsenko]

When you use WTF .. PAUSE, it stops program execution.

At that time, you should still see your screen image as visible.
Is it still visible to you?
If it is not, then DC_Scrn2ImageFile() would not work.

Hey, Roger!

And when debug statements was not, and now that they are on the screen all is visible perfectly as it should be

[rdonnay]

I am not sure what to tell you next.
Are you saying that everything works only when debugging is in the code?

[Eugene Lutsenko]

I am not sure what to tell you next.
Are you saying that everything works only when debugging is in the code?

The screen displays always: when the debug is, and when it is not. A record in a file never works, there are debugging or not: you still file a black. But if there is no rotation, everything is written in the form of a file normally. Now I make a small simple example.

Almost as the square of Malevich:)

[rdonnay]

You may have forgotten to unlock the presentation space of oStatic1.

oStatic1:unlockPS()

[Eugene Lutsenko]

You may have forgotten to unlock the presentation space of oStatic1.

oStatic1:unlockPS()

Unfortunately it didn't help. The attached file is a simple example which I started to do but could not finish because of gaps in knowledge. But I'm sure that You just glance at it to understand the idea and understand what is my mistakes.