TD4.1 cCalendarDropDown bug
TD4.1 cCalendarDropDown bug
Hi everyone,
there seems to be a bug in cCalendarDropDown when using a dual screen installation. When I try to dropdown the calender on the second screen, the calender itsself shows up on the first screen.
Is there a workarround for this bug?
TIA
Wilhelm
there seems to be a bug in cCalendarDropDown when using a dual screen installation. When I try to dropdown the calender on the second screen, the calender itsself shows up on the first screen.
Is there a workarround for this bug?
TIA
Wilhelm
Re: TD4.1 cCalendarDropDown bug
BTW, this also happens with TD4.2
Re: TD4.1 cCalendarDropDown bug
This really is frustrating. Is there really nobody who knows, how to fix this?
I think there must be a way to find the window handle of the calender control and move it to the actual position.
TIA
Wilhelm
I think there must be a way to find the window handle of the calender control and move it to the actual position.
TIA
Wilhelm
Re: TD4.1 cCalendarDropDown bug
I would too. How about catching hWndItem on SAM_Create for the control and keeping it?I think there must be a way to find the window handle of the calender control
Re: TD4.1 cCalendarDropDown bug
Hi Jeff,
I really don't know what I should make of your post. I am not stupid - well maybe I am, still using TD.
But perhaps you could give some more advice:
1. hWndItem is certainly not the handle of the popup calendar. I suppose it is the hande of the controls data field.
2. What Message would you suggest to react on, when the calendar is about to popup? (SAM_Dropdown at least isn't fired.)
3. When the dropdown takes place, there is an additional window created which pops up in the taskbar. I suppose this is the window I would have to move.
4. Again how would I get it's window handle?
This is a bug in one of your visual toolchest controls and I would really expect a little more enthusiasm on Unify's side for finding at least a workarround.
Sincerly
Wilhelm
I really don't know what I should make of your post. I am not stupid - well maybe I am, still using TD.
But perhaps you could give some more advice:
1. hWndItem is certainly not the handle of the popup calendar. I suppose it is the hande of the controls data field.
2. What Message would you suggest to react on, when the calendar is about to popup? (SAM_Dropdown at least isn't fired.)
3. When the dropdown takes place, there is an additional window created which pops up in the taskbar. I suppose this is the window I would have to move.
4. Again how would I get it's window handle?
This is a bug in one of your visual toolchest controls and I would really expect a little more enthusiasm on Unify's side for finding at least a workarround.
Sincerly
Wilhelm
Re: TD4.1 cCalendarDropDown bug
Well, since my simple answer isn't a solution for you, then the next best thing is to provide a small test case. I haven't used 4.1/4.2 in a loooong time so if my reply was too simplistic, sorry. As an experienced (not stupid!) TD programmer, you should be aware, then, that a test case can often help us all out.
Re: TD4.1 cCalendarDropDown bug
if you insist....
Please move the window to the second screen and "drop down"
Thanks
Wilhelm
Please move the window to the second screen and "drop down"
Thanks
Wilhelm
Re: TD4.1 cCalendarDropDown bug
... seems *.apt isn't accepted. ?!?
You do not have the required permissions to view the files attached to this post.
-
- Founder/Site Admin
- Posts: 3231
- Joined: 24 Feb 2017, 09:12
- Location: Gouda, The Netherlands
Re: TD4.1 cCalendarDropDown bug
Hi Wilhelm,
This issue is present on all TD versions (also TD 6.0) !
I personally do not use cCalendar, but I checked if I could find a quick workaround.
I think I have found one.
I created a sample, download here:
https://samples.tdcommunity.net/index ... rch_mode=f
Look at the messages section of the control class. I have found two messages which can be used to reposition the calendar.
The WM_COMMAND message is the earliest. But the other commented message also works but it seems to make it flicker.
Hope you can use this.
This issue is present on all TD versions (also TD 6.0) !
I personally do not use cCalendar, but I checked if I could find a quick workaround.
I think I have found one.
I created a sample, download here:
https://samples.tdcommunity.net/index ... rch_mode=f
Look at the messages section of the control class. I have found two messages which can be used to reposition the calendar.
The WM_COMMAND message is the earliest. But the other commented message also works but it seems to make it flicker.
Hope you can use this.
Regards,
Dave Rabelink

Articles and information on Team Developer Tips & Tricks Wiki
Download samples, documents and resources from TD Sample Vault
Videos on TDWiki YouTube Channel
Dave Rabelink

Articles and information on Team Developer Tips & Tricks Wiki
Download samples, documents and resources from TD Sample Vault
Videos on TDWiki YouTube Channel
Re: TD4.1 cCalendarDropDown bug
Hi Dave,
works like a charm.
Thank you very much for your help. I can't believe its still in 6.0.
I even own a licence for 6.0 and haven't had the nerve to install it yet.
Thanks again
Wilhelm
works like a charm.
Thank you very much for your help. I can't believe its still in 6.0.
I even own a licence for 6.0 and haven't had the nerve to install it yet.
Thanks again
Wilhelm
Re: TD4.1 cCalendarDropDown bug
...and another one,
SalTrackpopup Menue doesn't work either on the second screen. It seems the Menue always pops up centered on the undelaying window which is nice when you use it on top of a table window. TPM_CursorX and TPM_CursorY are ignored compeletly.
SAM_ContextMenue sends an incorrect X-screen coordinate and if you use that, the menue pops up on the rightmost position of the first screen.
It's unbelievable....
And I have attached another test. I suppose theese bugs are present in 6.0 as well?
Wilhelm
SalTrackpopup Menue doesn't work either on the second screen. It seems the Menue always pops up centered on the undelaying window which is nice when you use it on top of a table window. TPM_CursorX and TPM_CursorY are ignored compeletly.
SAM_ContextMenue sends an incorrect X-screen coordinate and if you use that, the menue pops up on the rightmost position of the first screen.
It's unbelievable....
And I have attached another test. I suppose theese bugs are present in 6.0 as well?
Wilhelm
You do not have the required permissions to view the files attached to this post.
Who is online
Users browsing this forum: No registered users and 0 guests