Buttons Not Being Queried
Posted: Fri Apr 02, 2021 12:36 pm
As an adjunct to this thread (https://devforum.softprocorp.com/viewto ... f=8&t=1384), I've discovered a new problem: buttons that have been registered using the RegisterHandler call, with the proper reference to the handler method, but the query never comes from the runtime.
The specifics of this are: I have four buttons in total, two that are loaded into a custom tab on the top ribbon, and two that are attached to the Order tab (Order tab is referenced in the CTD file as follows:)
Nothing unusual there, and all the buttons in both areas render properly and perform their click-handling functionality as they should. The problem arose when I started to attach a query handler to the buttons, and I noticed that only one of them (which is attached to the Order tab) would ever send queries to the handler method (a common one that I'm using to set permissions on the buttons). No matter what I try (splitting into separate handler methods, thread locking, etc.,) only one button has ever raised a query event.
Do you have any insight as to what might be blocking query events from the other buttons, or if you have seen this behavior in general? It's not a complete show-stopper for me, as I've already put code into the click events to intercept and check permissions before any further processing. It'd be nice to have the button-disabling option pre-click, though.
The specifics of this are: I have four buttons in total, two that are loaded into a custom tab on the top ribbon, and two that are attached to the Order tab (Order tab is referenced in the CTD file as follows:)
Code: Select all
<Guid name="OrderTabCommandSetGuid" value="f436331e-3d02-4b9b-af76-fc878517bcf9">
<ID name="OrderTab" value="4501" />
</Guid>
Do you have any insight as to what might be blocking query events from the other buttons, or if you have seen this behavior in general? It's not a complete show-stopper for me, as I've already put code into the click events to intercept and check permissions before any further processing. It'd be nice to have the button-disabling option pre-click, though.