1 reply to this topic

[burek]

Hi,

It might be wise to use only 1 MDI Child Window for private chats, instead of opening one for each private conversation. Same goes for public hubs, search, file lists, etc.
Explanation: Instead of using each mdi child window for each item (hub, pm, search, etc.) it would be more efficient to keep the info, related to that item, in the memory structure and when the user switches to another item, just to update the content of the mdi child window with the info from the memory structure for that item. This way Apex would allocate a lot less GDI objects, handles and total memory.
I'm telling this from my own personal experience, while programming MDI applications, so you might actually considering discussion about this topic with root developers (DC++) too, since it would be more effective for all derivative client apps.

Cheers.

[Big Muscle]

Your opinion seems interesting but what about overall performance? I don't think so that it eats so much handles and memory now (not counting extreme cases like 200 hubs + 150 PM frames). Wouldn't there be big performance drop when it needs to clear and refill whole chat history and userlist content everytime you click on another tab? (however, StrongDC++ based clients have already optimized userlist memory usage, because other DC++ clients just create another memory structure for each userlist's item and therefore they eat twice more memory than really needed).