Codejock Developer Community : CXTPCalendarDayView printing

CXTPCalendarDayView printing : Here fixed code covered 24:00...

Wed, 19 Aug 2009 13:56:16 +0000

Author: mdoubson
Subject: 14999
Posted: 19 August 2009 at 1:56pm

Here fixed code covered 24:00 as feasible strict ( < ) ScaleMaxTime

https://forum.codejock.com/uploads/DemoVersion/CalendarDemoStatic.rar

https://forum.codejock.com/uploads/DemoVersion/CalendarControlMFCUpdated.rar

As we are going to release 13.2 sometimes in September - please try to test and help to improve our Calendar

(all links already had 13.2 "beta" code - please try and give some feedback)

CXTPCalendarDayView printing : There is no problem to print...

Wed, 19 Aug 2009 10:53:46 +0000

Author: mdoubson
Subject: 14999
Posted: 19 August 2009 at 10:53am

There is no problem to print 1 hour range (like this [22:30 - 23:30])- except [23-24] one:

CXTPCalendarDayView printing : I don't consider crazy cases...

Wed, 19 Aug 2009 09:25:05 +0000

Author: mdoubson
Subject: 14999
Posted: 19 August 2009 at 9:25am

I don't consider crazy cases somebody want to print 1 hour only -

CXTPCalendarDayView printing :

Wed, 19 Aug 2009 09:16:19 +0000

Author: zitz
Subject: 14999
Posted: 19 August 2009 at 9:16am

CXTPCalendarDayView printing : mdoubson wrote:I tried it...

Wed, 19 Aug 2009 09:10:26 +0000

Author: zitz
Subject: 14999
Posted: 19 August 2009 at 9:10am

mdoubson wrote:

I tried it TODAY and after it not help and still give invalid data - COMMENTED IT.

Where it gives the wrong result? How can I repeat it?

mdoubson wrote:

Old Printing Code was very functional-poor - supported only one page with very little detailes as use only one mode - 30min interval.

There is nothing in print code related to DayView modificaionts. Everybody who asked to have detailed DayView printout (multi-pages) happy.

I also want a multi-pages, but unfortunately this feature is not working correctly. Please, experiment with different intervals: in one case, prints two pages when you do not need, n another case, print one page when it needs to the two.

CXTPCalendarDayView printing : I feel that "the more is...

Wed, 19 Aug 2009 09:06:37 +0000

Author: mdoubson
Subject: 14999
Posted: 19 August 2009 at 9:06am

I feel that "the more is the better"

CXTPCalendarDayView printing : With my patch all works fine,...

Wed, 19 Aug 2009 09:02:48 +0000

Author: zitz
Subject: 14999
Posted: 19 August 2009 at 9:02am

With my patch all works fine, but one thing
If i choose print range from 22:00 to 23:00, why it printed from 22:00 to 24:00 (23:59:59)? Hm... always adds one hour to the upper range i dont understand. How print from 21:00 to 22:00?

mdoubson wrote:

Btw - I like the fact our Forum site now supported cyrillic - howyou print it - directly in Form?

Yes, directly in Form.

CXTPCalendarDayView printing : What are you talking about - Previously...

Wed, 19 Aug 2009 09:00:27 +0000

Author: mdoubson
Subject: 14999
Posted: 19 August 2009 at 9:00am

What are you talking about - Previously used without a twinge of conscience? I tried it TODAY and after it not help and still give invalid data - COMMENTED IT. Old Printing Code was very functional-poor - supported only one page with very little detailes as use only one mode - 30min interval.

There is nothing in print code related to DayView modificaionts. Everybody who asked to have detailed DayView printout (multi-pages) happy.

CXTPCalendarDayView printing : mdoubson wrote:As you can...

Wed, 19 Aug 2009 08:37:57 +0000

Author: zitz
Subject: 14999
Posted: 19 August 2009 at 8:37am

mdoubson wrote:

As you can see in MFC source update - I tried your code without effect - now it commented. Find better way please

Let's better change TimeScale draw for last cell in this case (but in any cases we will never draw 24 as number - this is not logical - it still < restriction)

Previously used without a twinge of conscience, and now will not? You understand that we will all work to alter the events?
The problem is that if you move an event at this time that he hasnot 19.08. 2009 23:30 - 19.08. 2009 23:59 and 19.08. 2009 23:30 -20.08. 2009 00:00. Because you are so on the calendar was originallybuilt - the lower limit and upper limit. Everything is working! Now youoffer me to redo all of your new concept, right?
Neither have nowhere to draw the number 24! If you're worriedabout that in the options, for example, when printing, will be 23:00and then 24:00, then 23:00 so do 00:00 (which actually would be 24:00,ie the beginning of the next day). My users do not care what is written24:00.
The very scale of 24 we never see, as we see the number 18 willbe selected if the range of 16 to 18. What is the problem then?Everything seems to work well, for everybody, and bang! Now, you guyswill all work on another ...
Why do you print the other band displays? So on this I see onlyone explanation, the printing made by another person who does notunderstand how everything works.
The solution is simple (see code)
And when the press must take into account that m_dtTimeScaleMaxmay well be 1.0, in all the other code that takes into account (Ishowed the pieces of code above), it is not only the new features inthe printing.
Put file XTPCalendarDayView.cpp, re build the library and you will see that everything works perfectly. void CXTPCalendarDayView::SetScaleMaxTime(const COleDateTime dtNewScaleMaxTime)

{
    if (dtNewScaleMaxTime.GetStatus() == COleDateTime::valid)
    {
        m_dtTimeScaleMax = dtNewScaleMaxTime;
        if ( m_dtTimeScaleMax.m_dt != 1.0 ) m_dtTimeScaleMax = CXTPCalendarUtils::ResetDate( m_dtTimeScaleMax );
        CXTPCalendarControl::CUpdateContext updateContext(m_pControl, xtpCalendarUpdateRedraw);
    }
}

Here is XTPCalendarDayView.cpp
uploads/20090819_083349_XTPCalendarDayV.zip
I am confused at your patches, so that the version calendar I use now:
uploads/20090819_083733_Calendar.zip

CXTPCalendarDayView printing : As you can see in MFC source update...

Wed, 19 Aug 2009 07:30:35 +0000

Author: mdoubson
Subject: 14999
Posted: 19 August 2009 at 7:30am

As you can see in MFC source update - I tried your code without effect - now it commented. Find better way please

Let's better change TimeScale draw for last cell in this case (but in any cases we will never draw 24 as number - this is not logical - it still < restriction)