Toolkit Pro, Suite Pro 17.0.0 Beta 1 Released
Printed From: Codejock Forums
Category: Codejock Products
Forum Name: Toolkit Pro
Forum Description: Topics Related to Codejock Toolkit Pro
URL: http://forum.codejock.com/forum_posts.asp?TID=22645
Printed Date: 21 November 2024 at 3:49pm
Software Version: Web Wiz Forums 12.04 - http://www.webwizforums.com
Topic: Toolkit Pro, Suite Pro 17.0.0 Beta 1 Released
Posted By: kstowell
Subject: Toolkit Pro, Suite Pro 17.0.0 Beta 1 Released
Date Posted: 29 June 2015 at 2:36pm
|
Customers who have an active maintenance subscription for any Toolkit Pro or Suite Pro product will find the beta download under My Account > Product Download. Select your product to see the download link for the current beta. We will announce additional beta releases using the RSS feed on our website and the Codejock Messenger alert that is installed with each product. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Replies:
Posted By: Alex H.
Date Posted: 30 June 2015 at 7:44am
|
Where can we find the Release Notes of the BETA1? |
Posted By: krienp
Date Posted: 30 June 2015 at 9:27am
| If we run across issues, what's the appropriate way to submit feedback / bugs? Is support.codejock.com appropriate or something else during the beta period? |
Posted By: kstowell
Date Posted: 30 June 2015 at 9:45am
Please send all problems / bugs / suggestions to support@codejock.com and put 17.0 Beta 1 in the description. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
krienp wrote:Posted By: kstowell
Date Posted: 30 June 2015 at 9:46am
The release notes are included with the installer, they are quite extensive for this release. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: Marco1
Date Posted: 01 July 2015 at 7:47am
|
Please emphasize fixing ALL problems reported in this forum for the next beta/RC! First look on this beta is not too bad: - Ribbon Theme size and quick access bar of 2007/2010 theme with frame transparency seem to be okay! - Height of the message bar in Ribbon sample of 2007 theme is too small, please fix! - No VS 2015 support yet, please fix urgent! -Themed frame size still too thin. Please fix - but DON'T break the button and quick access bar size again! ------------- Product: XTP 18.3.0 on VS 2017 Platform: VS 2017 / Windows 10 (64bit) |
Posted By: markr
Date Posted: 01 July 2015 at 10:38am
|
I agree, this first beta is looking pretty good. I found just a handful of issues and reported those to support@codejock.com. The big ones for me are: - Themed frame size being too thin (this must be fixed) - Report control horizontal scrollbars are messed up when using SetLastColumnExpand(TRUE) - Docking panes corrupt the client area when using UseSplitterTracker(FALSE) I've also noticed that my docking pane icons disappear when I use the new Office 2013 themes (they appear correctly when using Office 2010 or any other theme type). I assume that's a bug and not intentional theme behavior?
|
Posted By: Sergio
Date Posted: 01 July 2015 at 10:57am
|
Hello, The beta 17 is working fine, no issue found yet. Do you plan building an Office 2013 skin that matches the theme? Thanks ------------- Sergio |
Posted By: kstowell
Date Posted: 01 July 2015 at 12:47pm
Look at the Calendar Demo Visual Studio 2015 theme is fully supported, we just haven't updated all of the samples yet. Let us know if we missed something but with Beta 1 there is only one component (Docking Pane) that is missing Visual Studio 2015 theme support, and we are working on finishing this now for Beta 2.
Can you provide more details? A screen shot or steps to reproduce, along with the theme you are using will be helpful, thanks!
------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: kstowell
Date Posted: 01 July 2015 at 12:59pm
With Beta 1 we didn't have enough time to finish Office 2013 and Visual Studio 2015 themes for Docking Panes yet. We are working on this and should have it completed by the time Beta 2 is released. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: tomay3000
Date Posted: 01 July 2015 at 4:12pm
|
finally a beta ------------- Product: Codejock ToolkitPro MFC v16.2.0 Platform: Microsoft Windows 8 Pro (64-bit) Language: Microsoft Visual C++ v6.0 (MFC) |
Posted By: Marco1
Date Posted: 01 July 2015 at 5:26pm
I'm already using Visual Studio 2015 RC - and it would be really nice if it's supported by the installer. ------------- Product: XTP 18.3.0 on VS 2017 Platform: VS 2017 / Windows 10 (64bit) |
Posted By: kstowell
Date Posted: 01 July 2015 at 11:29pm
Ok, yes we are working on this and it is scheduled for Beta 2. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: Marco1
Date Posted: 02 July 2015 at 8:18am
Sure! First of all, this annoying "cursor sticks on the frame border" is still in the samples, I hoped, that this would be disabled by default. The frame of the 2013 theme is way to thin, guess therefore you invented this sticky thing:  Here in your Ribbon Sample. Office 2007 Theme: The icons and the quick access bar is positioned and aligned correctly now! Good! Please don't touch! But the message bar is vertically not big enough.  ------------- Product: XTP 18.3.0 on VS 2017 Platform: VS 2017 / Windows 10 (64bit) |
Posted By: KeithP
Date Posted: 02 July 2015 at 10:19am
|
Is there anyway to access the beta if you are just evaluating the software? I had some issues the current version of the software and I'm wondering if the beta has fixed any of them. |
Posted By: Alex H.
Date Posted: 03 July 2015 at 4:02am
|
XTP17
BETA: AGAIN incomplete German Resources Ribbon Customization Dialog is again not being translated properly/completely! We have been providing a translation for V13.4, V15.3, V16.4 and now AGAIN for V17
Can you imagine how frustrating it is, to have the same issues over and over
again? http://forum.codejock.com/uploads/365/Resource_de.zip" rel="nofollow - uploads/365/Resource_de.zip |
Posted By: olebed
Date Posted: 03 July 2015 at 6:00am
Hello Alexander, I've added your changes to Resource_de.rc. Thank you, Oleksandr Lebed |
Posted By: kstowell
Date Posted: 03 July 2015 at 11:45am
We have had a lot of requests for this, we will look into creating an evaluation for Beta 2. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: markr
Date Posted: 04 July 2015 at 11:33am
It doesn't appear to me that this problem is related to the beta at all. In fact, you can reproduce the problem with the v16.3 "DockingPane.Pane.exe" sample. When using the Office 2010 themes, you can see icons assigned to the pane tabs, but as soon as you switch to Office 2013 (or Visual Studio 2012) theme, the icons are no longer visible.
|
Posted By: kstowell
Date Posted: 06 July 2015 at 2:17pm
These are issues that are released to the Visual Studio 2012 / 2015 and Office 2013 themes, as I mentioned before they will be addressed with the next Beta. The Visual Studio 2015 themes will be replacing the 2012 themes in their entirety, however the Visual Studio 2012 themes will still be available for backward compatibility.
------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: snarfblatt
Date Posted: 16 July 2015 at 1:34pm
| Any updates on the next beta/RTM release? |
Posted By: kstowell
Date Posted: 16 July 2015 at 2:23pm
We had some good feedback on Beta 1 so we are working hard on addressing those issues. Realistically we are probably another 2 - 3 weeks out before we are ready for Beta 2. This should address the majority of outstanding issues that have been brought to our attention.
------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: Alex H.
Date Posted: 12 August 2015 at 2:50am
|
Beta 1 has no toolbar grippers compared with XTP 16.4 Ist this a bug or new a option? 
|
Posted By: kstowell
Date Posted: 12 August 2015 at 1:05pm
|
This was done intentionally to correct the 16.4 theme to more closely match Office 2013. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: markr
Date Posted: 12 August 2015 at 3:38pm
| Kirk, do you still expect BETA 2 to be released this week? |
Posted By: Alex H.
Date Posted: 13 August 2015 at 2:01am
|
There are now toolbars like that in Office 2013! Can i activate the gripper again somehow? I know, my customers will ask for it!  OneNote 2013 has also grippers in dragable windows:  |
Posted By: kstowell
Date Posted: 13 August 2015 at 1:47pm
You have a point there, how about we add the 3 dots like OneNote 2013 has to indicate gripper area does that work for everyone? ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: kstowell
Date Posted: 13 August 2015 at 2:07pm
We have everything ready to go, but there are 2 big issues we are trying to wrap up first. I think we should have this completed by the weekend and we can start BETA 2 builds early next week. Shouldn't be much longer.
------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: markr
Date Posted: 13 August 2015 at 2:21pm
Curious, I don't recall ever seeing a toolbar with grippers in Office 2013. Where are you seeing this? - Mark R.
|
Posted By: kstowell
Date Posted: 13 August 2015 at 3:14pm
Ok, I checked OneNote 2013 and there are indeed 3 dots for the gripper area on a dockable window. I think we can safely add this into the theme for toolbars an indicator the gripper area. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: markr
Date Posted: 13 August 2015 at 3:20pm
I think this is only true in some circumstances (such as when a window is docked to the desktop). Docking panels, like ones supported by XTP, do not appear to have grippers of any type. See the Templates docking panel below: 
I don't understand - why take a concept specific to dockable windows and apply it to toolbars? - Mark R.
|
Posted By: kstowell
Date Posted: 13 August 2015 at 4:03pm
Because in the past Microsoft toolbars and dockable windows shared the same gripper style. Unfortunately there are no good toolbar examples in Office 2013 to use as an example, so the dockable window would be the closest match, if that makes any sense. That being said we are willing to do whatever you guys want us to do, just let us know. My thoughts are to add a draw gripper option to display the 3 dots depending on user preferences.
------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: Alex H.
Date Posted: 14 August 2015 at 2:10am
|
Yes an option for toolbars would be fine :-) Thank you! |
Posted By: evoX
Date Posted: 14 August 2015 at 5:18pm
|
------------- Product: Xtreme ToolkitPro 19.30 Platform: Windows 10 64bit Language: Visual C++ (VS 2019) |
Posted By: markr
Date Posted: 14 August 2015 at 6:21pm
That's a screenshot of MS OneNote that I was using to point out that they Office 2013 docking panels don't have grippers by default. :-) Regards, Mark R.
|
Posted By: evoX
Date Posted: 15 August 2015 at 5:23pm
Oh I have not looked at the title bar  ------------- Product: Xtreme ToolkitPro 19.30 Platform: Windows 10 64bit Language: Visual C++ (VS 2019) |
Posted By: kstowell
Date Posted: 18 August 2015 at 12:29pm
Ok, I tested the gripper idea out. I don't mind adding it as an option but honestly, I think it looks distracting and would prefer leaving it the way it is now without the 3 dots. What is everyone's thought here? With Gripper:  Without Gripper:  ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: markr
Date Posted: 18 August 2015 at 2:07pm
|
Hi Kirk, > I think it looks distracting and would prefer leaving it the way it is now without the 3 dots. I agree; the dots just don't look right. It'd be a shame to have something like this is holding back the release of BETA 2. - Mark R.
|
Posted By: Alex H.
Date Posted: 19 August 2015 at 2:29am
|
Hi! In my case i need it for the classic floatable toolbars, because without them nobody will know they are floatable. So an option would be nice for those who need them.  We must change from 16.4 (still using Office 2013 style) to 17 in the next service pack. So our customers will storm our hotline without the grippers :-( Could you please also reduce the gap between the first icon and the gripper? |
Posted By: BeeJay
Date Posted: 19 August 2015 at 3:00am
|
Hi honestly I do not really understand, why a theme-taste-question should lead to a change to proven design and usability guide rules, just because of somebody's taste. A gripper indicates a possible area for starting drag & drop action. Office 2013 Ribbons are not floatable, hence we should not look at them at all. We should look at the normal "classic" toolbars that are floatable: https://msdn.microsoft.com/en-us/library/0862h9a4.aspx Being that, there should be a gripper when they are floatable. Otherwise the user will never ever explorer the feature of floatable toolbars at all. (Even not to speak of the strange gap when left out.) All developers who do not like having a gripper should use a non-floatable-toolbar. We are not discussing either whether we "like" the elevator-box in scrollbars or not. It is just there, because it has a certain functionality. The same applies for grippers. Regards BeeJay PS: at least give the developers an option if your personal taste is about overruling control design guidelines  |
Posted By: kstowell
Date Posted: 19 August 2015 at 2:28pm
I think BeeJay has a point here and if you don't want to display grippers, you can turn them off already by making your toolbar non-floatable, or simply disabling the gripper. We decided that since we don't have a good example from Microsoft for an Office 2013 dockable toolbar, and Visual Studio 2015 is so very similar to the Office 2013 design, we could use that as the guidline for Office 2013 toolbar grippers. Here is the end result, I think it looks pretty good actually. You can always disable the gripper display if you don't want your dockable toolbars to show the gripper. We are hoping this is a reasonable solution for everyone.  Regarding BETA 2 it is in the final stages of building now (this takes several hours) and we are hoping to release it either tonight or sometime tomorrow.
------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: BeeJay
Date Posted: 20 August 2015 at 5:56am
|
Hi, this looks great! Thank you. BeeJay |
Posted By: kstowell
Date Posted: 20 August 2015 at 7:44pm
|
Beta 2 just released folks! We also published an evaluation version that you can download if you don't have an active subscription. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: Norika
Date Posted: 20 August 2015 at 10:04pm
|
Hi Kirk, Thank you very much! I tried to install immediately, I found 17.0 Beta 2 Suite Controls does not show each Markup items correctly. Please confirm it. 
|
Posted By: BeeJay
Date Posted: 21 August 2015 at 3:13am
|
Hi there, BETA2 breaks compilation of existing code that uses mapi.h  .\ToolkitProv17.0.0.081715\Source\Calendar\Mapi\MAPIDefS.h defines a namespace "Codejock::MAPI" and therein does a typedef for LHANDLE and sets the #define to avoid duplicate typedefs of it. Due to the namespace, the type now is Codejock::MAPI::LHANDLE This breaks any compilation of .cpps that include and use mapi.h (standard Microsoft windows sdk include), as their typedef (without namespace) does not take effect (due to your #define __LHANDLE) and all MAPI functions/structs with LHANDLE cannot compile. You must not declare custom namespaces within standard Microsoft include files! Best regards BeeJay |
Posted By: BeeJay
Date Posted: 21 August 2015 at 3:32am
|
workaround for us: commenting out all *MAPI* include references from includes.h I don't know which side effects this might have in the future, especially when you want to use this MAPI feature - which we don't. Opting out this feature by setting a _XTP_EXCLUDE_CALENDAR_MAPI would be a great opportunity. |
Posted By: davbrat
Date Posted: 21 August 2015 at 5:32pm
|
Aye, Broken XAML tooltips in the ActiveX ReportControl. ------------- Product: Xtreme SuitePro (ActiveX) version 18.4.0 Platform: Windows XP SP2+ & Windows 7 (32bit & 64Bit) Windows 8/8.1/10 Language: Clarion 5.0/5.5/6.3/7.3/8/9/9.1/10 |
Posted By: astoyan
Date Posted: 22 August 2015 at 4:14pm
Thank you for reporting this. We've separated MAPI definitions furthermore which should eliminate all possible conflicts in future, and those who will want to use those definitions will have to XTP_USE_MAPI_DEFINES, by default it'll be undefined. Unfortunatelly we had to introduce namespaces initially and now to make even greater separation for macros because the dependency on internal MAPI definitions has already been in ToolkitPro for may years and it's the last changes in standard MAPI headers that started to cause conflicts with an ToolkitSpecific internal one during compilation. So, even introducing _XTP_EXCLUDE_CALENDAR_MAPI would only disable the problem for those who don't use MAPI but would not help for those who use it.
|
Posted By: astoyan
Date Posted: 23 August 2015 at 3:48pm
Thanks for pointing into this. The problem has been fixed. Though for ToolkitPro it should not happen while in Debug mode, but for ActiveX you'll have to wait for the next update.
|
Posted By: JoseAngel
Date Posted: 25 August 2015 at 12:59pm
|
Unable to compile a project using Beta 2 with Visual Studio 2015. Missing the next lines in XTToolkitPro.h? #if _MSC_VER == 1900
#define _XTPLIB_VISUALSTUDIO_VERSION "vc140" #endif |
Posted By: kstowell
Date Posted: 25 August 2015 at 1:58pm
Yes that is correct, we mentioned this in another post as well. It will be addressed with the next update. http://forum.codejock.com/forum_posts.asp?TID=22599&PID=73767&title=version-170-sneak-peek#73767" rel="nofollow - http://forum.codejock.com/forum_posts.asp?TID=22599&PID=73767&title=version-170-sneak-peek#73767 ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: terrym
Date Posted: 25 August 2015 at 6:27pm
|
ToolkitPro1700vc140DSD.lib not found in latest beta 2? Environment: Visual Studio 2015 and Windows 10 ------------- Thank you, Terry Mancey email terry@tmancey.ltd.uk | linkedin www.tmancey.ltd.uk | twitter @tmancey |
Posted By: BeeJay
Date Posted: 26 August 2015 at 2:53am
|
@TerryM regarding the lib: The Solution Settings changed compared to previous XTP versions (including Beta1): Librarian output path property changed from ../../lib/vc120/ToolkitPro1700vc120SUD.lib to $(OutDir)$(TargetName)$(TargetExt) which causes the built lib not to be generated in .\lib\vc120 but in .\Workspace\ToolkitPro\Static_Unicode_Debug\vc120 (e.g.) So you'll find the lib there. (I've address this issue already.) |
Posted By: terrym
Date Posted: 26 August 2015 at 12:07pm
------------- Thank you, Terry Mancey email terry@tmancey.ltd.uk | linkedin www.tmancey.ltd.uk | twitter @tmancey |
Posted By: markr
Date Posted: 27 August 2015 at 10:19am
|
Kirk, will you be re-releasing BETA 2 with some of these build-related issues fixed? - Mark R.
|
Posted By: Marco1
Date Posted: 27 August 2015 at 12:26pm
Come on, what kind of process is that? A beta comes with no cost at all. Why not release a BETA 3 or RC1? ------------- Product: XTP 18.3.0 on VS 2017 Platform: VS 2017 / Windows 10 (64bit) |
Posted By: markr
Date Posted: 27 August 2015 at 12:31pm
Because it took a long time to get from BETA 1 to BETA 2, and I was hoping for a quick refresh/update. Our applications make heavy use of markup, which seems to be very broken in BETA 2 - do we really can't test it at all. Just hoping to keep things moving forward. - Mark R.
|
Posted By: kstowell
Date Posted: 27 August 2015 at 1:04pm
Yes most likely a BETA 2.1 that addresses the immediate problems with BETA 2 looks like sometime next week.
------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: BeeJay
Date Posted: 28 August 2015 at 2:39am
@Kirk: that would be great!  @Marko1: cost or no cost - for most of us the UI is an essential part of our application and 16.4 has some <uhm> "shortcomings" we are eagerly looking forward to have them fixed in 17 (and it seems Codejock has done a really good job on this). To be honest: actually our customers start insisting*...  As beta2 now doesn't work at all under some aspects (e.g. being built statically with VS2013 // Markups // see above), there is no chance for us to help Codejock (and us) to catch as many issues in advanced as possible. And I'd love to have them caught before my customers are catching them  (and finger-pointing then is only for losers and no good style and the customer would not even care about that as he/she just wants OUR application to work properly)just my 2 cts *) Being that: if there is anything we could do to speed things up: let us know! |
Posted By: hamed
Date Posted: 28 August 2015 at 1:16pm
|
Hi, There is a bug in Beta 2 Vb6 Ribbon and commandbars samples that cause a crash on Windows 10 (both design and runtime), I just want to report it, Thanks, Hamed |
Posted By: Marco1
Date Posted: 28 August 2015 at 2:17pm
|
For me the UI is pretty much essential, too! I meant the cost of releasing new betas. If certain bugs are fixed, just release a new beta with an incremented version number - in short periods. ------------- Product: XTP 18.3.0 on VS 2017 Platform: VS 2017 / Windows 10 (64bit) |
Posted By: terrym
Date Posted: 29 August 2015 at 6:06am
|
Any help on linking errors above would be much appreciated ------------- Thank you, Terry Mancey email terry@tmancey.ltd.uk | linkedin www.tmancey.ltd.uk | twitter @tmancey |
Posted By: kstowell
Date Posted: 29 August 2015 at 1:01pm
This looks like a problem on your end, make sure you are linking against the same version of MFC. For example if you build the Toolkit using Visual Studio 2013 then try linking your application against that build using Visual Studio 2015 you will get errors like that. At first glance this is what appears to be happening. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: terrym
Date Posted: 01 September 2015 at 5:15am
|
Only have Visual Studio 2015 installed, built toolkit using VS 2015 and then built our app using VS 2015. ------------- Thank you, Terry Mancey email terry@tmancey.ltd.uk | linkedin www.tmancey.ltd.uk | twitter @tmancey |
Posted By: BeeJay
Date Posted: 01 September 2015 at 6:07am
|
@terrym: just a guess: please check whether the respective .cpp source files containing the missing methods are really part of the XTP source solution project (and target!) you are using to build XTP. Probably there is a problem that for your specific target they have been forgotten or are "excluded" by mistake or whatever. |
Posted By: Taro
Date Posted: 01 September 2015 at 10:40am
|
Hello, I checked with my product download page for beta download. I didn't see any link. Just point to v.16.4. I don't know why. Please kindly supports. |
Posted By: adrien
Date Posted: 01 September 2015 at 5:56pm
Hi Kirk any update on this one? Just back from vacation and wondering whether to try beta 2 or hold off for 2.1 ------------- http://www.wingate.com - http://www.wingate.com |
Posted By: markr
Date Posted: 04 September 2015 at 11:08am
|
Kirk, > Yes most likely a BETA 2.1 that addresses the immediate problems with BETA 2 looks like sometime next week. Can we still expect this today? - Mark R.
|
Posted By: kstowell
Date Posted: 18 September 2015 at 12:42pm
We just posted Beta 3 for download a few days early, we were planning on releasing it this Monday. You will see the download link on the same page as the Toolkit Pro and Suite Pro download link. You will need an active subscription to download Beta 3. We will be making an official announcement this weekend. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: markr
Date Posted: 18 September 2015 at 2:36pm
|
Still seeing quite a few problems with BETA 3, I'm afraid. Guess I'll start with a quick overview and you can let me know where you want/need additional details. - When using Office 2010 ribbon themes (with themed frame), the title bar loses color (becomes lighter) whenever the window loses focus. Appears to be a new bug in BETA 3. - Themed (Office 2010/2013) radio buttons don't redraw correctly after their check status changes. I have to hover over them to force a redraw. Bug appears to be present in all v17 BETA builds. - Unwanted borders around all standard toolbars (Office 2010 themes only). - With Office 2013 themes, small toolbar split buttons (xtpControlSplitButtonPopup) are drawn with an unwanted border around them when they're in a disabled state (they are fine with enabled). - Unwanted borders around themed (Office 2010 only) modal dialog frames (especially on the bottom). Appears to be a new bug in BETA 3. - When using the Office 2013 "light" themes, there is no border for docking panels. So if you have multiple panels stacked on top of one another, they become indistinguishable from one another. In the example below, there's no indication of where the pane starts and the client area ends.  - Office 2013 theme still isn't drawing tab icons (they show up just fine when using Office 2010 themes). - In debug mode, I see the following TRACE output a huge number of times (not a big deal, but it really slows down debugging): "..\..\Source\Markup\XTPMarkupBuilder.cpp(1126) : atlTraceGeneral - No Error" - Office 2013 theme crashes when I attempt to update window placement (again, doesn't happen with Office 2010 themes). Appears to cause heap corruption. Stack trace: > FolderSizes.exe!Gdiplus::GdiplusBase::operator delete(void * in_pVoid) Line 24 C++ [External Code] FolderSizes.exe!CXTPFrameShadow::PreComputedData::~PreComputedData() Line 141 C++ [External Code] FolderSizes.exe!CXTPFrameShadow::ComputeData() Line 530 C++ FolderSizes.exe!CXTPFrameShadow::Update(int bReposition, int bRedraw) Line 756 C++ FolderSizes.exe!CXTPFrameShadow::Show() Line 412 C++ FolderSizes.exe!CXTPFrameShadowManager::OnHookMessage(tagCWPRETSTRUCT * pc) Line 436 C++ FolderSizes.exe!CXTPFrameShadowManager::CFrameShadowHook::OnHookMessage(HWND__ * __formal, unsigned int __formal, unsigned __int64 & __formal, __int64 & lParam, __int64 & __formal) Line 73 C++ FolderSizes.exe!CXTPHookManager::CHookSink::OnHookMessage(HWND__ * hWnd, unsigned int nMessage, unsigned __int64 & wParam, __int64 & lParam, __int64 & lResult) Line 298 C++ FolderSizes.exe!CXTPHookManager::OnWindowsHookProc(int idHook, int nCode, unsigned __int64 wParam, __int64 lParam) Line 519 C++ FolderSizes.exe!CXTPHookManager::OnWH_CALLWNDPROCRET(int nCode, unsigned __int64 wParam, __int64 lParam) Line 499 C++ [External Code] FolderSizes.exe!CWnd::SetWindowPlacement(const tagWINDOWPLACEMENT * lpwndpl) Line 1235 C++ Regards, Mark R.
|
Posted By: markr
Date Posted: 18 September 2015 at 4:00pm
|
I wanted to swing back around and provide a couple of screenshots relating to my post above. First, regarding the unwanted borders that are new to v17. The screenshot below shows a themed dialog (Office 2010 theme) with a standard toolbar. Compared to v16, there's a border on either side of the toolbar (it disappears if I link against v16). Also, there's a border on the bottom of the dialog frame that didn't exist in v16 (or v17 BETA 1).  Switching to the Office 2013 theme, I'm seeing that frame captions are not centered consistently. Switching between Office 2010 and 2013 themes shows a fairly huge change in centered caption position (which I assume is unintentional?). Also, small toolbar buttons have an unwanted border around them when they are disabled (doesn't appear when enabled).  I've found a few other problems, too, and will post about those when time permits. Regards, Mark R.
|
Posted By: markr
Date Posted: 19 September 2015 at 8:44pm
|
Please disregard the problem I mentioned regarding the XAML/markup background. I was able to tweak the XAML to eliminate the issue, and I don't think it would be encountered in most other scenarios (I just use markup very heavily). - Mark R.
|
Posted By: markr
Date Posted: 21 September 2015 at 3:10pm
|
My research indicates that both the unwanted bottom frame border and the title bar color issue (when the frame loses focus) are both caused by the removal of: FlatFrame = 1 ... from the [Window] section of the BlueTheme.ini, BlackTheme.ini, and SilverTheme.ini style files (for Office 2010). In fact, removal of this flag also affects (breaks) the rendering of the frame when DWM is enabled. It seems that someone might have removed this flag without entirely understanding the consequences (or thoroughly testing the results). However, the unwanted toolbar borders seem to be unrelated (e.g. caused by some other issue). - Mark R.
|
Posted By: Alopez
Date Posted: 19 November 2015 at 10:10am
|
Hi, we wanted to give everyone an update on the schedule for 17.0 product release. We are in the final stages of preparing a release candidate for version 17.0. We plan on releasing this by the end of this month. The RC version will be in testing phase for 2 weeks and if no significant issues are reported we will schedule a final release for the third week in December. Thank you, ------------- Anthony Lopez, Technical Support CODEJOCK SOFTWARE SOLUTIONS |
Posted By: kstowell
Date Posted: 11 December 2015 at 11:44am
|
Release Candidate for v17 has been published. This will be the last of the betas that we publish prior to the final release version. We are looking to publish the final v17 product release by the end of December. ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: Kenneth
Date Posted: 12 December 2015 at 9:10pm
| The deploy wizard does not work on Windows 10 using Visual C 6.0. It did work on beta 3. It appears to me to be a different or newer deploy wizard. |
Posted By: kstowell
Date Posted: 13 December 2015 at 2:38pm
Can you please provide me with the following information (I just want to verify): 1. Version of Windows. 2. Visual Studio Version(s) you have installed. 3. Versions of Codejock product(s) you have installed. This will help us to try and reproduce the problem on our end, thanks! ------------- Kirk Stowell, President and CEO CODEJOCK SOFTWARE SOLUTIONS< |
Posted By: Alex H.
Date Posted: 24 May 2016 at 6:14am
|
With XTP 17.2 unfortunately there is no gap between the gripper and the first control of a toolbar. At least one pixel would be great! Please have a look at Visual Studio:  |