pcbrainbuster

Sup guys,

When you do retrieve a window's information using GetWindowInfo, how do you check to see if a window has the style WS_OVERLAPPED?

Thanks.

grumpy

Your first step to find an answer is to think for yourself rather than trying to get other people to do the thinking for you. Your second step is RTFM.

Ancient Dragon

You have to pass a pointer to a WINDOWINFO object to GetWidowInfo(). Then just and the dwStyle member with WS_OVERLAPPED to see if it is present as one of the styles.

null_ptr0

Wow, Ancient Dragon for Win32 Wiz.

__________________
iload_0 iconst_1 ishl or
iload_0 iconst_2 idiv or
iload_0 iconst_2 iconst_1 imul idiv
[1] & [2] use the smallest stack size

pcbrainbuster

Thanks for your posts! Could someone please explain how the operator & works? Also could Grumpy please tell me what the abbreviation stands for?

Thanks.

Sane

PcBrain, I hate to say it like this, but a lot of these questions you could be finding answers to more quickly by doing your own research. The & operator is called the bitwise 'and' operator, and it evaluates the 'and' of each bit.


This can be used to quickly determine whether or not a bit is set.

For instance, if x can contain any integer value, and we want to see if the third bit in x is set:


So in the context of window styles... I believe each style is represented by a different bit, and you can use a constants to isolate the bit for the style that the constant represents.

pcbrainbuster

Ahh, I see.

So something like the following should return true right? -


Thanks.

null_ptr0

yuck.
is much better, don't do '== true' or '== false', use the more simple alternatives.

__________________
iload_0 iconst_1 ishl or
iload_0 iconst_2 idiv or
iload_0 iconst_2 iconst_1 imul idiv
[1] & [2] use the smallest stack size

Ancient Dragon

I agree -- the & operator doesn't return true or false, but either 0 if WS_OVERLAPPED is not in the flags or some non-zero value if it does.

Sane

My mistake, I probably threw off the op when I said:

y is 1 (True)

(It was supposed to be y is 4 (True) as well...)

In my example, the only reason I said 'True' is because it gives some meaning to the arbitrary value of 4. In a coding scenario, I agree that it's more readable to neglect the '== true'. Sorry about the confusion.