- This topic has 12 replies, 6 voices, and was last updated 9 years ago by
.
-
Posts
-
new build..498 is out
i think everybody how work in paltalk dont nothing to do .. and everday send a new build out loool@locohacker wrote:
Thanks
Man this ATL: updates are killing the programs ehheheI see they rather play with s*** than fix bugs.
@locohacker wrote:
Thanks
Man this ATL: updates are killing the programs ehheheThat is why you need to learn how to enum the windows instead of direct mapping.
When you use Pats (or equivalent) to get the code, it will always be version spacific because you are mpping parent/child windows all the way from top level down to the window you want. If you enum the windows, then often you can go many versions without having to update code.
The ATL changing with every new build is not because the Pal coders are trying to break your integrations, but rather it is because the ATL object is randomly assigned its number during the compile process. This means that it is out of the hands of the developer and handled by the complier application.
@Loco bro True…
Thanks for the Note CHIKE and AUTO PILOT!
I agree with Chike….. And AutoPilot am pretty sure your right, there is a lot for me to learn from that too!
Thanks!
Auto you mean like using the Id handles like Chike show in
cause that’s what I’m thinking bout doing right now 🙄
@locohacker wrote:
Auto you mean like using the Id handles like Chike show in
cause that’s what I’m thinking bout doing right now 🙄
Old: SysListView32
New: SysHeader32@winter wrote:
@locohacker wrote:
Auto you mean like using the Id handles like Chike show in
cause that’s what I’m thinking bout doing right now 🙄
Old: SysListView32
New: SysHeader32Wrong, SysHeader32 is a child window of bothboth, SysListView and the ATL.
@ChiNa-Man wrote:
Awesome Chike, I was a bit confused over winters reply also, since i can see both!
You can search for the SysHeader32 and take it’s parent, this will work on new and older versions, but why when there is an easier way.
@locohacker wrote:
Auto you mean like using the Id handles like Chike show in
cause that’s what I’m thinking bout doing right now 🙄
Right, weather you enum to find the ID as described in Chikes post or you use class and index as I have shown in the past. Although if I understand Chike correctly, even though the index may occationally change, the ID does not, so that may be the better thing to use.
Also, you could have a file on your site that your app checks against to get version spacific enum values so that when a new version comes out, you just updat your master file and all apps that read from it get updated.
The ID may change, though it hadn’t for a long time.
The function check visability as well as there are duplicates of both the user and room text controlls. It’s weird because it looks like both were duplicated each is visible in one of the groups.Go with the ID and worry about changes when and if they are made.
You can keep the old code if you wish just add the function and change few calls, depending how clean or messed your code is..@Chike wrote:
@ChiNa-Man wrote:
Awesome Chike, I was a bit confused over winters reply also, since i can see both!
You can search for the SysHeader32 and take it’s parent, this will work on new and older versions, but why when there is an easier way.
wuw,,, Thank you Chike, Saved me for some work extra work….
Related
- You must be logged in to reply to this topic.