Codejock Developer Community : General Discussion

General Discussion : Toolkit pro v 15.3.1 and Visual Studio 2015 vc140)

Tue, 04 Mar 2025 09:50:57 +0000

Author: astoyan
Subject: Toolkit pro v 15.3.1 and Visual Studio 2015 vc140)
Posted: 04 March 2025 at 9:50am

The latest officially compatible Visual Studio version for Toolkit Pro 15.3.1 is 2010. It is possible that there will be compatibility issues if it is compiled in Visual Studio 2015 as it has not been tested. It is also possible that those compatibility issues will be quite simple to fix manually, i.e. a few simple compilation errors/warnings. So, at least it is worth trying despite the lack of the official support.

Regards,

Alexander

General Discussion : Toolkit pro v 15.3.1 and Visual Studio 2015 vc140)

Sun, 02 Mar 2025 14:20:51 +0000

Author: Marecki Marek
Subject: Toolkit pro v 15.3.1 and Visual Studio 2015 vc140)
Posted: 02 March 2025 at 2:20pm

Is it possible to compile Toolkit pro v15.3.1 using vc140?

General Discussion : Skin or theme?

Tue, 07 Nov 2023 04:25:31 +0000

Author: matsjansson
Subject: Skin or theme?
Posted: 07 November 2023 at 4:25am

I have an old MDI application that I want to get to look nicer, getting rid of the round corners of the MDI child windows.

My first understanding was that this is done using skins.

Now I recognized that it also seems to be possible to accomplish using themes.

What is the difference using skins or themes?

General Discussion : XTPImageManager::AddIcons appears to be buggy.

Tue, 05 Sep 2023 04:54:15 +0000

Author: agontarenko
Subject: XTPImageManager::AddIcons appears to be buggy.
Posted: 05 September 2023 at 4:54am

Hello,

Unfortunately we are unable to re-produce the problem. Can you please provide more detailed information and steps to take, screenshots or video can be useful as well. If it cannot be re-produced in any of our sample applications provided I would appreciate you sending a small code snippet or ideally a sample application so that we could debug it.

Regards,
Artem Gontarenko

General Discussion : Developer wanted

Mon, 04 Sep 2023 15:42:03 +0000

Author: chsgermany
Subject: Developer wanted
Posted: 04 September 2023 at 3:42pm

Hello everybody,

we are looking for experienced developer that can create or modify style for us.

Most important to us is to modernize the look and feel of MFC application.

Ideally no borders around the windows anymore

Best would be if the application shown below looks bit similar to the first screen shot.

Please let me know if you know somebody that would be interested to take that task.

General Discussion : XTPImageManager::AddIcons appears to be buggy.

Fri, 01 Sep 2023 20:07:45 +0000

Author: lviolette
Subject: XTPImageManager::AddIcons appears to be buggy.
Posted: 01 September 2023 at 8:07pm

As a work-around, and possibly a more correct way to do this. I updated the code to avoid a temporary CXTPImageManager and it "appears" to be functioning correctly.

void CMyXTPResizeDlg::UpdateImages()
{
    static UINT pnCommands[] = 
    {
        ID_WETRACK_AUTOKEY, ID_WETRACK_UPDATEKEY, ID_WETRACK_SCALEMODE
    };

    {
        CXTPTempColorMask mask(RGB(255, 0, 255));
        XTPImageManager().SetIcons(IDPNG_TOOLBAR_WETRACK, pnCommands, 3, CSize(16, 16));
    }

    // This avoided the local image manager.
    // From what I've seen so far, the buttons are showing correctly.
}

General Discussion : XTPImageManager::AddIcons appears to be buggy.

Fri, 01 Sep 2023 18:57:28 +0000

Author: lviolette
Subject: XTPImageManager::AddIcons appears to be buggy.
Posted: 01 September 2023 at 6:57pm

Code that worked in 18.3, but appears to be broken in 22.1. This code is lead-up to a crash I'm having while migrating to 22.1

Consider the following:


