2011 Version 15 Release Schedule Update

We have listened to your feedback regarding our version 15 (2011) release and have decided to implement more features like many of you have requested.  Because of this, the final release will be delayed however we will continue to introducing betas on a regular basis.  These will be available for public download in our evaluation area.

We apologize for the delays but are hopeful that our v15 release will be one of the best releases we have produced in quite some time.

As now we are looking to have a final release ready by mid January 2011.

We will post a complete list of new features soon.

If you have positive feedback or suggestions please feel free to post them here.

Happy Holidays!

Hello,

Here are also some wishes.

------ Report --------
add:
bool CXTPReportItem::GetIconRect(XTP_REPORTRECORDITEM_ARGS* pDrawArgs, CRect& rcItem);
to receive the IconRect. Because of own handling click on icon.

update:
CXTPReportTip support Markup Items & Markup tips.

add: virtual function to draw background
CXTPReportRecordItem::DrawBackground(CDC *pDC, XTP_REPORTRECORDITEM_DRAWARGS* pDrawArgs, CRect& rcItem)
{
    if (pMetrics->clrBackground != XTP_REPORT_COLOR_DEFAULT)
        pDC->FillSolidRect(rcItem, pMetrics->clrBackground);
}
(http://forum.codejock.com/forum_posts.asp?TID=17390&title=wish-for-cxtpreportrecorditemdraw)

add: Columns Filter Editor
http://forum.codejock.com/forum_posts.asp?TID=16436&title=column-filter-editor

add: CXTPReportInplaceList::Create not virtual
http://forum.codejock.com/forum_posts.asp?TID=13110&title=cxtpreportinplacelistcreate-not-virtual

---------- Markup ------------------
update: Speedup markup parsing:
we have make a makrup listbox. but insert of  3000 need to much time (3 sec).
every entry must be parse, because the listbox need the entry height for the scrollbar.

update: Markup wish fro x:Static System Color changing
http://forum.codejock.com/forum_posts.asp?TID=17196

add: Wish to have a Global.Resource
http://forum.codejock.com/forum_posts.asp?TID=17122

------- Toolkit pro ----------------
Create a HICON from XTPImageManager, if ImageIcon is a alpha bitmap.
http://forum.codejock.com/forum_posts.asp?TID=16605

  Jimmy

- Datagrid control
- Group and Filter on a RC with virtualmode
- Fasten RC with large recordset (500.000 records or more)

Please, do not forget about the skins. XTP is the only library that offers "Office 2007"-GUI for dialogs and other windows. Update it to support all 2007/2010 modes and you'll be way on top!

Please add:

SyntaxEdit

1. Drag and Drop support. Issue #24980
2. Word Wrap support. This has been requested by a lot of people for many years in the forum. Issue #24884
3. Splitter support (your MFC demo shows it, but ActiveX version doesn't and all other SyntaxEdit controls I've used/played with support this). Issue #24883

Docking Pane

1. Make my life easier by exposing properties to know docked / undocked pane's location (left and bottom) without having to use API GetWindowsRect and GetClientRect. Why have to use an api call and extra coding when you can make my life (and others) easier (isn't that the point of third party controls). Doesn't the pane already know where it's docked and can't you easily expose this information. Issue #25083

Recent File List

1. I am moving from another MRU component that had Key, Caption, Icon, and Value properties that I could set. In my case, I need to display to the user a friendly path, but keep the full path plus some server related info (i.e. xyz;myserver:3312;blah\blah\blah.bla) as we're dealing with items not just directly on the file system or UNC. Issue #25084

I find that RecentFileList is EXTREMELY limited. Can you please add support for:

• Caption (what is displayed to user)
• Icon (ability to set/change the icon shown)
• Key (a unique key that can be searched on)
• Value (not shown to user but allows to store info like my example above so I can retrieve the item from the location: xyz;myserver:3312;blah\blah\blah.bla)

2. There appears to be a limit of only showing items numbered through 9?? Even if you set the maxsize property beyond 9. WHY? By the way, this has been reported multiple times in the forums for a long while without being addressed. Issue #25084

adrien wrote: Could I put in a vote for 13.4.3 There are a couple bug-fixes we need, particularly  http://forum.codejock.com/forum_posts.asp?TID=17435 We can't use the new stuff in release code yet for a while, so for us, to delay bug-fixes for implementation of new stuff we can't use is problematic.

1. Resizeable Image-DialogBoxes to all your Suite-Controls. So the developer see more Icons for selecting...


----------------------

2. In Combo- and ListBoxes a new method, called "FindItemByItemData"

FindItemByItemData(IndexStart as Long, Data as Variant)

...it's a little bit like your "FindItem(IndexStart as Long, String as String, Exact as Boolean)", but with searching for "ItemData" instead of "ItemText".

----------------------

3. New event in your TabControl, called SelectedChange (don't muddle with your SelectedChanged!)

Please spend a new Event to your "TabControl" >>>  SelectedChange(ByVal Item As XtremeSuiteControls.ITabControlItem, Cancel As Boolean)

OK, You've already a "BeforeItemClick" Event. But this Event doesn't fires, if another Item will selected by code.

And because your "SelectedChanged" Event fires too late, it's very important to have a "Cancel as Boolean"!

BTW: Same post from me you'll find here: http://forum.codejock.com/forum_posts.asp?TID=17622&title=xtreme-suite-v15-wishlist

Thank you,
Jebo

I'm desperate for a couple of MarkupLabel issues to be fixed, but I haven't heard anything from my support ticket or in the Beta Testing board:

http://forum.codejock.com/forum_posts.asp?TID=17623&title=v15-markuplabel-issues-requests
http://forum.codejock.com/forum_posts.asp?TID=17645&title=bug-markuplabel-control-rowdefinition-height

Any chance of fixes for v15 for these issues?

FIXED FOR 15.

Hi,

There are a few issues which need to be fixed

http://forum.codejock.com/forum_posts.asp?TID=16309&title=bug-v1330-issues-57-solved-14

Aaron wrote: Hi, There are a few issues which need to be fixed http://forum.codejock.com/forum_posts.asp?TID=16309&title=bug-v1330-issues-57-solved-14   Thanks

Many of those will be fixed in the final release.

jpbro wrote: A small request that has been hanging around for years, but shouldn't be too difficult: Add an option for the PopupControl to ignore mouse: http://forum.codejock.com/forum_posts.asp?TID=10144&title=showing-a-png-with-transparency This will complete the feature set for the PopupControl to be used as a splash screen control. Thanks in advance if possible.

Thanks for the fixes guys - can you take a look at this one:

http://forum.codejock.com/forum_posts.asp?TID=17454&PID=61775#61775

Thanks a lot.

NOT A BUG - PEBCAK ;)

If possible, could we add this option to the Calendar control (ActiveX)?

http://forum.codejock.com/forum_posts.asp?TID=17208&title=year-view

Thanks

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!

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.

Sorry Oleg, I missed that. Thanks a lot.

... and a feature list please !

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.

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.

@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 ???

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.

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?

Should real be soon now. 

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!

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.

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

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.

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

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

Great

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

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.

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

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

Hi,

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

Nothing yet for me :(

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.

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

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

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

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

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).

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.

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

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!

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
};

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

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

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?

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?