Tab in control

Hello,
I'm looking to create a control that I want to insert a tab control inside. Do you know a way to do it?
Thank you,

coolaid wrote:
I don't really want it to act like a cluster.
Well, that's good, because you can't.
I only want to organize my front panel. But, It would be easier to me to add it in the custom control.
It would be, but due to the technical reasons I indicated above, you cannot do so. The tab control has to go on a VI, not on a custom control. It may work with an XControl, but I've never tried that.

Similar Messages

IE script to open multiple tabs in quick tab view (control Q)

First thanks Scripting Guys for all the great information provided by this forum! I'm using Windows 7 Internet Explorer 8. I'm looking for a VB Script that when lauched opens multiple webpages in one browser, so each page has it's own tab and
I need it to open in Quick Tab view (control Q). When users launch the script it will open a page with all the home pages visible. Thanks for any help you guys provide.

I did find some script that somewhat works, the position of the browser is messed up if I have other tabs open it will be added on, but I need it in a seperate browser, and I still need to change view to Quick Tab.
'***This Browser Window Posistion***
Option Explicit
Dim navOpenInNewTab : navOpenInNewTab = &h0800
Dim navOpenNewForegroundTab : navOpenNewForegroundTab = &h10000
Dim surl : surl="http://www.yahoo.com"
Dim sur2 : sur2="http://www.cnn.com"
Dim count : count = 0
Dim objIE : Set objIE = Wscript.CreateObject("InternetExplorer.Application","objIE_")
objIE.Visible = True
objIE.top = 0
objIE.left = 1370
objIE.Height = 770
objIE.Width = 650
'=======================================
'***Open web tool Main Browser***
objIE.Navigate surl
Wscript.Sleep 2000
objIE.navigate2 sur2, 2048
Wscript.Sleep 2000

Call report selection screen in module pool program with tab strip control

Hi,
Could anyone explain in detail to call report selection screen in module pool program with tab strip control.
Thanks
Mano

Hi,
Refer std program:
demo_sel_screen_in_tabstrip.
demo_sel_screen_with_tabstrip.
Call your program with SUBMIT stmt form module program.
Reward points if this Helps.
Manish

About the data of table control in tab strip control

hi experts:
I use screen 0001 include one tab strip control,and its include two subscreens,one of it is table control(subscreen is 0003).
I input data in the table control,when I click the button of tab strip control to change to another subscreen 0002.I found that the data I input into table control have not append to internal table.how can I solve this problem?
appreciate your reply.thanks a lot.

Hi,
in the Main Screen
In PAI
call subscreen sub. ---> here it calls the subscreen where the tablecontrol is placed
then call module user_command
In the subscreen where you have your table control
in PAI
Loop at itab.
module modify_tab.
endloop.
module modify_tab,
descirbe table itab lines tc-lilnes.
if tc-lines <= tc-current_line.
modify itab index tc-current_lilne.
else.
append itab.
endmodule.
next you call the module user_command on the main screen
module user_command
case sy-ucomm
WHEN 'TAB1'
TS-ACTIVE_TAB = 'TAB1'
when tab2.
ts-active_tab = 'TAB2'.
endmodule
further you can take the help of CONTROL EXAMPLES in DWDM tcode
Regards
Ramchander Rao.K

Adding tabs dynamically at runtime for a tab navigator control

Hi,
Is it possible in flex builder 2 to dynamically add the tabs
at runtime to the tab navigator control, if we can add plz tell the
procedure to do that
thanks in advance

Given that you had a tab navigator declared in mxml like
this:
<mx:TabNavigator id="myTabber" selectedIndex="0">
</mx:TabNavigator>
you should just be able to call the addChild method, passing
the child tab containers. So for example, in some ActionScript
event handler:
var newTab:Canvas = new Canvas();
myTabber.addChild(newTab);
bear in mind I haven't done this by adding tabs, but have
done tons with adding controls to an application at runtime using
this method (DataGrids, Grid, GridItems, etc...)
Jason

Help me in tab strip control

HI,
CAN ANY ONE GIVE ME THE ADVICE PLEASE URGENT.
CAN I CREAT TAB STRIP CONTROL AND SUB SCREEN USEING SELECTION-SCREEN?
first i have to create selection-screen and after entering the values in this and execute i have to generate the tabstrip in sub screen .so help me please.
do u have example code please send me
WITH WARM REGARDS.
KHADAR.