void CMyXTPResizeDlg::UpdateImages()
{
    static UINT pnCommands[] = 
    {
        ID_WETRACK_AUTOKEY, ID_WETRACK_UPDATEKEY, ID_WETRACK_SCALEMODE
    };

    {
        CXTPImageManager localImageManager;
        localImageManager.SetMaskColor(RGB(255, 0, 255));
        localImageManager.SetIcons(IDPNG_TOOLBAR_WETRACK, pnCommands, 3, CSize(16, 16));
        GetCommandBars()->GetImageManager()->AddIcons(&localImageManager);
    }

    // When the iconsets were copied over, their CXTPImageManager* member was NOT updated.
    // They are still pointing at localImageManager even though are actually in the dialog's image manager.
    // This results in a crash down the line.
}

Attempt to explain why we crash...


void CXTPImageManager::AddIcons(CXTPImageManager* pImageManager)

This function adds icons from one image manager to another. It does so by iterating over

the icons, retrieving each iconset and passing the iconset to

void CXTPImageManager::AddIcons(CXTPImageManagerIconSet* pIconSetAdd)

This function then iterates over the various icons in the icons set and adds them to the iconset of the image manager.

But, it does so by constructing a CXTPImageManagerIcon like so:

pIcon = new CXTPImageManagerIcon(pIconSetAdd->GetID(), pIconSetAdd,
                                            CSize(XTPToIntChecked(nWidth), 0));

That pIconSetAdd is actually (&localImageManager). And it's being used as the image manager in this new icon. Which is invalid.

This logic has changed since 18.3.

In 22.1, it crashes in CXTPImageManager::SetIcon(const CXTPImageManagerIconHandle& hIcon) because I am updating one of the images and it hits this code:

if (m_pIconSet)
    m_pIconSet->RefreshAll();

Since m_pIconSet is pointing to the deleted localImageManager, it crashes. In 18.3 m_pIconSet here would have been nullptr, so it would have skipped calling RefreshAll.

My question is...

Is CXTPImageManager::AddIcons(CXTPImageManager* pImageManager) working as intended?

Is it suppose to take the images in pImageManager, add them to "this", but leave them with pointers to pImageManager rather than "this"?

I'd like an answer to this before I rewrite this code I inherited to add the icons the to image manager and correctly set the iconset's m_pImageManager pointer.

General Discussion : Visual Studio 2022 C'ant Compile MFC

Tue, 18 Apr 2023 07:11:25 +0000

Author: agontarenko
Subject: Visual Studio 2022 C'ant Compile MFC
Posted: 18 April 2023 at 7:11am

Hello,

Do you use Codejock? Can you describe more detail of problem.

I've tested with clean Windows 11 + VS2022 and any problem not found.

Regards,

Artem Gontarenko

General Discussion : Visual Studio 2022 C'ant Compile MFC

Sat, 18 Mar 2023 15:13:50 +0000

Author: miguelandradebr
Subject: Visual Studio 2022 C'ant Compile MFC
Posted: 18 March 2023 at 3:13pm

Hello guys!

The see video here:

https://www.youtube.com/watch?v=6eyu34fO0oU[TUBE]6eyu34fO0oU[/TUBE]

I've created a MFC Dialog Application and put a button on it and tried to compile and got this message:

RC2135: file not found

How to solve?

Thanks

General Discussion : Unified visual appearance

Thu, 11 Jun 2020 03:26:46 +0000

Author: cpede
Subject: Unified visual appearance
Posted: 11 June 2020 at 3:26am

The CodeJock is a great toolkit and makes life much easier for me when developing applications. However with the growing focus on visual appearance, I would like the toolkit to be more unified.

Fx.

*Splitter Trackers: when using the splitter trackers for docking windows it uses alpha blending and when using for splitter control, property editor etc. it uses PatBlt, giving different results.

*Tooltips are not the visual same for all controls.

*Themes are not affecting the scrollbars in the controls, even a lot of code is made for scrollbars.

It is so close to being perfect :-)

-cpede