TD 6.2 GUI.NET and XAML

Transcription

1 DOCUMENT TYPE Title Here TD 6.2 GUI.NET and XAML OpenText Gupta Team Developer Progress Bar A new control called Progress Bar has been added to the control lists. Progress Bar will be the alternative to cmeter. There are 14 new SalMeterxxxx functions added to the Sal func-tion library to make the Progress Bar control useful. To use this control, it is required to set the start, end and step values. As the start value is incremented or decremented, the progress will be shown in the bar based on the step value. SalMeterSetRange() can be used to set the range and SalMeterSetStepSize() can be used to set the step size. As the value increments or decrements, the progression will be affected. Step size plays a role in how fast or slow the bar progresses. It is also possible to set start and end colours for the Progress Bar. The colour will gradually change as the progression happens. In the example below, pink is the start colour and green is the end colour. The functions SalMeterSetFromColor() and SalMeterSetToColor( ) are used to set the colours.

2 Another interesting functionality is that the Progress Bar allows the progress to be shown vertically or horizontally. The function SalMeterSetVertical(), when called with TRUE as the second parameter allows the progression to be shown vertically. The function SalMeterSetVertical(), when called with FALSE as the second parameter al-lows the progression to be shown horizontally. New Sal Functions The new sal functions and parameters are described below. SalMeterGetRange: Returns the current "range" of the progress bar, both the minimum and maximum values. Receive Number: The minimum of the range Receive Number: The maximum of the range SalMeterSetRange: Sets the current "range" of the progress bar, both the minimum and maximum values. Number: The minimum of the range Number: The maximum of the range SalMeterGetFromColor: Gets the color at the beginning of the gradient used to indicate progress. Return value: The current "From" color of the progress bar O P E N T E X T G U P T A T E A M D E V E L O P E R 2

3 SalMeterSetFromColor: Sets the color at the beginning of the gradient used to indicate progress. Number: The new "From" color of the progress bar SalMeterGetToColor: Gets the color at the end of the gradient used to indicate progress. Return value: The current "To" color of the progress bar SalMeterSetToColor: Sets the color at the end of the gradient used to indicate progress. Number: The new "To" color of the progress bar SalMeterGetStepSize: Gets the current amount the progress bar's value will be incremented or decremented when calling SalMeterStepUp/SalMeterStepDown. Return value: Returns the current step size SalMeterSetStepSize: Sets the current amount the progress bar's value will be incremented or decremented when calling SalMeterStepUp/SalMeterStepDown. Number: The new step size SalMeterGetSmooth: Gets the current "smooth" setting. See SalMeterSetSmooth for more details. Return value: Returns TRUE or FALSE for the current "Smooth" setting. O P E N T E X T G U P T A T E A M D E V E L O P E R 3

4 SalMeterSetSmooth: Sets the current "Smooth" setting. If smooth=true, the progress bar displays progress with a continuous gradient. If smooth=false, the progress bar displays progress with chunks of progress. Each chunk of progress con-tains the specified gradient. Boolean: The new "smooth" setting Return Value: Returns TRUE or FALSE indicating the success or failure of the operation SalMeterGetVertical: Gets whether the progress bar is displayed horizontally or vertically. Return value: Returns TRUE if the progress bar is currently displayed vertically, or FALSE otherwise SalMeterSetVertical: Gets whether the progress bar is displayed horizontally or vertically. Number: The new "vertical" value - TRUE will cause the progress bar to be displayed vertically. SalMeterStepDown: Causes the progress bar to decrease its value by the current "Step Size". Return value: Returns the new value of the progress bar SalMeterStepUp: Causes the progress bar to increase its value by the current "Step Size". Return value: Returns the new value of the progress bar Named Toolbar Extensions Team Developer 6.1 did introduce a new object of named toolbars. Named toolbars look and behave similar to the toolbars the TD IDE is using. With Team Developer 6.2 we are enhancing the capabilities of named toolbars by a new set of APIs that allow more control over the toolbar buttons behavior. O P E N T E X T G U P T A T E A M D E V E L O P E R 4

5 Named toolbars are defined in the Global Declarations section of the app outline. Individual application windows can load any number of defined named toolbars at application runtime. Named toolbars can be rearranged by the user to meet personal usability requirements. Named toolbars can be dragged around in the toolbar of a window allowing things like multi-row toolbars and such. The image shows a sample of re-arranged named toolbars using two rows of toolbars. Named Toolbars can include toolbar buttons and menu separators. Each toolbar button has an Actions section that allows coding the desired actions of the button. The outline structure of a named toolbar and its contents. Creating a toolbar at runtime is done via TD s SalCreateWindow() function. The first param-eter is the named toolbar name; the second parameter is the window handle of the parent window that should open the named toolbar in its toolbar area. The image shows how creating 3 toolbars for a TD form window is done. O P E N T E X T G U P T A T E A M D E V E L O P E R 5

