[SOLVED] AddComboButton(TRUE) does not work!

XTP 15.1.3

Can you please add that function to your test cases. This is the second time it stops working!

Modify ReportSample, in TaskListView.cpp(223)

pColumnStatus->GetEditOptions()->m_bAllowEdit = FALSE;

pColumnStatus->GetEditOptions()->AddComboButton(TRUE);

Voilà! You can't edit your cell!

EDIT:

Patch provided by CJ solves the problem. Thanks Abuenger!

PokerMemento - http://www.pokermemento.com/

Btw, using Visual Studio 2010 SP1.

PokerMemento - http://www.pokermemento.com/

Hi,

I look into a solution for the next release. In the past m_bAllowEdit = FALSE; disabled the edit box but you could still select a constraint from the combobox. The was no way to disable editing entirely.

There must be 3 different modes:
- Editing, Combobox
- No editing, Combobox
- No editing, no combobox

Andre

Codejock support

Hmm, It would still be nice to allow a control be be used only from the drop-down button, or spin button, even it is read-only.

Please see my post:

http://forum.codejock.com/forum_posts.asp?TID=18153&PID=63666&title=readOnly-cxtpcontroledit-with-spin-buttons#63666

Allowing people to use the spin-buttons or combo drop-down without being able to write directly into the edit or combo field!

-cpede

Product: Xtreme ToolkitPro (24.0.0)
Platform: Windows 10 (x64)
Language: Visual Studio 2017 (C++)

This issue also broke my application - I used to have "drop list" behaviour on the combo boxes on my report control, but after upgrading the combo box button does not appear.

Is this anything that will be fixed in a future release and in this case, when is it scheduled? I will not be able to upgrade until then.

Also, it would be good if the release notes listed the breaking changes in the code and what it should be replaced by. The equivalents of m_bHeaderRowsVisible and m_bHeaderRecordsVisible (ShowHeaderRows()/HeaderRowsAllowEdit()) are now found in XTPReportDeprecated implying that they will be removed in the future. Then, by what?

Thanks

Windows 10, Visual Studio 20157, Toolkit Pro 18.3.0

no need to worry, nothing will be removed and no application broken.

What I meant with "breaking changes" for me was that the application did not compile after upgrading. And that after replacing the deleted members with (what I think) correct calls my combo boxes no longer worked.

The compilation errors were due to that I have a derived CXTPReportControl where I accessed m_pHeaderRows (now private), m_bHeaderRowsVisible (now gone) and m_bHeaderRecordsVisible (also now gone) and a m_pImageManager somewhere (now private).

But yes, I do agree with that the changes are for the better.

Windows 10, Visual Studio 20157, Toolkit Pro 18.3.0

Please provide a patch or a release date when this will be fixed.

Please do not tell me to file a support ticket. I already did. Long time ago. No response.

PokerMemento - http://www.pokermemento.com/

Great to hear!

Now, did the test pass with the latest build? :P

15.1.4 soon to come?

PokerMemento - http://www.pokermemento.com/

Hi,

I have the same problem - unfortunately this broke the current release and I need to fix it up and update the version urgently. I can't seem to find the patch mentioned, can someone please point me to it? Thanks!

// W7 64 Ultimate SP1
// VS 2008
// CodeJock 16.2.3 (MFC)

Yes, the latest release fixes this issue, thanks.

// W7 64 Ultimate SP1
// VS 2008
// CodeJock 16.2.3 (MFC)

Is this fix included in 15.2.1.0403?

PokerMemento - http://www.pokermemento.com/