Component Pack 22.214.171.124
Delphi 10.1 Berlin
Windows 7 x64
Component Pack 126.96.36.199
I retested this here with the demo but I cannot see any issue.
Yes, clean install. I did not mention that i am using 120dpi and it could be the reason. I will try running the demo app on a VM I keep specially to vary the text size settings. This might be a Berlin issue since there are lots of reported issues with Berlin at other than 96dpi
No, it is not text size. There is no problem with the demo program on W10/64 at 100%, 125% or 150%. But the box is still misplaced on my main development system (W7/64 at 125%). I will investigate with a debugger!
I set a breakpoint in the 'EDIT' section of the StartParamEdit method. The value of pt is exactly the same on the first and second attempt to edit the field, but the box pops up in different places.
Final post today. The problem occurs when running on Windows 7 and the screen text size is not 100% and the form Scaled attribute is set. It does not occur when the screen text size is 100%, and it does not occur on Windows 10 at any text size. The development machine was running with the screen text size 125% when the demo program was built.
This indeed is related to an issue in the VCL itself. We have implemented a workaround for this though and this workaround will be included in the next update.
- I'm not sure I understand your remark. When a checkbox is clicked, the control.ItemIndex property indicates what checkbox was clicked, regardless of the list having comment items.2. There can indeed be an index of items (TParamListBox, TParamCheckList) and an index of parameters itself within an item. We have made this more clear in the doc by now referring to ItemIndex and ParamIndex.
3. We have corrected references to href as being an integer to string.4. The info about ParamProps was also updated to include the TOGGLE.Next TMS Component Pack update will have this updated doc.
All good! My point in (1) is that in the current on-click event, I am passed the itemindex in the control. But I ALWAYS need to know the parameter that has been check-clicked (I only have one href per line), It would be good if there was an href parameter for the onclick event, because the paramindex is offset by the number of preceding comments, so needs work to use.
I'm sorry but this message is confusing to me. You refer to OnClick (only Sender parameter) , OnCheckClick (only Sender parameter).
If you want to detect clicks on parameter values in items, please use the OnParamClick. This returns as 2nd parameter the index of the item that contains the parameter (regardless of comment items) and the 3rd parameter is the href of the parameter value.
When you click the checkbox of a checklist item, only OnCheckClick is triggered and with ItemIndex you can identify the item for which the checkbox was clicked.If from that event you want to do anything with the parameter values of that item, you can use ParamItemRefCount[ItemIndex] and loop through the item parameter values with ParamItemRefs[ItemIndex,ParamIndex]: string
Yes, apologies for my typo - I meant to refer only to the oncheckclick event. OnParamClick is fine. And yes, I know there are workarounds, either involving a loop or (as I have used myself) building a lookup table in advance. All I am pointing out is that since the whole component is (very usefully and consistently) parameter-centric, it is a pity that OnCheckClick requires work to connect it equally easily with the parameter(s) being enabled and disabled.
The checkbox shouldn't be treated as a parameter. This is similar to a node in a TParamTreeview where the node shouldn't be treated as a parameter as well. The TParamCheckList is basically a TParamListBox with a checkbox, similar to a TCheckListBox is a TListBox with embedded checkboxes per item and the OnCheckClick is kept consistent with how a TCheckListBox is to a TListBox.