yes u can create it.
This is a sample program to create a tabstrip.
SELECTION-SCREEN BEGIN OF SCREEN 500 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-010.
PARAMETERS: USER(10) TYPE c,
            PWD(10) TYPE c.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN END OF SCREEN 500.
SELECTION-SCREEN BEGIN OF SCREEN 600 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-010.
PARAMETERS: BUSNO(10) TYPE c,
            BUSNAME(10) TYPE c.
SELECTION-SCREEN END OF BLOCK b2.
SELECTION-SCREEN END OF SCREEN 600.
SELECTION-SCREEN BEGIN OF SCREEN 700 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE text-010.
PARAMETERS: TNO(10) TYPE c,
            TNAME(10) TYPE c.
SELECTION-SCREEN END OF BLOCK b3.
SELECTION-SCREEN END OF SCREEN 700.
SELECTION-SCREEN: BEGIN OF TABBED BLOCK sub FOR 10 LINES,
                    TAB (10) LOGIN USER-COMMAND LOGIN,
                    TAB (10) BUS USER-COMMAND BUS,
                    TAB (10) TRAIN USER-COMMAND TR,
                  END OF BLOCK sub.
INITIALIZATION.
LOGIN = 'LOGIN'.
BUS = 'BUS'.
TRAIN = 'TRAIN'.
SUB-DYNNR = 500.
SUB-PROG = SY-REPID.
AT SELECTION-SCREEN.
CASE SY-UCOMM                  .
WHEN 'LOGIN'.
     SUB-DYNNR = 500.
WHEN 'BUS'.
     SUB-DYNNR = 600.
WHEN 'TR'.
     SUB-DYNNR = 700.
ENDCASE.

TABLE CONTROL IN TAB STRIP CONTROL

hi experts,
I have a problem with table control in tab strip control i have table control in first tab
and some text fields in second tab .
i enter data into table control in first tab and enter into second tab and i fill data into second tab also .
then i press save after filling data into these two tabs at that time table control data is not updating into corresponding table ,Because when the time we enter into second tab data in table control is cleared .
please give me a solution for this problem as early as possible.
Note : saving data is done after filling two tabs only.
Regards,
k.Rajesh.

Hi,
go through this code,
DIALOG PROGRAMMING
TABSTRIPS
IN SE51 FLOW LOGIC MAIN SCREEN
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN PER_REF1 INCLUDING 'YMODULE_PR8' '0200'.
CALL SUBSCREEN SALE_REF1 INCLUDING 'YMODULE_PR8' '0300'.
MODULE STATUS_0100.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0100.
IN SE51 FLOW LOGIC FOR SCREEN 200. 1st TAB IN SUBSCREEN AREA.
PROCESS BEFORE OUTPUT.
MODULE STATUS_0200.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0200.
IN SE51 FLOW LOGIC FOR SCREEN 300. 2nd TAB IN SUBSCREEN AREA.
PROCESS BEFORE OUTPUT.
LOOP AT ITVBAK WITH CONTROL TABCTRL.
MODULE STATUS_0300.
ENDLOOP.
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0300.
LOOP AT ITVBAK.
ENDLOOP.
IN FLOW LOGIN OF MAIN SCREEN
PROGRAM YMODULE_PR8 .
TABLES : KNA1, VBAK.
DATA : BEGIN OF ITVBAK OCCURS 0,
       VBELN LIKE VBAK-VBELN,
       ERDAT LIKE VBAK-ERDAT,
       ERNAM LIKE VBAK-ERNAM,
       NETWR LIKE VBAK-NETWR,
       END OF ITVBAK.
CONTROLS : TABCTRL TYPE TABLEVIEW USING SCREEN 300,
                        TABSTRIP1 TYPE TABSTRIP.
*&      Module STATUS_0300 OUTPUT
MODULE STATUS_0300 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
MOVE-CORRESPONDING ITVBAK TO VBAK.
ENDMODULE.                 " STATUS_0300 OUTPUT
*&      Module USER_COMMAND_0100 INPUT
MODULE USER_COMMAND_0100 INPUT.
CASE SY-UCOMM.
WHEN 'EXIT'.
    LEAVE PROGRAM.
WHEN 'PERSONAL' OR SPACE.
    SELECT * FROM KNA1
     WHERE KUNNR = KNA1-KUNNR.
    ENDSELECT.
    TABSTRIP1-ACTIVETAB = 'PERSONAL'. ## TO ACTIVATE TABSTRIP & MAKE IT
