To ensure that the TabEx widget can be used instead of the Tab widget, fully implement the trigger (including double click) in the TabEx widget.
Use Case
Importance
High
Type
Windows GUI
Operating System
Not Applicable
Status
Open
4 thoughts on “Detail on Tabex”
onTabButton
The onTabButton extended trigger is used to implement the processing that should occur when a user clicks the tab button, if present, in the active tab of the TabEx widget.
trigger onTabButton
; enter your code here
end ; trigger onTabButton"
Description
The onTabButton trigger is typically used to close a tab when the user clicks on the tab button. This button is located on each tab only if theTabButton property of the TabEx widget is True.
Trigger Activation
The onTabButton trigger is activated when the user clicks the tab button on a tab.
This was implemented in 9.6.03, doesn’t this achieve what you are looking for?
It’s not a matter of the tabex button, but the fact that the tabex widget does not provide all the triggers of the older tab widget. Therefore, one can not use the tabex instead of the tab without changing the behaviour of the uniface application.I agree with paul that an enhanced widget should provide ALL features of the underlying one.
… this is mandatory to be able to change from tab to tabex with just a change in the ASN file. But if the tabex does not activate the DTLF trigger, this can not be done. So one has to take away functionality the customers were used to to give them some perhaps new options. This should not occur in a professional application.
Welcome to the online Uniface Community. The Uniface community site is a global communication channel for professional users of Uniface Enterprise Application Development
Uniface.info uses cookies to improve this site and deliver a personalized, secure and responsive service. Read MoreAccept
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
onTabButton
The onTabButton extended trigger is used to implement the processing that should occur when a user clicks the tab button, if present, in the active tab of the TabEx widget.
Description
The onTabButton trigger is typically used to close a tab when the user clicks on the tab button. This button is located on each tab only if theTabButton property of the TabEx widget is True.
Trigger Activation
The onTabButton trigger is activated when the user clicks the tab button on a tab.
This was implemented in 9.6.03, doesn’t this achieve what you are looking for?
It’s not a matter of the tabex button, but the fact that the tabex widget does not provide all the triggers of the older tab widget. Therefore, one can not use the tabex instead of the tab without changing the behaviour of the uniface application.I agree with paul that an enhanced widget should provide ALL features of the underlying one.
… this is mandatory to be able to change from tab to tabex with just a change in the ASN file. But if the tabex does not activate the DTLF trigger, this can not be done. So one has to take away functionality the customers were used to to give them some perhaps new options. This should not occur in a professional application.
ALL documented features I would agree with.
DETAIL was not documented, this is why is was not included in the extended tab project.
Adding it is work that is currently not in our plans.