Sign in to follow this  
Followers 0
THECARDNEXUS

WPF and checksums

8 posts in this topic

trying to get pixelchecksums on a WPF platform GUI using I think .net 4.0. For some reason my checksums keep giving me the "screen below it" as the checksum value. I am not sure why autoit's checksum function is ignoring the window. Thoughts? is this a known issue?

Share this post


Link to post
Share on other sites



Bump? Help please. :graduated:

Share this post


Link to post
Share on other sites

Bump?

Share this post


Link to post
Share on other sites

#4 ·  Posted (edited)

Hey, I loaded up one of my WPF projects which plays video with a MediaElement control. I let it play some video and then used this script to watch response from PixelChecksum:

While 1
    $color = PixelChecksum(100, 100, 200, 200)
    ConsoleWrite($color & @CRLF)
    Sleep(500)
WEnd

The output from the ConsoleWrite:

3516219189
681447533
2964028469
3638388148
4111338171
3745841968
1990985828
627549878
2462512366
264911947
997709767
238698662
3684483589
1578230762
3882656256
3494904084
2335149842
1775099953
2425728290
1756068723
3234036028
3061414513

You can see it varies, while the only thing in that area that was moving was the video window.

Here is a screenshot of my entire setup:

http://gyazo.com/79637b921737f8bafd4c31a0780650ab

I think the reason you did not get a response yet is because no one knows this is a "known issue" because it is not a known issue. Is it really this hard to make a reproducer like I did? :D

Are you playing with transparency and borderless WPF windows? That could be a factor.

Edited by Manadar

Share this post


Link to post
Share on other sites

#5 ·  Posted (edited)

it is not the fact it aint easy to make a reproducer i worked with this guy and made one already the problem is the gui seems invisable to the checksum call

all that seems to happen is it returns the checksum from the screen under the gui window

if it helps i can send you to the gui in question so you can see for yourself

Edited by belgarath

Share this post


Link to post
Share on other sites

If it's easy to make a reproducer, then make one. I really need to see the problem to be able to understand and solve it easily. I'm not going to try five thousand combinations of parameters and circumstances until I finally figure out what the problem is.

You tell me the problem, I tell you the answer.

Share this post


Link to post
Share on other sites

i dont think this guy is going to help us he said he needed to see the problem so i tried to give him the link to the downloader for the client he just thought it was a virus and refused to look.

Share this post


Link to post
Share on other sites

I've repeatedly asked for a reproducer in the form of a VS2010 project with the source code and everything. It doesn't mean I want your entire software product and just start poking around in it. Also, I'm not going to run random executables sent to me by some stranger. Because: What's in it for me? Best case scenario I get a "Thank you" (and 99.99% of the time this doesn't even happen), worst case you're poking in my computer fucking my stuff up. No thanks.

Either way, I don't know how to be more clear. You've said it was "very easy" to make a reproducer. Make one. Start VS2010; Make a new WPF project. Play with the various properties on the window with the sample AutoIt code I wrote for you until you have the same results as you describe in the problem.

My time is more valuable than wasting it on people like you don't let themselves be helped.

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