FUNCTIONAL
WHEN 'SALES'.
    SELECT VBELN ERDAT ERNAM NETWR
      FROM VBAK
      INTO TABLE ITVBAK
     WHERE KUNNR = KNA1-KUNNR.
    DESCRIBE TABLE ITVBAK LINES TABCTRL-LINES.
    TABSTRIP1-ACTIVETAB = 'SALES'. ## TO ACTIVATE TABSTRIP & MAKE IT
FUNCTIONAL
ENDCASE.
ENDMODULE.                 " USER_COMMAND_0100
reward if usefull

When opening a new tab , press control plus T CTrl+T,, why is it blank page, how ca i set it to be on yahoo or google

when opening a new tab , press control plus T CTrl+T,, why is it blank page, how ca i set it to be on yahoo or google

There are other things that need your attention.
Your above posted system details show outdated plugin(s) with known security and stability risks that you should update.
*Shockwave Flash 10.1 r53
See:
*http://www.mozilla.com/plugincheck/
Update the Flash plugin to the latest version.
*https://support.mozilla.com/kb/Managing+the+Flash+plugin
*http://kb.mozillazine.org/Flash
*http://www.adobe.com/software/flash/about/
Update the Adobe Reader plugin to the latest version.
*https://support.mozilla.com/kb/Using+the+Adobe+Reader+plugin+with+Firefox
*http://kb.mozillazine.org/Adobe_Reader
*http://get.adobe.com/reader/otherversions/

Does tab strip control work in LSMW

does tab strip control work in LSMW or not if yes give me a scenario

Yes it does,
The trick is uto use transaction SHDB to record the transaction that you are trying to use and then convert this to a program. From here you can add the logic into your ABAP.
Tab strip sontrol also works in LSMW.
Regards
Jules

General Tab in Control

Dear Experts,
Can anyone please tell the purpose of fields " Testing Technique" & "Operation Frequency" in general tab of Control.
Thanks!
With regards,
Shyam

Hi Shyam,
These fields are information about the characteristics of the control. They don't imply on restriction in the moment of test.
Testing Technique – This field has the purpose of to inform how the test will be done, like: will be done interview? Will be done re-execution of the control? Will be done document analysis?
Operation Frequency – This field informs what is the frequency, period of time, of the execution of the control, like: annually, daily, monthly, etc.
Best regards,
Evanir

Creation of Tab Strips controls

Hi Gy's ,
pelase help me how to create the Tab Stip control in Sceen Painter(se51) step-by- step procedure.
Thanks,
sai.

