flat assembler
Message board for the users of flat assembler.
![]() |
Author |
|
roticv
192mhz ram?
|
|||
![]() |
|
JohnFound
roticv wrote: 192mhz ram? Of course 192Mbytes. Simply mistake. Fixed. ![]() |
|||
![]() |
|
Foamplast
Why do you compare such different things? GetWindowLong/SetWindowLong operate on data linked to the window and owned by Window's GUI. SetProp/GetProp/RemoveProp operate on user-defined data linked to the window. Generally, user-defined data can be read or written and GetProp/SetProp/RemoveProp functions can operate on these data without any understanding what these data are. Unlikely, GetWindowLong/SetWindowLong should have an understanding of the data's meaning to operate correctly. Your results show that this point of view can be true.
|
|||
![]() |
|
JohnFound
Foamplast wrote: Why do you compare such different things? Both, Set/GetProp and Set/GetWindowLong can be used as placeholders for user data for subclassed windows, custom window classes and other user data asociated with some control ( GWL_USERDATA and also the extra bytes (WNDCLASS.cbWndExtra) defined for given user registered class) So, usual method used in assembly written applications (you can check several examples here and there) is using Get/SetWindowLong, but my tests make me think that better method is namely SetProp/GetProp method. Besides that Get/SetProp is more flexible method, it seems that is is faster in some conditions and acceptable slower in worst case. Of course my tests concerns only Win98. Maybe in Win2000/XP things looks different. (but I don't think so...) Regards. |
|||
![]() |
|
< Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2020, Tomasz Grysztar. Also on GitHub, YouTube, Twitter.
Website powered by rwasa.