Sign in to follow this  
Followers 0
matrix200

Gdiplus refresh issue

5 posts in this topic

Well I was not able to find any mention of that in the forum.

Forgive me if I missed.

Anyway all gdiplus examples in the help files lack a very important thing.

Since gdiplus functions drawn stuff is not being repainted on WM_PAINT event I think it could be useful to add an

appropriate GuiRegister handler to have them refreshed.

I was trying various examples and couldn't figure out why things would dissappear after I minimized and restored the window.

Share this post


Link to post
Share on other sites



i dod the task with GUIRegisterMsg($WM_ACTIVATEAPP, "APPACTIVATE")


-- Arck System _ Soon -- Ideas make everything

"La critique est facile, l'art est difficile"

Projects :

[list] [*]Au3Service : Run your exe as service V3 / Updated 29/07/2013 Get it Here [/list]

Share this post


Link to post
Share on other sites

Since gdiplus functions drawn stuff is not being repainted on WM_PAINT event I think it could be useful to add an

appropriate GuiRegister handler to have them refreshed.

So what exactly is stopping you from registering a WM_PAINT handler?

"be smart, drink your wine"

Share this post


Link to post
Share on other sites

Nothing stops me from doing that.

I am just pointing out that the code examples that come with Autoit are "buggy" and it would be a better idea to have a WM_PAINT handler included in the example scripts.

And arcker how come you use $WM_ACTIVATEAPP?

If I understand right this event would be fired when the window becomes active.

I think this is a problem since you might have another application blocking partly or fully your window and then your window would remain inactive and you might end up with "damaged" window content.

Share this post


Link to post
Share on other sites

Nothing stops me from doing that.

I am just pointing out that the code examples that come with Autoit are "buggy" and it would be a better idea to have a WM_PAINT handler included in the example scripts.

And arcker how come you use $WM_ACTIVATEAPP?

If I understand right this event would be fired when the window becomes active.

I think this is a problem since you might have another application blocking partly or fully your window and then your window would remain inactive and you might end up with "damaged" window content.

Not "buggy", just the wm_paint wasn't implimented in the examples. There is nothing wrong with the examples they show exactly what they are supposed to show.


SciTE for AutoItDirections for Submitting Standard UDFs

 

Don't argue with an idiot; people watching may not be able to tell the difference.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0