hi,
A tabstrip control is a screen object consisting of two or more pages. Each tab page consists of a tab title and a page area. If the area occupied by the tabstrip control is too narrow to display all of the tab titles, a scrollbar appears, allowing you to reach the titles that are not displayed. There is also a pushbutton that allows you to display a list of all tab titles.
Tabstrip controls allow you to place a series of screens belonging to an application on a single screen, and to navigate between them easily. The recommended uses and ergonomic considerations for tabstrip controls are described in the Tabstrip Control section of the SAP Style Guide.
From a technical point of view, a tab page is a subscreen with a pushbutton assigned to it, which is displayed as the tab title.
The tabstrip control is the set of all the tab pages. Tabstrip controls are therefore subject to the same restrictions as subscreens. In particular, you cannot change the GUI status when you switch between pages in the tabstrip control. However, they are fully integrated into the screen environment, so present no problems with batch input.
To use a tabstrip control on a screen, you must be using a SAPgui with Release 4.0 or higher, and its operating system must be Motif, Windows 95, MacOS, or Windows NT with version 3.51 or higher.
When you create a tabstrip control, you must:
Define the tab area on a screen and the tab titles.
Assign a subscreen area to each tab title.
Program the screen flow logic.
Program the ABAP processing logic.
You must then decide whether you want to page through the tabstrip control at the SAPgui or on the application server. In the first case, each tab page has its own subscreen. In the second, there is a single subscreen area that is shared by all tab pages.
Defining the Tabstrip Control Area and Tab Titles
You define both the tabstrip area and the tab titles in the screen layout.
The tabstrip area has a unique name and a position, length, and height. You can also specify whether the tabstrip area can be resized vertically or horizontally when the user resizes the window. If the area supports resizing, you can specify a minimum size for it.
When you define a tabstrip area, it already has two tab titles. Tab titles are technically exactly the same as pushbuttons. To create additional tab titles, simple create pushbuttons in the row containing the tab titles. Tab titles have the same attributes as pushbuttons, that is, each has a name, a text, and a function code. You can also use icons and dynamic texts with tab titles.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
Paging on the Application Server
One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN: <area1> INCLUDING <prog 1> <dynp 1>,
<area2> INCLUDING <prog 2> <dynp 2>,
<area3> INCLUDING <prog 3> <dynp 3>,
PROCESS AFTER INPUT.
CALL SUBSCREEN: <area1>,
<area2>,
<area3>,
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING <prog> <dynp>.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
Examples
Tabstrip control, paging at SAPgui
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
SAVE_OK TYPE SY-UCOMM.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
MYTABSTRIP-ACTIVETAB.
ENDIF.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code OK.
In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',
SUB2 INCLUDING SY-REPID '0120',
SUB3 INCLUDING SY-REPID '0130'.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN: SUB1,
SUB2,
SUB3.
MODULE USER_COMMAND.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.
When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.
Tabstrip control with paging on the application server.
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
SAVE_OK TYPE SY-UCOMM.
DATA NUMBER TYPE SY-DYNNR.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
NUMBER = '0120'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
MYTABSTRIP-ACTIVETAB.
ELSE.
MYTABSTRIP-ACTIVETAB = SAVE_OK.
CASE SAVE_OK.
WHEN 'PUSH1'.
NUMBER = '0110'.
WHEN 'PUSH2'.
NUMBER = '0120'.
WHEN 'PUSH3'.
NUMBER = '0130'.
ENDCASE.
ENDIF.
ENDMODULE.
The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.
The same subscreen screens 110 to 130 are defined as in the last example.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control.
refer the following sites for reference--
http://www.saptechies.com/difference-bw-tabstrip-and-table-control/
http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbac1d35c111d1829f0000e829fbfe/content.htm
Regards,
sravanthi

About tab strip control

Could anyone tell me the usage of tab strip controls in REUSE_ALV_GRID_DISPLAY. The IS_LAYOUT has parameters called dtc_layout type dtc_s_layo. What exactly would be the use of this, if anybody has worked on this?
Regards,
Vijay

Hi Vijay,
fro better understabding read the FM documentation,
in that they explained it very well about IS_LAYOUT.
IS_LAYOUT
Output list description structure.
The parameters are described under the following headers:
Display options
Exceptions
Totals
Interaction
Detail screen
Display variants (only for hierarchical-sequential lists)
Color
Other
Note the section 'Default'.
Regards
vijay

Dynamic Tab Access Control?

Is there a way to set up dynamic tab access control? For instance if I wanted a professor to only have Shared access to a particular tab in a course page is there a way to define the credential to indicate which tab they should have access to?
Thanks,
Jason

Is there a way to set up dynamic tab access control?
For instance if I wanted a professor to only have
Shared access to a particular tab in a course page
is there a way to define the credential to indicate
which tab they should have access to?
I haven't tried this, but I think you could create a new course template that uses the instructor and student roles, and set the access control option in that to allow an instructor shared access to a given tab. New courses based on that template would use the same permissions. I don't think there's any need to include access control information in the credential itself (as the credential is just used for authentication; iTunes U itself decides what you get to).
Or am I missing something in your question?
Ken

Tab and control buttons do not work in Firefox (they work in other browsers) AND I switched to a new keyboard.

The tab and control buttons are not working the Firefox browser (My browser is up-to-date). The buttons work in IE and Chrome, however, before I realized that, I even switched out my keyboard to a brand new one hoping it would solve the issue.

Thank you--there were a few random extensions I had not added (spyware, maybe?). Once I removed those the issue was fixed!

MSI Clock & Information Tabs In Control Panel\Display do not open

I can't open the MSI Information tab and the MSI Clock tab in Control Panel\Display; keep getting the message that "an error occured while trying to run shell32.dll, control-rundll C:\Windows\system32\desk.cpl, display". Other than this, everything else is working perfectly. Any suggestions?

I would also recommend a 3rd party solution. On my 845PE with a GEForce3 Ti200 (MS8851), the system will reboot becuase of drivers problems (XP Pro) when accessing advanced page if I use the MSI controls.
Remoing the controls solves the issue.

Creation of Tab Strips control

