It's been a long-awaited update, and finally, it's here with a host of exciting new features and long requested fixes! This release is particularly special as it introduces two outstanding features that the Codejock community has been anticipating for many years: complete SVG support and the new Gauge control! Alongside these two fantastic additions are numerous other enhancements and improvements.

Complete SVG support has finally been added to both ToolkitPro and SuitePro. Yes, that means our users can now enjoy scalable and easy-to-manage SVG icons in CommandBars, Ribbon, and other controls. Additionally, SVG images can be previewed in the Preview control, used in Markup, image managers, and loaded and drawn using a dedicated CXTPSvgImage class (ToolkitPro only). 

We're opening a new chapter in Codejock's history by introducing a framework for creating and using professional gauges to express complex measurements in simple, attractive, and highly customizable forms. Built entirely in Markup and JavaScript, the Gauge control allows for the creation and extension of multi-dimensional gauges where almost every visual element can be configured or animated to meet the most demanding business needs. The initial implementation allows for analogue meter gauges of up to five dimensions, a digital screen of up to five dimensions, and a state-reflecting gauge for an unlimited number of states. You can find the main FAQ article on it here:  http://https//codejock.com/support/articles/mfc/gauge/gc_intro.asp" rel="nofollow - Link to the FAQ

Make your application look modern and consistent on all supported OS versions using the new Windows 11 theme, available in Light and Dark color schemes.

Many other smaller yet important additions and fixes have been included, including significant improvements to time-consuming data and image processing algorithms by enabling parallel computations, extended COM/OLE initialization for MFC apps, new WebView2 initialization properties for the WebBrowser control, markup support for ComboBox, a large number of Markup fixes and improvements, especially those related to Markup stability, performance, and scripting, SVG primitives that replace dependency on Codejock.ttf, a number of reworked samples, and much more. 

We'll be happy to hear all feedback from you about this release and we're grateful in advance for sharing your thoughts with us. Please refer to our release notes for this version on our website  http://codejock.com/products/releasenotes/release_notes.asp" rel="nofollow - https://codejock.com/products/releasenotes/release_notes.asp  

}

3) Found the link to gauge here - the one in the post was broken:  https://codejock.com/support/articles/common/gauge/gc_intro.asp" rel="nofollow - Gauge Control (codejock.com)

XAML with MatrixTransform still doesn't work. Look here for a fix I applied on an earlier release:

https://forum.codejock.com/making-xaml-icons-with-matrixtransform-work_topic24367.html?KW=matrixtransform" rel="nofollow - https://forum.codejock.com/making-xaml-icons-with-matrixtransform-work_topic24367.html?KW=matrixtransform

FlatEdit (Appearance = NativeWindows11) in Windows 11 environment still does not have the same theme as the TextBox native control

And I have reported a bug earlier that is said to be fixed, but it is not in beta 1. 

So what way is the best to give feedback and ask questions like these?

Best regards 

Mats

Hi,

Are the sample application available somewhere for version 24 Beta (without need to build them)?

download section only provides for stable version 22.1 (which makes sens)

https://codejock.com/downloads/samples/" rel="nofollow - https://codejock.com/downloads/samples/

and account download only shows the installer and help, but no sample, as usual.

CXTPCommandBars::TrackPopupMenu(&oMenu, TPM_LEFTALIGN | TPM_RIGHTBUTTON, point.x, point.y, this);

if (GetCommandBars()->GetPaintManager()->IsPopupRoundedCorners(pt))

Similar issue here upgrading from 19.3.0 to 24.0 Beta 1

I get a crash with the exception:

Exception thrown: read access violation. this was nullptr.

CXTPPaintManager* CXTPCommandBars::GetPaintManager() const { return (NULL != m_pPaintManager ? m_pPaintManager : XTPPaintManager()); }

I'm glad to inform you that the issue has been addressed and fixed. The fix will be available in the next beta or final release.

As hotfi you can to chage line

if (GetCommandBars()->GetPaintManager()->IsPopupRoundedCorners(pt))
to
include "Common/XTPMacros.h"
..
if(XTP_SAFE_GET2(GetRootParent(), GetPaintManager(), IsPopupRoundedCorners(pt), NULL))

Regards,

Artem Gontarenko

Having exactly the same issues as stated here. Downloaded the beta on 24/05/2024.

Anton

The window on the application side (in this case CXTPBrowserCtrl) is just a host parent window for the browser window. The actual browser window is managed by WebView2 itself, and that is managed out to a different process. Hence, your application process/thread won't see the usual mouse messages. And the HWND of the actual browser is not intended for use. I don't think WebView2 has mouse event handlers (but I may be wrong). If you want to deal with user interaction, I would expect it to be implemented on the page itself.

As for ExecuteScript. I believe the return value is a HRESULT indicating success of beginning execution of the script. You need to use the out parameter for get the return value of the script. Keep in mind that WebView2 is asynchronous. ExecuteScript will pump messages until the result is available.

or

WebBrowser1.ExecuteScript("document.getElementById('body').scrollTop = 0;")

produces nothing!  I placed both of these in the NavigateComplete2 sub, so the DOM should be ready at this point, correct?