2011 Version 15 Release Schedule Update

SuperMario wrote: Write to support for the new Office 2010 skins

jpbro wrote: Office2010.cjstyles is now available to those who request it from support.codejock.com

Office2010.cjstyles is now available to those who request it from support.codejock.com

Lodep59 wrote: Ok guys, just made a sample project. I'll send it to support but, look at these video : 15.0.1 : http://screencast.com/t/QsAZfdph 15.0.2 : http://screencast.com/t/SsDr2qpYR Please make a fix !

Heeeeeeeeeee, THAT'S EXACTLY THE SAME PROBLEM!

Please look here:

>>> http://forum.codejock.com/forum_posts.asp?TID=18031&title=cant-work-with-v1502-if-i-use-codesmart

@Lodep59
Please DEACTIVATE your "CodeSMART" - and you will see, the problem is gone!
But it's not really a solution, because I (I think you too) need CodeSMART very much!

...OR please DELETE the Codejock-TabControl from your form and the problem is also gone!

And yes, the problem is since v15.0.2!

No Problems here!

If it's really soon I can wait.

...and the Office2010 SkinFramework style???

Hi CJ

jpbro wrote: What happened to the Office2007 White theme for the CommandBars control?

Download and edit the XML files on this page.

Re: ChartControl Border, I found a solution:
Me.ChartControl1.Content.Border.Visible = False

What happened to the Office2007 White theme for the CommandBars control?

ABuenger wrote: Enclaved Shadow wrote: This is a problem for me as well.  Have you found a solution? Use xtpTabColorResource. xtpTabColorOffice2010  = xtpTabColorResource is missing.

enum XTPTabColorStyle
{
    xtpTabColorDefault          = 0x0001, // Tabs will use the default color for the currently set Appearance.
    xtpTabColorVisualStudio2003 = 0x0002, // Tabs will use the Visual Studio 2003 color style for the currently set Appearance.
    xtpTabColorOffice2003       = 0x0004, // Tabs will use the Office 2003 color style for the currently set Appearance.
    xtpTabColorWinNative        = 0x0008, // Tabs will use the Windows XP color style for the currently set Appearance.
    xtpTabColorVisualStudio2005 = 0x0010, // Tabs will use the Visual Studio 2005 color style for the currently set Appearance.
    xtpTabColorResource         = 0x0020, // Tabs will use the Office 2007 color style for the currently set Appearance.
    xtpTabColorVisualStudio2008 = 0x0040, // Tabs will use the Visual Studio 2008 color style for the currently set Appearance.
    xtpTabColorOffice2007Access = 0x0080, // Tabs will use the Office 2007 Access color style for the currently set Appearance.
    xtpTabColorVisualStudio2010 = 0x0100, // Tabs will use the Visual Studio 2010 color style for the currently set Appearance.

    //{{AFX_CODEJOCK_PRIVATE

    // obsolete, for backward compatibility only.
    xtpTabColorVisualStudio = xtpTabColorVisualStudio2003,
    xtpTabColorWinXP        = xtpTabColorWinNative,
    xtpTabColorWhidbey      = xtpTabColorVisualStudio2005,
    xtpTabColorAccess2007   = xtpTabColorOffice2007Access,
    xtpTabColorOffice2007   = xtpTabColorResource,

    //}}AFX_CODEJOCK_PRIVATE
};

It looks like that is for Office 2007 not Office 2010.  Why was the 0x0200 (xtpTabColorVisualStudio2010) value removed?

