Although I use Python to modify the CheckdState property of the checkbox in the click event, it can force its state not to change. Make the user appear unchanged. But the problem lies in the modification event of the document triggering, which leads to the editor triggering the save event (i.e. WOPI calling back the server’s save), which can cause errors in the data. In short, forcing the modification of CheckdState may not be feasible. Is there any other way to make it read-only?
Disable Interaction:
- You can set the checkbox’s
Interactiveproperty toFalse. This will prevent any user interaction with the checkbox, effectively making it read-only.
I am not sure about this solution. Let me find if there is also other possible ways as well…
Thanks,
Darshan
@gulixiang maybe if you use Marco to revert the change? will that work , not sure of this approach but just a thought
Use a Macro to Revert Changes:
- Instead of directly modifying the
CheckedState, you can write a macro that listens for changes and immediately reverts the checkbox to its original state. This may prevent the triggering of unwanted save events. ( just poc can you please try ?)
Sorry, I didn’t quite understand what you meant. The Python script I used immediately changes the state of the checkbox when clicking on an event. What is the difference between ‘Marco to reverse the change?’? Or do you mean to add modify listening events on the content checkbox control? It seems that there is no way to add events to the content checkbox.
Addendum: My operation is a content checkbox, not a form checkbox control. They are two objects
Perhaps it’s a good idea to ask this question on Matrix as well. There are many people there who might have faced the same issue, so we could get some insights on what to try next. I’m feeling a bit unsure about the next steps at this point.