Hi Guy's,
Please help me How to create the Tacbstript control in Screen painter(SE51) step-by-step procedure.
Thanks,
Sai

Hi,
Very good docu....
Tabstrip Controls
A tabstrip control is a screen object consisting of two or more pages. Each tab page consists of a tab title and a page area. If the area occupied by the tabstrip control is too narrow to display all of the tab titles, a scrollbar appears, allowing you to reach the titles that are not displayed. There is also a pushbutton that allows you to display a list of all tab titles.
Tabstrip controls allow you to place a series of screens belonging to an application on a single screen, and to navigate between them easily. The recommended uses and ergonomic considerations for tabstrip controls are described in the Tabstrip Control section of the SAP Style Guide.
From a technical point of view, a tab page is a subscreen with a pushbutton assigned to it, which is displayed as the tab title.
The tabstrip control is the set of all the tab pages. Tabstrip controls are therefore subject to the same restrictions as subscreens. In particular, you cannot change the GUI status when you switch between pages in the tabstrip control. However, they are fully integrated into the screen environment, so present no problems with batch input.
To use a tabstrip control on a screen, you must be using a SAPgui with Release 4.0 or higher, and its operating system must be Motif, Windows 95, MacOS, or Windows NT with version 3.51 or higher.
When you create a tabstrip control, you must:
Define the tab area on a screen and the tab titles.
Assign a subscreen area to each tab title.
Program the screen flow logic.
Program the ABAP processing logic.
You must then decide whether you want to page through the tabstrip control at the SAPgui or on the application server. In the first case, each tab page has its own subscreen. In the second, there is a single subscreen area that is shared by all tab pages.
Defining the Tabstrip Control Area and Tab Titles
You define both the tabstrip area and the tab titles in the screen layout.
The tabstrip area has a unique name and a position, length, and height. You can also specify whether the tabstrip area can be resized vertically or horizontally when the user resizes the window. If the area supports resizing, you can specify a minimum size for it.
When you define a tabstrip area, it already has two tab titles. Tab titles are technically exactly the same as pushbuttons. To create additional tab titles, simple create pushbuttons in the row containing the tab titles. Tab titles have the same attributes as pushbuttons, that is, each has a name, a text, and a function code. You can also use icons and dynamic texts with tab titles.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
Paging on the Application Server
One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>,
                  <area2> INCLUDING [<prog 2>] <dynp 2>,
                  <area3> INCLUDING [<prog 3>] <dynp 3>,
PROCESS AFTER INPUT.
CALL SUBSCREEN: <area1>,
                  <area2>,
                  <area3>,
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>.
PROCESS AFTER INPUT.
CALL SUBSCREEN <area>.
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
Examples
Tabstrip control, paging at SAPgui
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
      SAVE_OK TYPE SY-UCOMM.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
    MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
                                  MYTABSTRIP-ACTIVETAB.
ENDIF.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code OK.
In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',
                  SUB2 INCLUDING SY-REPID '0120',
                  SUB3 INCLUDING SY-REPID '0130'.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN: SUB1,
                  SUB2,
                  SUB3.
MODULE USER_COMMAND.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.
When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.
Tabstrip control with paging on the application server.
REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
CONTROLS MYTABSTRIP TYPE TABSTRIP.
DATA: OK_CODE TYPE SY-UCOMM,
      SAVE_OK TYPE SY-UCOMM.
DATA NUMBER TYPE SY-DYNNR.
MYTABSTRIP-ACTIVETAB = 'PUSH2'.
NUMBER = '0120'.
CALL SCREEN 100.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE USER_COMMAND INPUT.
SAVE_OK = OK_CODE.
CLEAR OK_CODE.
IF SAVE_OK = 'OK'.
    MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='
                                  MYTABSTRIP-ACTIVETAB.
ELSE.
    MYTABSTRIP-ACTIVETAB = SAVE_OK.
    CASE SAVE_OK.
      WHEN 'PUSH1'.
        NUMBER = '0110'.
      WHEN 'PUSH2'.
        NUMBER = '0120'.
      WHEN 'PUSH3'.
        NUMBER = '0130'.
    ENDCASE.
ENDIF.
ENDMODULE.
The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.
The same subscreen screens 110 to 130 are defined as in the last example.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.
The screen flow logic of subscreens 110 to 130 does not contain any module calls.
This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control.
Pls. reward if useful...

Tab in control

Similar Messages

Maybe you are looking for