ABuenger wrote: xtpTabColorOffice2010 is missing in the migration guide. 13.4.2 enum XTPTabColorStyle {     xtpTabColorDefault          = 0x0001, // Tabs will use the default color for the currently set Appearance.     xtpTabColorVisualStudio2003 = 0x0002, // Tabs will use the Visual Studio 2003 color style for the currently set Appearance.     xtpTabColorOffice2003       = 0x0004, // Tabs will use the Office 2003 color style for the currently set Appearance.     xtpTabColorWinNative        = 0x0008, // Tabs will use the Windows XP color style for the currently set Appearance.     xtpTabColorVisualStudio2005 = 0x0010, // Tabs will use the Visual Studio 2005 color style for the currently set Appearance.     xtpTabColorOffice2007       = 0x0020, // Tabs will use the Office 2007 color style for the currently set Appearance.     xtpTabColorVisualStudio2008 = 0x0040, // Tabs will use the Visual Studio 2008 color style for the currently set Appearance.     xtpTabColorOffice2007Access = 0x0080, // Tabs will use the Office 2007 Access color style for the currently set Appearance.     xtpTabColorVisualStudio2010 = 0x0100, // Tabs will use the Visual Studio 2010 color style for the currently set Appearance.     xtpTabColorOffice2010       = 0x0200, // Tabs will use the Office 2010 color style for the currently set Appearance.     //{{AFX_CODEJOCK_PRIVATE     // obsolete, for backward compatibility only.     xtpTabColorVisualStudio = xtpTabColorVisualStudio2003,     xtpTabColorWinXP        = xtpTabColorWinNative,     xtpTabColorWhidbey      = xtpTabColorVisualStudio2005,     xtpTabColorAccess2007   = xtpTabColorOffice2007Access,     //}}AFX_CODEJOCK_PRIVATE }; 15.0.1 enum XTPTabColorStyle {     xtpTabColorDefault          = 0x0001, // Tabs will use the default color for the currently set Appearance.     xtpTabColorVisualStudio2003 = 0x0002, // Tabs will use the Visual Studio 2003 color style for the currently set Appearance.     xtpTabColorOffice2003       = 0x0004, // Tabs will use the Office 2003 color style for the currently set Appearance.     xtpTabColorWinNative        = 0x0008, // Tabs will use the Windows XP color style for the currently set Appearance.     xtpTabColorVisualStudio2005 = 0x0010, // Tabs will use the Visual Studio 2005 color style for the currently set Appearance.     xtpTabColorResource         = 0x0020, // Tabs will use the Office 2007 color style for the currently set Appearance.     xtpTabColorVisualStudio2008 = 0x0040, // Tabs will use the Visual Studio 2008 color style for the currently set Appearance.     xtpTabColorOffice2007Access = 0x0080, // Tabs will use the Office 2007 Access color style for the currently set Appearance.     xtpTabColorVisualStudio2010 = 0x0100, // Tabs will use the Visual Studio 2010 color style for the currently set Appearance.     //{{AFX_CODEJOCK_PRIVATE     // obsolete, for backward compatibility only.     xtpTabColorVisualStudio = xtpTabColorVisualStudio2003,     xtpTabColorWinXP        = xtpTabColorWinNative,     xtpTabColorWhidbey      = xtpTabColorVisualStudio2005,     xtpTabColorAccess2007   = xtpTabColorOffice2007Access,     xtpTabColorOffice2007   = xtpTabColorResource,     //}}AFX_CODEJOCK_PRIVATE };

This is a problem for me as well.  Have you found a solution?

Alex H. wrote: You have not mentioned the new FlowGraph Feature on http://www.codejock.com/products/releasenotes/release_notes.asp Or have you removed it in the 15.0.1 Release??

Flowgraph is part of the chart package.  And also part of the suite\toolkit

FlowGraph is present in the evaluation / demos: http://codejock.com/downloads/samples/chart.asp If they remove it I'll nuke them!

xtpTabColorOffice2010 is missing in the migration guide.

13.4.2

enum XTPTabColorStyle
{
    xtpTabColorDefault          = 0x0001, // Tabs will use the default color for the currently set Appearance.
    xtpTabColorVisualStudio2003 = 0x0002, // Tabs will use the Visual Studio 2003 color style for the currently set Appearance.
    xtpTabColorOffice2003       = 0x0004, // Tabs will use the Office 2003 color style for the currently set Appearance.
    xtpTabColorWinNative        = 0x0008, // Tabs will use the Windows XP color style for the currently set Appearance.
    xtpTabColorVisualStudio2005 = 0x0010, // Tabs will use the Visual Studio 2005 color style for the currently set Appearance.
    xtpTabColorOffice2007       = 0x0020, // Tabs will use the Office 2007 color style for the currently set Appearance.
    xtpTabColorVisualStudio2008 = 0x0040, // Tabs will use the Visual Studio 2008 color style for the currently set Appearance.
    xtpTabColorOffice2007Access = 0x0080, // Tabs will use the Office 2007 Access color style for the currently set Appearance.
    xtpTabColorVisualStudio2010 = 0x0100, // Tabs will use the Visual Studio 2010 color style for the currently set Appearance.
    xtpTabColorOffice2010       = 0x0200, // Tabs will use the Office 2010 color style for the currently set Appearance.

    //{{AFX_CODEJOCK_PRIVATE

    // obsolete, for backward compatibility only.
    xtpTabColorVisualStudio = xtpTabColorVisualStudio2003,
    xtpTabColorWinXP        = xtpTabColorWinNative,
    xtpTabColorWhidbey      = xtpTabColorVisualStudio2005,
    xtpTabColorAccess2007   = xtpTabColorOffice2007Access,

    //}}AFX_CODEJOCK_PRIVATE
};


15.0.1

enum XTPTabColorStyle
{
    xtpTabColorDefault          = 0x0001, // Tabs will use the default color for the currently set Appearance.
    xtpTabColorVisualStudio2003 = 0x0002, // Tabs will use the Visual Studio 2003 color style for the currently set Appearance.
    xtpTabColorOffice2003       = 0x0004, // Tabs will use the Office 2003 color style for the currently set Appearance.
    xtpTabColorWinNative        = 0x0008, // Tabs will use the Windows XP color style for the currently set Appearance.
    xtpTabColorVisualStudio2005 = 0x0010, // Tabs will use the Visual Studio 2005 color style for the currently set Appearance.
    xtpTabColorResource         = 0x0020, // Tabs will use the Office 2007 color style for the currently set Appearance.
    xtpTabColorVisualStudio2008 = 0x0040, // Tabs will use the Visual Studio 2008 color style for the currently set Appearance.
    xtpTabColorOffice2007Access = 0x0080, // Tabs will use the Office 2007 Access color style for the currently set Appearance.
    xtpTabColorVisualStudio2010 = 0x0100, // Tabs will use the Visual Studio 2010 color style for the currently set Appearance.

    //{{AFX_CODEJOCK_PRIVATE

    // obsolete, for backward compatibility only.
    xtpTabColorVisualStudio = xtpTabColorVisualStudio2003,
    xtpTabColorWinXP        = xtpTabColorWinNative,
    xtpTabColorWhidbey      = xtpTabColorVisualStudio2005,
    xtpTabColorAccess2007   = xtpTabColorOffice2007Access,
    xtpTabColorOffice2007   = xtpTabColorResource,

    //}}AFX_CODEJOCK_PRIVATE
};

On a positive note, I think the new Office 2010 themes look marvelous, as does the backstage view.

I was able to upgrade two large MFC projects to v15 in about 15 minutes each using the provided grep utility (there were a couple minor bumps in the road, but it did most of the work just fine). In the long term, I think the increase in naming consistency will be quite beneficial.

Sure, it would have been nice to see a few more major new features in the mix, but what's there today certainly represents the high quality I've come to expect from CodeJock. IMO, they continue to make their competitors look pathetic.

Congrats!

Do you have already a schedule for a new release with fixes for the ‘asserts’ found so far? Can we expect it soon or is it again a question of weeks and months? Right now 15.0 is NOT useable for us without fixes. I cannot release an app with known ‘ASSERTS’ in it - still hard enough to release with unknown ‘ASSERTS’ J

Yes, where can we found the Office2010.cjstyles file? I googled only one (deviantART) but this is for Win7 and can not be opened by CJ skinframework.

one thing we could do to ease migration would be instead of #defines and using the preprocessor to replace things, use typedefs to get the compiler to achieve the same thing (for class names anyway).

if you need your counter reset please contact support...we need your order number to look up your account to reset it.

Still having problems with download of Suite v15 !
Download link is unclickable

Server is now fixed for the Suite Downloads.  The download should work providing your download counter is not at 0.

Simon HB9DRV wrote: Please confirm whether the Chart is part of Toolkit Pro 2009 on http://codejock.com/purchase/ as I let my subscription lapse some years ago and want to get a Toolkit & Chart licence.

Yes, Chart is part of Toolkit v15.0.1

Please confirm whether the Chart is part of Toolkit Pro 2009 on http://codejock.com/purchase/ as I let my subscription lapse some years ago and want to get a Toolkit & Chart licence.

Nothing yet for me :(

immoassist wrote: I have sent also a ticket, but not download link :( Could you send me the link as PM? So I could test it, and upgrade the app for today :)

All tickets have been responding to.  Please send a request to support@codejock.com

Hi,

I notified sales, and they will be resetting your accounts soon.  Sorry for the inconvenience, you will have the downloads soon.

I've got a "page not found" when I try to download from Online Store Account.

adrien wrote: yeah, I don't know if renaming was such a great idea. it also means if we find 15.0.1 unreleasable for any reason, we already had to migrate all our source to find that out, and would need to migrate it back to roll back the toolkit. Since the choice of toolkit is a system-wide setting in MSDev, it's not even like you can easily set up different projects to use different versions (not in the old dinosaur MSVC6)

As the document says, be sure to make backups of all your projects before you make modifications. VC6 you can simply change the path to look at the new dlls.  If you don't like the new version it only takes a few seconds to change the paths back.

yeah, I don't know if renaming was such a great idea.

adrien wrote: Many classes have been renamed, styles, defines and structs renamed (to make naming consistent - in general *XT* -> *XTP* ).

Great

you might want to check the release notes before you do that.

Just an update.  Due to issues with our build machine we haven't been able to get a build completed.  Because of this will will have to push the release to tomorrow.  Sorry for the extra delay.

I agree with the previous two posts - take your time and do it right.  Release it next week or next month if you have to.  While I can only speculate, I would venture the majority of Codejock customers are professionals - not hobbyists.  My products are only as good as the components that go in them.  If Codejock ships a product that looks like they are just trying to get it out the door, then my products as well as every other professional around here will look the same. 

In the big scheme of things, components are a dime a dozen.  However, components developed to extremely high standards are components worth paying for.  As a professional, I use components worth paying for which is why I have a Codejock subscription. 

Codejock, please keep this in mind as you weigh your options as to when you are going to release Version 15.  The professionals who use your products are counting on excellence.    Thank you!

Sincerely,

John P. Coffey, President
JobTabs, LLC
http://www.jobtabs.com

SuperMario wrote: Just an update.  15.0.1 will be released by the end of the day tomorrow, not today.  Thank you for your patience.

Jebo wrote: Good news! I have spoken with support in the meantime. Version 15 will be posted today, 07-FEB-11.

Excellent, about time I blew my users' socks off with great UI features!

Should real be soon now. 

Any plans for a new ‚real‘ beta (not an evaluation) or any kind of feature-list before your release or delay v15 in 2 or 3 weeks?

Thanks Fabian, I'll check it out.  I did get another workaround for another user that seemes to work as well, but my point to CJ was here is one of your base controls that has a problem, and I can't get them to fix it.  The same code using the MS progress bar and even a freebie one I found on the web does not slow down like the CJ progress bar.  Thanks again.

@CJ-Team
"As now we are looking to have a final release ready by mid January 2011."
Is this true? In two days the final v15 will be released???

   or ???

ABuenger wrote: The last Beta was released "11/29/10". We are all developers, so we all know how much could have been done since then. Sometimes it seems to me that some users here expect them to do magic. Releasing too much info is also two-fold for them. They want to give their customers as much info as possible, but then there is also a competitor who reads each message of them. Why do you think has BCGSoft now also a Chart control? They've read each request etc. here. It's a poor situation for them in which they only can lose.

Guys, calm down. There is only so much that can be done within 1 month. Obviously there can't be weekly Betas. We'll either see an other Beta or the final release, I'm sure we will get an update within the next days.

The chart control was quite a large addition to the toolkit and therefore they couldn't work on the existing controls as much as in the past.

Everyone here is posting his requests, but no one seems to notice that they sum up to several month of work. A lot of the issues posted here have already been addressed, as you can see from their replies.

... and a feature list please !

Sorry Oleg, I missed that. Thanks a lot.

Another small but useful feature that I would really welcome:

The ability to draw an icon/bitmap in the ImageManager control to an hDc with alpha and using one of the xtpImageNormal, xtpImageChecked, xtpImageHot, xtpImagePressed, xtpImageDisabled flags. Is this possible for V15? ALREADY EXISTS, MY MISTAKE.

Any chance of getting an IPrintView interface from the MarkupLabel control for use with the PrintPreview control?

Even nicer would be a PrintToDc option with the ability to define the RECT to print to, similar to what we have with the ChartControl.

Thanks a lot. DONE FOR V15. Thanks a lot!