6 With Team Developer 6.2 we are introducing a set of new APIs to enable and disable named toolbar items. Plus we are introducing a new method to change the text portion and the tooltip of a named toolbar button. Another new method allows you to set the background color of a named toolbar button. SalTBEnableItem This new function enables a specified named toolbar item in a specified named toolbar. usage: result = SalTBEnableItem( hwndtb, nindex ) Boolean result: success or failure of the operation Window Handle hwndtb: the window handle of the named toolbar Number nindex: The 0-based index of the toolbar item to enable SalTBDisableItem This new function disables a specified named toolbar item in a specified named toolbar. usage: result = SalTBDisableItem( hwndtb, nindex ) Boolean result: success or failure of the operation Window Handle hwndtb: the window handle of the named toolbar Number nindex: The 0-based index of the toolbar item to disable SalTBSetItemText This new function sets the button text of a specified named toolbar item in a specified named toolbar. usage: result = SalTBSetItemText( hwndtb, nindex ) Boolean result: success or failure of the operation Window Handle hwndtb: the window handle of the named toolbar Number nindex: The 0-based index of the toolbar item to whose text is being set SalTBSetItemTooltip This new function sets the button tooltip of a specified named toolbar item in a specified named toolbar. usage: result = SalTBSetItemTooltip( hwndtb, nindex ) Boolean result: success or failure of the operation Window Handle hwndtb: the window handle of the named toolbar Number nindex: The 0-based index of the toolbar item whose tooltip is being set O P E N T E X T G U P T A T E A M D E V E L O P E R 6

7 SalTBGetItemCount This new function retrieves the number of child objects of a specified named toolbar. usage: result = SalTBGetItemCount( hwndtb ) Number result: the number of items on the toolbar Window Handle: hwndtb: the window handle of the named toolbar SalTBSetItemColor Allows to set the background color of a specified named toolbar button residing in a speci-fied named toolbar. usage: result = SalTBSetItemColor( hwndtb, nindex, ncolor ) Boolean result: success or failure of the operation Window Handle hwndtb: the window handle of the named toolbar Number nindex: The 0-based index of the toolbar item whose color is being set Number ncolor: The color number of the color to set the toolbar item This is a sample app for the new named toolbar methods. Below is a URL that allows you to download and try the sample. O P E N T E X T G U P T A T E A M D E V E L O P E R 7

8 .NET 64 Bit Applications With the advent of 64 bit Operating Systems, it now becomes possible to run native 64 bit applications. However, until now TD has always compiled its.net applications as 32 bit, meaning they will always run as 32 bit even if running on a 64 bit OS. In the Project menu build settings dialog, there is now an Advanced button which will bring up a new Ad-vanced Settings dialog box. In this dialog, the user can choose one of three values for the Target CPU: 32 bit: the application will always run as 32 bit, no matter the OS. On a 64bit OS, it will run within the 32 bit subsystem 64 bit: the application will always run as 64 bit and can only run on a 64 bit machine Auto: the application will decide what bitness to use at launch time, depending on the OS or, for DLLs, depending on the process loading it. Note: due to limitations in our debugger, we can only attach to and debug 32 bit processes and so, regardless of the Target CPU setting for your application, when you run it from the IDE it is always built as 32 bit. There is also a new command-line argument to TD for specifying the target CPU when compiling from a DOS prompt. The syntax for the new flag is: "-cpu:32bit", "-cpu:64bit" or "-cpu:auto". O P E N T E X T G U P T A T E A M D E V E L O P E R 8

9 Load XAML Resource Dictionary Dynamically The existing function SalDictionaryPromote (introduced in Team Developer 6.1) allows the user to switch between resource dictionaries giving one higher precedence over the other. A new function called SalDictionaryLoad has been added to the Sal functions in Team De-veloper 6.2. This function will accept a *.XAML file containing a resource dictionary. It will load the dictionary into memory and merge it with the existing dictionaries. The new dictionary will be placed at the bottom of the merge order. This function will help users selectively switch between their resources at runtime. Example 1: The users do not have to have all their dictionaries loaded at the startup of the application. Every form or module could have a separate dictionary. The new function SalDictionaryLoad() can be called to load the specific dictionary just before the module or the form is loaded. Example 2: The users may want to display a form in one language e.g. English and another in a different language e.g. French. SalDictionaryLoad() can be called to load the English dictionary when the English form is loaded and French if and when the French form is load-ed. The new sal function is described below. SalDictionaryLoad String: a *.XAML file Number: for future use Return Value: Boolean indicating success or failure Users will be able to load various resources stored in different directories at run time on demand. O P E N T E X T G U P T A T E A M D E V E L O P E R 9

10 About OpenText OpenText provides Enterprise Information Management software that enables companies of all sizes and industries to manage, secure and leverage their unstructured business information, either in their data center or in the cloud. Over 50,000 companies already use OpenText solutions to unleash the power of their information. To learn more about OpenText (NASDAQ: OTEX; TSX: OTC), please visit NORTH AMERICA UNITED STATES GERMANY UNITED KINGDOM AUSTRALIA Copyright Open Text Corporation OpenText is a trademark or registered trademark of Open Text SA and/or Open Text ULC. The list of trademarks is not exhaustive of other trademarks, registered trademarks, product names, company names, brands and service names mentioned herein are property of Open Text SA or other respective owners. All rights reserved. For more information, visit: SKU#