- Topics - 9
- Replies - 583
- Total Posts - 592
unrealted bit #1: Do I misunderstand you code or are you not checking the rc codes here? I know it doesn’t really relate to you question, but is it just me or are you calling Getfirst regardless of whether or not OpenDs returns rc=success and then calling GetFirst regardless of whether or not GetFirst returns rc=success? I wonder if you would see TWRC_FAILURE/TWCC_MAXCONNECTIONS if you checked the Rc and Cc during the OpenDs call… Or do you just stop getting messages everywhere?
unrelated bit#2: Are you maintaining and tracking the twState during your calls? It seems to me (from this small bit of code) that you aren’t.
>>Is there a way for the wrapper to open the dsm while maintaining its conversation with the app?
this has been asked before and someone (who I don’t know and have no reason to believe or for that matter not believe) said no. but I always wondered. It seems to me (and no, I don’t know – I just have a strong suspicion) that if your wrapper, which is itself a source, – and it looks from &in_hWnd that you are if I understand what that points to, maintained it’s own messageloop, by deriving from nativeWindow, that it should be able to talk to the dsm independant of connection to the parent app. Then your wrapper would (should be able to?) be able to close and reopen the dsm if needed to get stuff done while maintaining the conversation with the app. Or maybe I need more sleep and less coffee, hard for me to tell sometimes.
Which of the 5 DSM_Entry calls from you code do you think is the problem? Would it help if you were stepping thru the code from all parties invloved?
You mentioned testing with a couple of different some that worked other that didn’t depending on the xfer mode , is this problem reproducable with twacker?