Layout Positioning

hi again :)
so now i have Flex at work and at home... however, for some
reason (at work), i dont have the "layout propery"(where there are
check boexes and you can align things the way you want to) in my
"Flex properties"..
also, everything is just on one panel, no accordion, like i
have at home.
did i do something wrong? am i missing aplugin?
how does your Flex look?
help me fix it please.
Thanks!

I think I got it after numerous tries. See
http://www.indianaeagleforum.org/contact_join.html

Similar Messages

Get layout-position of a component

Hi!
i have a frame applcation with two toolbars.
they can both be dragged to a new position in the borderlayout with the mouse. it was'nt easy to have no problems with the layout-manager when they are set to a new position.
now i want so save the alignment of the toolbars for the next start of the application.
how do i get the current alignment of a toolbar?
the toolbar is an attribute of the class, i know the panel, and that is no other component in the north, south, east or west.
for example the best thing would be to retrieve
String layoutPosition = toolbarPanel.whereTheHellIsTheToolbar(toolbar);
(e.g. "BorderLayout.SOUTH")
to serialize this string and to initialize at the next start
add(toolbar, layoutPosition);
thanks for any help in advance.
Rainer

Not sure, but this thread might help:
http://forum.java.sun.com/thread.jsp?forum=57&thread=340326

Gridbag layout positions

Hello, I am creating a gui with various swing objects. I put a grouping of various objects within some panels as to allow for simpler layout. The problem however is spaning a jpanel over 2 rows.
basically i want one panel on the left that spans 2 rows, and two panels that span one row each but are placed horizontally to the first panel. followed by 3 panels places horizontally on a 3rd row. when i try to set gridheigh=2 i get weirdness
package javaiq3;
/** Iq3GUI.java
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class Iq3GUI extends JFrame implements ActionListener{
/* main window essential objects */
protected JFrame frame; // main window
private JPanel panel; // content panel for main window
private GridBagLayout gridbag = new GridBagLayout(); // layout object for main window
   * constructor
   * @param title Main window title
public Iq3GUI(String title){
    //initializes the main window, its layout and panels
    frame = new JFrame(title); // initializes main window
    frame.addWindowListener(new WindowAdapter() { // window listener
      // exits program when window is closed
      public void windowClosing(WindowEvent e) {System.exit(0);}
    GridBagConstraints c = new GridBagConstraints(); // constraints
    GridBagConstraints subc = new GridBagConstraints(); // constraints
    panel = new JPanel();
    panel.setLayout(gridbag);
    setLookAndFeel("com.sun.java.swing.plaf.windows.WindowsLookAndFeel");
/**** menu bar ****/
    JMenuBar menuBar = new JMenuBar();
    frame.setJMenuBar(menuBar);
    JMenu menu = new JMenu("File");
    menu.setMnemonic(KeyEvent.VK_F);
    menu.getAccessibleContext().setAccessibleDescription("File menu");
    menuBar.add(menu);
/**** end: menu bar ****/
/**** type radio buttons ****/
    JRadioButton[] typeRButton = new JRadioButton[2];
    typeRButton[0]=new JRadioButton("Life");
    typeRButton[1]=new JRadioButton("Crit");
    JPanel typeRButtonPanel = new JPanel(); // panel for radio buttons
    typeRButtonPanel.setLayout(new BorderLayout());
    typeRButtonPanel.setBorder(BorderFactory.createTitledBorder("Type:")); // sets border
    ButtonGroup typeGroup = new ButtonGroup(); // radio button group
    for(int x=0;x<typeRButton.length;x++){ // groups radio buttons together
        typeGroup.add(typeRButton[x]);
    typeRButtonPanel.add(typeRButton[0],BorderLayout.CENTER); // adds them to panel
    typeRButtonPanel.add(typeRButton[1],BorderLayout.SOUTH);
    c.insets = new Insets(15,15,0,0);
    c.gridx=0; c.gridy=0; c.ipady=0; c.gridwidth=1; gridbag.setConstraints(typeRButtonPanel, c);
    panel.add(typeRButtonPanel); // adds radio button panel to main panel
/**** end: type radio buttons ****/
/**** company combo box ****/
    JComboBox companyComboBox = new JComboBox();
    JPanel companyComboBoxPanel = new JPanel();
    companyComboBox.setPreferredSize(new Dimension(300,18));
    companyComboBoxPanel.setLayout(gridbag);
    subc.insets = new Insets(-2,5,2,5); gridbag.setConstraints(companyComboBox, subc);
    companyComboBoxPanel.setBorder(BorderFactory.createTitledBorder("Company:"));
    companyComboBoxPanel.add(companyComboBox);
    c.insets = new Insets(0,0,0,0);
    c.gridx=1; c.gridy=0; c.ipadx=0; gridbag.setConstraints(companyComboBoxPanel, c);
    panel.add(companyComboBoxPanel);
/**** end: company combo box ****/
/**** product combo box ****/
    JComboBox productComboBox = new JComboBox();
    JPanel productComboBoxPanel = new JPanel();
    productComboBox.setPreferredSize(new Dimension(300,18));
    productComboBoxPanel.setLayout(gridbag);
    subc.insets = new Insets(-2,5,2,5); gridbag.setConstraints(productComboBox, subc);
    productComboBoxPanel.setBorder(BorderFactory.createTitledBorder("Product:"));
    productComboBoxPanel.add(productComboBox);
    c.insets = new Insets(0,0,0,0);
    c.gridx=1; c.gridy=2; c.ipady=0; gridbag.setConstraints(productComboBoxPanel, c);
    panel.add(productComboBoxPanel);
/**** end: product combo box ****/
/**** type sex radio buttons ****/
    JRadioButton[] sexRButton = new JRadioButton[2];
    sexRButton[0]=new JRadioButton("Male");
    sexRButton[1]=new JRadioButton("Female");
    JPanel sexRButtonPanel = new JPanel(); // panel for radio buttons
    sexRButtonPanel.setLayout(new BorderLayout());
    sexRButtonPanel.setBorder(BorderFactory.createTitledBorder("Sex:")); // sets border
    ButtonGroup sexGroup = new ButtonGroup(); // radio button group
    for(int x=0;x<sexRButton.length;x++){ // groups radio buttons together
        sexGroup.add(sexRButton[x]);
     sexRButtonPanel.add(sexRButton[0],BorderLayout.CENTER); // adds them to panel
     sexRButtonPanel.add(sexRButton[1],BorderLayout.SOUTH);
     c.gridx=0; c.gridy=3; c.ipady=0; gridbag.setConstraints(sexRButtonPanel, c);
     panel.add(sexRButtonPanel); // adds radio button panel to main panel
/**** end: sex radio buttons ****/
/**** smoker check box/combo box ****/
    JCheckBox smokerRButton = new JCheckBox("No");
    JComboBox smokerComboBox = new JComboBox();
    smokerComboBox.setPreferredSize(new Dimension(100,18));
    JPanel smokerPanel = new JPanel();
    smokerPanel.setLayout(new BorderLayout());
    smokerPanel.setBorder(BorderFactory.createTitledBorder("Smoker:"));
    smokerPanel.add(smokerRButton,BorderLayout.CENTER);
    smokerPanel.add(smokerComboBox,BorderLayout.SOUTH);
    c.gridx=1; c.gridy=3; c.ipady=0; gridbag.setConstraints(smokerPanel, c);
    panel.add(smokerPanel);
/**** end: smoker check box/combo box ****/
/**** waiver radio buttons ****/
    JRadioButton[] waiverRButton = new JRadioButton[2];
    waiverRButton[0]=new JRadioButton("Yes");
    waiverRButton[1]=new JRadioButton("No");
    JPanel waiverRButtonPanel = new JPanel(); // panel for radio buttons
    waiverRButtonPanel.setLayout(new BorderLayout());
    waiverRButtonPanel.setBorder(BorderFactory.createTitledBorder("Waiver:")); // sets border
    ButtonGroup waiverGroup = new ButtonGroup(); // radio button group
    for(int x=0;x<waiverRButton.length;x++){ // groups radio buttons together
        waiverGroup.add(waiverRButton[x]);
     waiverRButtonPanel.add(waiverRButton[0],BorderLayout.CENTER); // adds them to panel
     waiverRButtonPanel.add(waiverRButton[1],BorderLayout.SOUTH);
     c.gridx=2; c.gridy=3; c.ipady=0; gridbag.setConstraints(waiverRButtonPanel, c);
     panel.add(waiverRButtonPanel); // adds radio button panel to main panel
/**** end: type radio buttons ****/
/**** main gui properties ****/
// Dimension screenDim = Toolkit.getDefaultToolkit().getScreenSize(); //screen dimensions
// Rectangle frameDim = frame.getBounds(); // frame boundries
// frame.setLocation((screenDim.width - frameDim.width) / 4,(screenDim.height - frameDim.height) / 4);//sets frame's location to center screen
// frame.setSize(600,100);
    frame.setContentPane(panel); frame.pack();
    frame.setVisible(true);
/**** end: main gui properties ****/
   * setLookAndFeel
   * Sets the look and feel of the application, if it cannot be set to the
   * user defined one, sets the default java
   * @param feel Stores the look and feel string
public void setLookAndFeel(String feel){
     try { // sets the GUI style to the parameter type
          UIManager.setLookAndFeel(feel);
      } catch (Exception e) {
         try{
           UIManager.setLookAndFeel(UIManager.getCrossPlatformLookAndFeelClassName());
         catch (Exception e2){ // if default java one cannot be set, exits program
            System.err.println(e2.getMessage());
            System.exit(0);
   * errorBox
   * Displays a JDialog box with an ok button, programmer defined message
   * and a warning icon
   * @param message Programmer defined message
public void errorBox(String message){
    JOptionPane.showMessageDialog(frame,message,"Error",JOptionPane.ERROR_MESSAGE);
    System.exit(0);
* actionPerformed
* Performs action sent to by action listener
* @param e Action object
public void actionPerformed(ActionEvent e){
    System.out.println("Click");
* Main
* Test method
* @param args Does nothing
public static void main(String[] args){
    Iq3GUI heh = new Iq3GUI("IQ3");
}

Wow. That's some ugly code. You might want to work on coding conventions a bit.
The reason books provide information in paragraphs is to give the eye a rest and the brain time to process the information (a brain is only 8 MHz -- no kidding). Your code should do the same. If 80% of effort goes into maintaining code, you'll help yourself (and potential coworkers) by coding neatly so that things are easy to understand at a glance without dealing with a lot of visual clutter.
1) Try to put comments on their own lines instead of whacking them onto the end of a line of code.
2) Include spaces between code segments that are related tasks -- think of them as "virtual blocks" (since they're not enclosed in braces). Think about the paragraph analogy again. A paragraph groups related sentences. Let your code do the same.
3) Never, ever jam multiple statements into a single line of code. It's a huge pain in the ass to read. While the compiler doesn't care about whitespace, human beings do.
4) When working with GridBagLayout, add all your components in the same part of your class file. By doing so, when you need to alter the layout, you don't have to dig through all of your code to find bits and pieces of the layout. Your project is small, but if you do this stuff for a living, you're eventually going to work on gigantic projects. My current project, for example, consists of 20,000 lines of code just for the GUI (and my project isn't even all at big).
5) Exiting a program without telling the user is laaaaame. I know you're just playing around, but now's the time to get good habits.
OK, so now that you've sat through the editorial, the quick and dirty answer is that you have to explicitly specify widths and heights in your constrains for each component, otherwise GridBagLayout's behavior becomes hard to predict.
In your code, you specify gridwidth once and never again. You know that a Constraint object is reusable, right? What you've just told GridBagLayout is "try to make everything the same width." Meanwhile, the layout is trying to respect your preferred sizes.
Please read the Java Tutorial on GridBagLayout, particularly the suggestion to sketch your layout on a piece of paper ahead of time so that you remember which constraint attributes to change. For safe measure, you might want to specify an entire set of constraints each time you lay out a component so that you won't leave out something important.
As for the background color, I just fixed it by setting a background for your main panel. Windows look and feel is lame, I guess. I always use the Java look and feel, so I haven't run into your problem before.
See my modified code below.
//package javaiq3;
/** Iq3GUI.java
import javax.swing.*;
import java.awt.*;
import java.awt.event.*;
public class Iq3GUI extends JFrame implements ActionListener
    protected JFrame frame;
    private JPanel panel;
    private GridBagLayout gridbag = new GridBagLayout();
    public Iq3GUI(String title)
        frame = new JFrame(title);
        frame.addWindowListener(new WindowAdapter()
            public void windowClosing(WindowEvent e)
                System.exit(0);
        GridBagConstraints c = new GridBagConstraints();
        GridBagConstraints subc = new GridBagConstraints();
        panel = new JPanel();
        panel.setLayout(gridbag);
        panel.setBackground(Color.lightGray);
        setLookAndFeel("com.sun.java.swing.plaf.windows.WindowsLookAndFeel");
        JMenuBar menuBar = new JMenuBar();
        frame.setJMenuBar(menuBar);
        JMenu menu = new JMenu("File");
        menu.setMnemonic(KeyEvent.VK_F);
        menu.getAccessibleContext().setAccessibleDescription("File menu");
        menuBar.add(menu);
        JRadioButton[] typeRButton = new JRadioButton[2];
        typeRButton[0]=new JRadioButton("Life");
        typeRButton[1]=new JRadioButton("Crit");
        JPanel typeRButtonPanel = new JPanel();
        typeRButtonPanel.setLayout(new BorderLayout());
        typeRButtonPanel.setBorder(BorderFactory.createTitledBorder("Type:"));
        ButtonGroup typeGroup = new ButtonGroup();
        for(int x=0;x<typeRButton.length;x++)
            typeGroup.add(typeRButton[x]);
        typeRButtonPanel.add(typeRButton[0],BorderLayout.CENTER);
        typeRButtonPanel.add(typeRButton[1],BorderLayout.SOUTH);
        c.insets = new Insets(15,15,0,0);
        c.gridx=0;
        c.gridy=0;
        c.ipady=0;
        c.gridwidth=1;
        gridbag.setConstraints(typeRButtonPanel,c);
        panel.add(typeRButtonPanel);
        JComboBox companyComboBox = new JComboBox();
        JPanel companyComboBoxPanel = new JPanel();
        companyComboBox.setPreferredSize(new Dimension(300,18));
        companyComboBoxPanel.setLayout(gridbag);
        subc.insets = new Insets(-2,5,2,5);
        gridbag.setConstraints(companyComboBox, subc);
        companyComboBoxPanel.setBorder(BorderFactory.createTitledBorder("Company:"));
        companyComboBoxPanel.add(companyComboBox);
        c.insets = new Insets(0,0,0,0);
        c.gridx=1;
        c.gridy=0;
        c.ipadx=0;
        gridbag.setConstraints(companyComboBoxPanel, c);
        panel.add(companyComboBoxPanel);
        JComboBox productComboBox = new JComboBox();
        JPanel productComboBoxPanel = new JPanel();
        productComboBox.setPreferredSize(new Dimension(300,18));
        productComboBoxPanel.setLayout(gridbag);
        subc.insets = new Insets(-2,5,2,5);
        gridbag.setConstraints(productComboBox, subc);
        productComboBoxPanel.setBorder(BorderFactory.createTitledBorder("Product:"));
        productComboBoxPanel.add(productComboBox);
        c.insets = new Insets(0,0,0,0);
        c.gridx=1; c.gridy=2; c.ipady=0;
        gridbag.setConstraints(productComboBoxPanel, c);
        panel.add(productComboBoxPanel);
        JRadioButton[] sexRButton = new JRadioButton[2];
        sexRButton[0]=new JRadioButton("Male");
        sexRButton[1]=new JRadioButton("Female");
        JPanel sexRButtonPanel = new JPanel();
        sexRButtonPanel.setLayout(new BorderLayout());
        sexRButtonPanel.setBorder(BorderFactory.createTitledBorder("Sex:"));
        ButtonGroup sexGroup = new ButtonGroup();
        for(int x=0;x<sexRButton.length;x++)
            sexGroup.add(sexRButton[x]);
        sexRButtonPanel.add(sexRButton[0],BorderLayout.CENTER);
        sexRButtonPanel.add(sexRButton[1],BorderLayout.SOUTH);
        c.gridx=0;
        c.gridy=3;
        c.ipady=0;
        gridbag.setConstraints(sexRButtonPanel,c);
        panel.add(sexRButtonPanel);
        JCheckBox smokerRButton = new JCheckBox("No");
        JComboBox smokerComboBox = new JComboBox();
        smokerComboBox.setPreferredSize(new Dimension(100,18));
        JPanel smokerPanel = new JPanel();
        smokerPanel.setLayout(new BorderLayout());
        smokerPanel.setBorder(BorderFactory.createTitledBorder("Smoker:"));
        smokerPanel.add(smokerRButton,BorderLayout.CENTER);
        smokerPanel.add(smokerComboBox,BorderLayout.SOUTH);
        c.gridx=1;
        c.gridy=3;
        c.ipady=0;
        gridbag.setConstraints(smokerPanel,c);
        panel.add(smokerPanel);
        JRadioButton[] waiverRButton = new JRadioButton[2];
        waiverRButton[0]=new JRadioButton("Yes");
        waiverRButton[1]=new JRadioButton("No");
        JPanel waiverRButtonPanel = new JPanel();
        waiverRButtonPanel.setLayout(new BorderLayout());
        waiverRButtonPanel.setBorder(BorderFactory.createTitledBorder("Waiver:"));
        ButtonGroup waiverGroup = new ButtonGroup();
        for(int x=0;x<waiverRButton.length;x++)
            waiverGroup.add(waiverRButton[x]);
        waiverRButtonPanel.add(waiverRButton[0],BorderLayout.CENTER);
        waiverRButtonPanel.add(waiverRButton[1],BorderLayout.SOUTH);
        c.gridx=2;
        c.gridy=3;
        c.ipady=0;
        gridbag.setConstraints(waiverRButtonPanel,c);
        c.fill = GridBagConstraints.HORIZONTAL;
        c.gridx = 0;
        c.gridy = 0;
        c.gridwidth = 1;
        c.gridheight = 2;
        //c.weightx = 100;
        //c.weighty = 100;
        c.insets = new Insets(0,0,0,0);
        panel.add(typeRButtonPanel, c);
        c.fill = GridBagConstraints.HORIZONTAL;
        c.gridx = 1;
        c.gridy = 0;
        c.gridwidth = 2;
        c.gridheight = 1;
        //c.weightx = 100;
        //c.weighty = 100;
        c.insets = new Insets(0,0,0,0);
        panel.add(companyComboBoxPanel, c);
        c.fill = GridBagConstraints.HORIZONTAL;
        c.gridx = 1;
        c.gridy = 1;
        c.gridwidth = 2;
        c.gridheight = 1;
        //c.weightx = 100;
        //c.weighty = 100;
        c.insets = new Insets(0,0,0,0);
        panel.add(productComboBoxPanel, c);
        c.fill = GridBagConstraints.HORIZONTAL;
        c.gridx = 0;
        c.gridy = 3;
        c.gridwidth = 1;
        c.gridheight = 2;
        //c.weightx = 100;
        //c.weighty = 100;
        c.insets = new Insets(0,0,0,0);
        panel.add(sexRButtonPanel, c);
        c.fill = GridBagConstraints.HORIZONTAL;
        c.gridx = 1;
        c.gridy = 3;
        c.gridwidth = 1;
        c.gridheight = 2;
        //c.weightx = 100;
        //c.weighty = 100;
        c.insets = new Insets(0,0,0,0);
        panel.add(smokerPanel, c);
        c.fill = GridBagConstraints.HORIZONTAL;
        c.gridx = 2;
        c.gridy = 3;
        c.gridwidth = 1;
        c.gridheight = 2;
        //c.weightx = 100;
        //c.weighty = 100;
        c.insets = new Insets(0,0,0,0);
        panel.add(waiverRButtonPanel, c);
        frame.setContentPane(panel);
        frame.pack();
        frame.setVisible(true);
    public void setLookAndFeel(String feel)
        try
            UIManager.setLookAndFeel(feel);
        catch(Exception e)
            try
                UIManager.setLookAndFeel(UIManager.getCrossPlatformLookAndFeelClassName());
            catch(Exception e2)
                System.err.println(e2.getMessage());
                System.exit(0);
    public void errorBox(String message)
        JOptionPane.showMessageDialog(frame,message,"Error",JOptionPane.ERROR_MESSAGE);
        System.exit(0);
    public void actionPerformed(ActionEvent e)
        System.out.println("Click");
    public static void main(String[] args)
        Iq3GUI heh = new Iq3GUI("IQ3");
}

Keep layout position when using Find/Change?

When using Find/Change in InDesign CS4, each occurrence of the "Found" material is centered in the window, so the page moves around with each find. Is there a way to keep the page in a fixed position when searching through a document?

Actually, I can think of a shortcut for the hard part: The user uses the
regular find/change UI to make all their settings. Then, they run the
script, which will simply use the settings in the UI. Nice, huh! So you
could get a listBox of all the finds -- select the entry and you get
taken to the desired location. Click the "change" button and the change
is made. Here's a proof of concept:
#targetengine engine20
var myFinds = app.findText();
var w = new Window("palette");
var myList = w.add("listbox", undefined, myFinds);
var changeButton = w.add("button", undefined, "Change");
myList.onChange = gotoFound;
changeButton.onClick = makeTheChange;
w.show();
function gotoFound(){
app.select(myFinds[myList.selection.index].parentTextFrames[0].parent.parent);
app.select(myFinds[myList.selection.index]);
function makeTheChange(){
myFinds[myList.selection.index].changeText();
Obviously very rudimentary: but this does work in CS4. If the list is
too long, though, the change button will disappear off the bottom of the
screen. Also, really once the change is made, the item should be removed
from the list, but there's a bug in CS4 that makes it impossible to do
that simply, if I recall correctly (or was that only a tree list?)
Also, I have found that the only sure way of getting the entire spread
to show is as I've done it above (and it would need much more error
checking than this -- for instance, overset text).
Ariel

Div Layout positioning - borders?

Hello all,
I've slowly been tinkering away at re-making our company's website in downtime between projects. I'm a graphic designer, still getting used to DW. I've had a lot of assistance from searching topics and asking questions on these forums already. I'm pretty confident once I finish a page I can extend that practice throughout the rest of our site. I seem to be stymied at this point:
I've laid out a header and footer with site navigation and content including a "direct to products" menu. I want to place an image of our office here, as pictured:
I've learned tables are bad, and absolute positioning is bad, so I've been laying out the page using margins around divs to keep them in place. This has worked pleasingly so far in all the browers I've tested it in. You can see the margins indicated in the picture above in DW. However, when I delete the position:absolute attribute, I cannot get this div back into the "content" portion of the page (It keeps wanting to default it in or below the left menu- "homenav."
I'm assuming it's not finding a border to work against? I've put a 1px border around the left menu, but it's not working. What's more, when I do a preview in any browser, the image is gone entirely:
Here is a link to the temporary homepage:
http://www.gellerlighting.com/indextemporary.html
I appreciate any help you can give me. I'm assuming there is a CSS attribute I'm not familiar with that I have to assign to the image div, or the menu div on the left? Thanks
Dan

Amend the css for the 'homenav' <div> to exactly as shown below:
#homenav {
    float: left;
    width:210px;
    height:531px;
    background-image: url(Images/front%20page%20nav%20menu.jpg);
    margin-left: 14px;
    margin-top: 15px;
    background-repeat: no-repeat;
Next select your 'apDiv9' <div> (the one which contains your large image which you want positioned next to the left side navigation). Cut it from the code because it's in the incorrect location. Paste it directly after the closing 'homenav' </div> tag.
You can locate the closing tag for the 'homenav' container by clicking on it's tag name which will be shown along the bottom of Design View in Dreamweaver when you click your mouse anywhere inside of the <div>. Switch to code view and scroll down to the end of the highlighted section and paste back in your 'apDiv9' <div> after the highlighted section.
Then amend the 'apDiv9' css to exactly as shown below:
#apDiv9 {
float: left;
    width:535px;
    height:286px;
    margin-left: 26px;
    margin-top: 16px;
To align elements side by side you need to use the 'float' css attribute(as shown in the css above).
See those %20 characters in the path name to your background image? They are spaces in the name. Don't leave spaces. Use underscores to join up the image name like - Images/front_page_nav_menu.jpg
Best practice is also try not to set height on your <divs>. I see no reason why you should assign a height to the 'homenav' <div> and there is no reason to assign one to the 'apDiv9' <div> either.

Weird Positioning for Skinned Panel in Flex Builder 3

In the previous versions of the Flex Builder 3, even for the
Flex Builder 3 Beta Milestone 4, my custom skinned Panel component
worked fine. So I have an image skin and then I put into Flex
Builder, set the 9 slice settings, did some adjustments to the
headerHeight. And when I add a child component to the Panel
component, it will automatically be placed beneath the Panel's
title (like a VBox layout), position it inside the panel.
But now, compiling with the same files and css in the new
Flex Builder 3 final release, the Panel does not position the
children components correctly anymore. The children are still
positioned in a VBox layout but the first child started from the
point 0,0 of the Panel. So, the first child is overlapping the
Panel's title and all the children seems to go out of the Panel a
bit. This isn't what it used to be(that's to automatically position
them in the content are of the Panel component or at least within
the 9 slice middle area).
A Panel that isn't skinned at all works fine.
Is there anything I have to change or do to solve this?
Thanks.

Looks like what I am having is something close to that except
that my problem is related to the borderSkin and not the
borderStyle. But I have seen some of the comments talking about the
borderSkin problem too.
What I have done now is I use the Flex 3 public release but
copied the sdk from the previous beta version and compile with that
sdk.
It kind of resolves that panel bug problem(since I am just
using the old version) but I am sure I will be missing out any new
features that the new Flex 3 public release has.

Slide show does not work

I created a slide show. It works really well on the Prieview with a browser. Once I put it on the web it does not work. here is the code.
<%@LANGUAGE="JAVASCRIPT"
CODEPAGE="65001"%>
<!doctype html>
<html>
<head>
<meta charset="utf-8">

<title>Untitled Document</title>
<style type="text/css">
/* BeginOAWidget_Instance_2141542: #ImageSlideShow */
#ImageSlideShow.ImageSlideShow {
    width: 300px;
    height: 300px;
    border: solid 5px #000000;
#ImageSlideShow .ISSClip {
    background-color: #333333;
/* EndOAWidget_Instance_2141542 */
</style>

<style type="text/css">
#apDiv16 {
    position: absolute;
    left: 267px;
    top: 289px;
    width: 402px;
    height: 331px;
    z-index: 14;
    border: thick ridge rgb(0,0,255);
</style>
<style type="text/css">
#apDiv17 {
    position: relative;
    left: 687px;
    top: 287px;
    width: 346px;
    height: 65px;
    z-index: 15;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 18px;
    line-height: 20px;
    font-weight: bold;
    font-style: italic;
</style>
<style type="text/css">
#apDiv18 {
    position: absolute;
    left: 814px;
    top: 318px;
    width: 254px;
    height: 369px;
    z-index: 16;
    font-family: Arial, Helvetica, sans-serif;
    line-height: 3px;
    color: rgb(0,0,0);
    font-weight: bold;
#apDiv18 P FONT {
    color: rgb(0,0,0);
#apDiv18 P FONT {
    font-weight: normal;
</style>
<style type="text/css">
#apDiv19 {
    position: absolute;
    left: 301px;
    top: 280px;
    width: 426px;
    height: 328px;
    z-index: 1000;
</style>
<style type="text/css">
#apDiv20 {
    position: absolute;
    left: 314px;
    top: 319px;
    width: 437px;
    height: 312px;
    z-index: 16;
</style>
<style type="text/css">
#apDiv21 {
    position: absolute;
    left: 273px;
    top: 231px;
    width: 520px;
    height: 23px;
    z-index: 16;
    font-size: 18px;
</style>
<style type="text/css">

</style>
<link href="../SpryAssets/SpryMenuBarHorizontal.css" rel="stylesheet" type="text/css">
<style type="text/css">
#apDiv8 {
    position: absolute;
    left: 70px;
    top: 66px;
    width: 1280px;
    height: 41px;
    z-index: 8;
    font-family: Arial, Helvetica, sans-serif;
    color: #000;
    font-weight: bold;
#apDiv2 {
    position: absolute;
    left: 11px;
    top: 213px;
    width: 140px;
    height: 308px;
    z-index: 9;
</style>
<link href="../SpryAssets/SpryMenuBarVertical.css" rel="stylesheet" type="text/css">
<style type="text/css">
#apDiv3 {
    position: absolute;
    left: 302px;
    top: 321px;
    width: 654px;
    height: 466px;
    z-index: 10;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 14px;
    font-weight: bold;
    line-height: 10px;
    border-top-width: thick;
    border-top-style: solid;
    border-right-style: solid;
    border-bottom-style: solid;
    border-left-style: solid;
    border-top-color: rgb(0,51,255);
#apDiv7 {
    position: absolute;
    left: 2px;
    top: 35px;
    width: 302px;
    height: 326px;
    z-index: 7;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 16px;
    line-height: 5px;
    font-weight: normal;
    color: #666;
#apDiv9 {
    position: absolute;
    left: 270px;
    top: 302px;
    width: 382px;
    height: 295px;
    z-index: 11;
    border: thick solid rgb(0,51,255);
.style12 {font-size: 18pt}
#apDiv7 P FONT {
    color: rgb(0,0,0);
    font-family: Verdana, Geneva, sans-serif;
    font-size: 16px;
#apDiv10 {
    position: absolute;
    left: 4px;
    top: 164px;
    width: 131px;
    height: 293px;
    z-index: 999;
#apDiv11 {
    position: absolute;
    left: 670px;
    top: 298px;
    width: 268px;
    height: 61px;
    z-index: 13;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 18px;
    color: #000;
.container .content #apDiv11 P FONT {
    color: rgb(0,0,0);
#apDiv13 {
    position: absolute;
    left: 134px;
    top: 230px;
    width: 864px;
    height: 551px;
    z-index: 13;
#apDiv14 {
    position: absolute;
    left: 151px;
    top: 252px;
    width: 605px;
    height: 278px;
    z-index: 13;
#apDiv15 {
    position: absolute;
    left: 98px;
    top: 392px;
    width: 1350px;
    height: 496px;
    z-index: 13;
#apDiv16 {
    position: absolute;
    left: 339px;
    top: 249px;
    width: 724px;
    height: 37px;
    z-index: 900;
    border-bottom-width: thick;
    border-bottom-style: solid;
    border-bottom-color: rgb(255,0,0);
#apDiv17 {
    position: absolute;
    left: 50;
    top: 266px;
    width: 620px;
    height: 1;
    z-index: 13;
    background-color: #FF0000;
#apDiv22 {
    position: absolute;
    left: 132px;
    top: 50px;
    width: 40px;
    height: 46px;
    z-index: 1000;
    color: #FFF;
#apDiv23 {
    position: absolute;
    left: -103px;
    top: 340px;
    width: 800px;
    height: 3;
    z-index: 10;
    border-top-width: thick;
    border-top-style: groove;
    border-top-color: rgb(255,0,0);
#apDiv30 {
    position: absolute;
    height: 30px;
    width: 1000px;
    left: -102px;
    top: 288px;
</style>
<script src="../SpryAssets/SpryMenuBar.js" type="text/javascript"></script>

<style type="text/css">
#apDiv16 {
    position: absolute;
    left: 264px;
    top: 326px;
    width: 402px;
    height: 331px;
    z-index: 14;
    border: thick ridge rgb(0,0,255);
</style>
<style type="text/css">
#apDiv17 {
    position: absolute;
    left: 687px;
    top: 324px;
    width: 346px;
    height: 65px;
    z-index: 15;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 18px;
    line-height: 20px;
    font-weight: bold;
</style>
<style type="text/css">
#apDiv18 {
    position: absolute;
    left: 687px;
    top: 392px;
    width: 254px;
    height: 358px;
    z-index: 16;
    font-family: Verdana, Geneva, sans-serif;
    font-size: 16px;
    line-height: 0px;
</style>
<style type="text/css">
#apDiv19 {
    position: absolute;
    left: 214px;
    top: 293px;
    width: 952px;
    height: 375px;
    z-index: 101;
</style>
<style type="text/css">
#apDiv22 {
    position: absolute;
    left: 216px;
    top: 286px;
    width: 906px;
    height: 348px;
    z-index: 17;
#apDiv24 {
    position: absolute;
    left: 70px;
    top: 518px;
    width: 785px;
    height: 113px;
    z-index: 1000;
#apDiv25 {
    position: absolute;
    left: 222px;
    top: 361px;
    width: 115px;
    height: 250;
    z-index: 7;
</style>
<link href="../Spry-UI-1.7/css/SpryImageSlideShow.css" rel="stylesheet" type="text/css">
<script src="../Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryPanelSet.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryFadingPanels.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryImageLoader.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryImageSlideShow.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/plugins/ImageSlideShow/SpryPanAndZoomPlugin.js" type="text/javascript"></script>
<script type="text/xml">

</script>

</head>
<body>
<div>Content for New Div Tag Goes Here</div>
<div>Content for New Div Tag Goes Here</div>
<container class="container">
<div id="apDiv1">

<div id="apDiv25">
<ul id="ImageSlideShow">
    <li><a href="../images/bent_shank_wnuts.jpg"><img src="../images/src/bent_shank_wnuts.jpg" alt="" /></a></li>
    <li><a href="../images/champion_rivet_at_operator.JPG"><img src="../images/src/champion_rivet_at_operator.JPG" alt="" /></a></li>
    <li><a href="../images/coining.jpg"><img src="../images/src/coining.jpg" alt="" /></a></li>
    <li><a href="../images/dry_box_workers.jpg"><img src="../images/src/dry_box_workers.jpg" alt="" /></a></li>
    <li><a href="../images/laser_shlomo.jpg"><img src="../images/src/laser_shlomo.jpg" alt="" /></a></li>
<li><a href="../images/lung-blocker-white-gowns.jpg"><img src="../images/src/lung-blocker-white-gowns.jpg" alt="" /></a></li>
</ul>
<script type="text/javascript">
// BeginOAWidget_Instance_2141542: #ImageSlideShow
var ImageSlideShow = new Spry.Widget.ImageSlideShow("#ImageSlideShow", {
    widgetID: "ImageSlideShow",
    injectionType: "replace",
    autoPlay: true,
    displayInterval: 4000,
    transitionDuration: 2000,
    componentOrder: ["view", "controls"],
    plugIns: [ Spry.Widget.ImageSlideShow.PanAndZoomPlugin ]
// EndOAWidget_Instance_2141542
</script>
</div>
<div id="apDiv23"></div>

NOGAH
<div id="apDiv5">Machine Designers & Builders</div>
<div id="apDiv4">smart innovative engineering </div>
</div>

<div id="apDiv15">
<p> </p>
</div>

<div class="header"><a href="#"><img src="../images/logoN.jpg" alt="Insert Logo Here" name="Insert_logo" width="100" height="150" id="Insert_logo" style="color: #F00; text-transform: uppercase; font-size: 40px; font-family: 'Arial Black', Gadget, sans-serif; display: block;"></a>
</div>
<div class="content">
    <div id="apDiv6" style="left: 100px; top: 170px">
      <ul id="MenuBar1" class="MenuBarHorizontal">
        <li><a href="index.html">Home</a>        </li>
        <li><a href="facility.html">Our Facility</a></li>
        <li><a href="about%20us.html">About Us</a></li>
<li><a href="contact%20us.html">Contact Us</a></li>
        <li><a href="#" class="MenuBarItemSubmenu">Medical</a>
          <ul>
            <li><a href="lung%20blocker%20bed%20mounted.html">Lung Blocker Bed Mounted</a></li>
            <li><a href="lung%20blocker%20stand.html">Lung Blocker Stand</a></li>
            <li><a href="couch.html">Radiation Couch</a></li>
            <li><a href="lab%20bench.html">Lab Bench</a></li>
          </ul>
        </li>
        <li><a href="#" class="MenuBarItemSubmenu">Biotech</a>
          <ul>
            <li><a href="mega%20base%20SH.html">Mega Base Dispensing S.H</a></li>
            <li><a href="mega%20base%20DH.html">Mega Base Dispensing D.H</a></li>
            <li><a href="filling%20machine.html">Liquid Filling Machine</a></li>
            <li><a href="powder%20dispenser.html">Powder Dispensing</a></li>
            <li><a href="capper.html">Capper</a></li>
            <li><a href="laser%20labeler.html">Laser Labeler</a></li>
            <li><a href="racker.html">Vial Racker</a></li>
            <li><a href="dry%20box.html">Glove Box</a></li>
            <li><a href="heat%20seal.html">Sealing Press</a></li>
</ul>
        </li>
        <li><a href="#" class="MenuBarItemSubmenu">Polymers</a>
          <ul>
            <li><a href="lid%20stacking.html">Lid Stacking</a></li>
            <li><a href="heat%20staking%20machine.html">Heat Staking</a></li>
            <li><a href="tire%20assembly.html">Roller Assembly</a></li>
            <li><a href="lint%20trap.html">Lint Trap</a></li>
            <li><a href="bosch.html">Dryer Assembly</a></li>
            <li><a href="marbal.html">Cooling Tower</a></li>
            <li><a href="jar%20trimming.html">Jar Trimming</a></li>
          </ul>
        </li>
        <li><a href="#" class="MenuBarItemSubmenu">Fasteners</a>
          <ul>
            <li><a href="bent%20shank.html">Bent Shank </a></li>
            <li><a href="lug%20nuts%20tapping%20machine.html">Lug Nuts</a></li>
            <li><a href="round%20small%20nuts.html">Rivets Tapping</a></li>
            <li><a href="knurling.html">Knurling</a></li>
            <li><a href="eyebolts.html">Eye Bolts</a></li>
          </ul>
        </li>
        <li><a href="#" class="MenuBarItemSubmenu">Feeding</a>
          <ul>
            <li><a href="feeding%20with%20vision.html">Using Vision</a></li>
          </ul>
        </li>
        <li><a href="#" class="MenuBarItemSubmenu">Metal</a>
          <ul>
            <li><a href="champion.html">Rail Road</a></li>
            <li><a href="assembly.html">Assembly</a></li>
            <li><a href="coining.html">Coining</a></li>
            <li><a href="pointing.html">Pointing</a></li>
            <li><a href="damper%20assembly.html">Damper Assembly</a></li>
            <li><a href="fomo.html">Notching</a></li>
            <li><a href="nut%20welder.html">Nut Welding</a></li>
            <li><a href="soundwich.html">Dashboard</a></li>
            <li><a href="water%20pump.html">Drilling</a></li>
            <li><a href="rotor_deburing.html">Deburing</a></li>
          </ul>
        </li>
        <li><a href="#" class="MenuBarItemSubmenu">General</a>
          <ul>
            <li><a href="road%20construction.html">Road Construction</a></li>
            <li><a href="large%20hose.html">Large Hose Mfg. Drive</a></li>
          </ul>
        </li>
        <li><a href="IMTS%20show.html">IMTS Show</a></li>
        <li><a href="http://www.yedaengineering.com/">Yeda LLC</a></li>
      </ul>
</div>
<h2> </h2>
    <p class="MenuBarHorizontal"> </p>
    <p> </p>
<p class="style12"> </p>
    <p> </p>
    <p> </p>
    <p> </p>
    <p> </p>
    <p> </p>
    <p> </p>
    <p> </p>
    <p> </p>
</div>
<div class="footer">
    <div id="apDiv8">Nogah Engineering 1800 London Road Unit C Cleveland Ohio 44112 USA Tel: 216.738.1730 Fax: 216.738.1770 </div>
    <p> </p>
</div>
</div>
<script type="text/javascript">
var MenuBar1 = new Spry.Widget.MenuBar("MenuBar1", {imgDown:"../SpryAssets/SpryMenuBarDownHover.gif", imgRight:"../SpryAssets/SpryMenuBarRightHover.gif"});
</script>
</body>
</html>
Thanks.

All these supporting files are missing (404 not found on server).
<link href="../Spry-UI-1.7/css/SpryImageSlideShow.css" rel="stylesheet" type="text/css">
<script src="../Spry-UI-1.7/includes/SpryDOMUtils.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryDOMEffects.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryWidget.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryPanelSet.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryFadingPanels.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryImageLoader.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/SpryImageSlideShow.js" type="text/javascript"></script>
<script src="../Spry-UI-1.7/includes/plugins/ImageSlideShow/SpryPanAndZoomPlugin.js" type="text/javascript"></script>
Upload Spry-UI-1.7 folder to your remote server by clicking the folder and hitting the UP arrow in your Files Panel.
Also, validate your code and fix reported errors. You have unbalanced div tags.
HTML - http://validator.w3.org/
Nancy O.

The text in my Word document has disappeared. Any suggestions for recovery? Its due in tomorrow morning!

I have a essay I've been working on, using MS Word for Mac and today when I opened the file all the text is missing. The layout (position of text boxes etc) is still there and images of graphs I inserted are still there too. It's just the text I wrote that has vanished. Its due in tomorrow, any ideas guys?

You should contact Microsoft for Mac Support and/or post in their forums.

More than 1 line of text when using text generator from file?

hi
have 8 line blocks of text to show onscreen.
would like to use text generatorn>from file
all they seem to print is one line.
is there a work around?
have trhied soft returns and paragraphs on saved text file.
no change.
anyonre know how to get 2 or more lines of text?
thanks in addvance!

Select the File generator layer and in the Inspector, select the Layout pane and in Layout controls, set the Layout Method to Paragraph. Narrow your margins and the text will "flow" into multiple lines.
You can also keyframe the paragraph layout position. [Probably more info than you want here.]
That said, you can only display *one line* at a time per File Generator. (If you're up to date with Motion [v5.1.2], you can use more than one File generator.) The generator does not accept any other characters for returns other than newline and carriage return.
I've never tried it, but thinking about it, you can set Tab stops in the Paragraph layout (double click in the layout rectangle and a ruler should appear over the top -- right click on the ruler to set tabs). If you go back into the original text file and where you need to break lines into two or more, setting a left tab stop in the layout very near the end of a line might force the tabbed text into the next line (did I make that clear enough??)

Template problem with a scroll

Hi,
This is Niranjan Reddy. I am using the ADF Ritch client with JDeveloper 11g Premier 1. I created a template with a panelstrech layout(position:absolute;width:100%;height:100%).
My requirment is to increase the height of the layout when the components in the page increase.But I am not able to get it.Can any one can sole my problem
Thanks in advance
NIRANJAN REDDY

You need the JDeveloper and ADF.

Travel expense print form

Hello all,
I have an issue regarding the travel expense print form.
The problem is not related to the printer, it is related to the PDF-File which is created.
In the PDF-File, the left margin is wrong. Thus, it can not be printed correctly due to the wrong margin.
On the left side, the border line and some characters are not printed.
If I have to adjust something, how can I procede?
Thanks in advance for your help,
Soumaya

Do you have many receipts in the PDF? If so it can affect the spacing and margins - check it as follows:
Access your form via SFP;
Select: Layout;
Position yourself on the faulty table;
Make palette "Object" avaible for entry;
In the "Binding" section of "Object" you will find the pertinent
table stated in the "Name:" field
Click onto "Pagination";
Here adjust if neccessary the following boxes:
Include Header Row in Initial Page and
Include Header Row in Subsequent Pages
Also there were some notes released for more specific issues 1140369

Using different content with template tag (struts)

I developed a page according to the examples on the following link.
http://jakarta.apache.org/struts/api/org/apache/struts/taglib/template/package-summary.html
my problem is, that i want to use different pages as content. How can i do this?? do i need, to write multiple pages like this??
<%@ taglib uri='/WEB-INF/tlds/struts-template.tld' prefix='template'>
<template:insert template='/chapterTemplate.jsp'>
<template:put name='title' content='Templates' direct='true'/> <template:put name='header' content='/header.html' />
<template:put name='sidebar' content='/sidebar.jsp' />
<template:put name='content' content='/introduction.html'/>
<template:put name='footer' content='/footer.html' />
</template:insert><%/*"introduction.jsp"Specify template for this page (chapterTemplate.jsp).The chapterTemplate.jsp defines the layout positions for fiveelements: title, header, sidebar, content, and footer.Specify the source file (html or jsp) for each element.*/%>

slight typo .. corrected version
<definition name="master" path="/chapterTemplate.jsp">
<put name="title" value="title.jsp" />
<put name="sidebar" value="sidebar.jsp" />
<put name="body" value="body.jsp" />
<put name="footer" value="footer.jsp" />
</definition>
<definition name="a.struts.def" extends="master">
<put name="body" value="anotherBodyA.jsp" />
</definition>
<definition name="b.struts.def" extends="master">
<put name="body" value="anotherBodyB.jsp" />
</definition>

How to Make a "fonts.css" style sheet

Hi, I have a wordpress blog with a stylesheet named “style.css”. I want to change the fonts in the style sheet and so I want to create a separate style sheet named “fonts.css"
I could just duplicate the ”style.css” page and then rename it “fonts.css” but I believe I read somewhere it is better to create a new style sheet named “fonts.css” and then add my font styles to that. Doens anyone know of a tutorial or how I make the new style sheet and add my fonts?

I only typically use two stylesheets on any given site, layout.css and styles.css. One is for the overall layout/positioning info of the site and the other is the style information which would include fonts, colors, shadows, transitions, etc.
If it is better in your mind and for your workflow to create a third stylesheet just for the font values, go for it. To me, fonts are just another style element though, so they stay in my styles.css file.
There's really no right or wrong to doing it either way. Just make sure you create another link in the head section of your site to the new file if you create fonts.css.
Thanks jon,
Yes I agree, I could just change the fonts in “style.css” and then have less style sheets, but the themes developer told me to create a new style sheet named “fonts.css” only because the theme is updated regularly and uploading a new theme will write over the file named “style.css” and then your fonts will default to their original fonts.
I don't see anything wrong with that approach. Just remember that if you have both styesheets linked to the same page then the page will get it's css styles from the last linked stylesheet.
So for instance if you have:
body {
font-size: 14px ;
in the style.css
and
body {
font-size: 12px ;
in the fonts.css
and the last linked stylesheet was styles.css the page would display 14px text.
So you just need to get them in the right order IF you have more than one styleshet linked to a page.
Thanks Osgood,
Yes that was my other question. So in my uploaded CSS folder I have the original “style.css” file and now my new “fonts.css” file. “style.css” is above the “fonts.css” file and both contain the same information except the file “fonts.css’ has been changed to use different fonts.
So if I understand you correctly I need to either move the file “fonts.css" above the file “style.css” or delete “style .css” from the CSS folder so the file “fonts.css” will take precedence. Is this correct?
Also, I needed to open style.php and edit the code to include “fonts.css” which I did.
I opened "style.php" and then added the code in "red" then uploaded it to the (CSS) folder on the server.
<?php
header( "Content-type: text/css" );
$files = array();
$files[] = 'style.css';
$files[] = 'responsive.css';
$files[] = 'fonts.css';
foreach($files as $file) :
    $content = @file_get_contents( $file );
    echo minify( $content );
endforeach;
function minify( $code ) {
          $code = preg_replace( '#\s+#', ' ', $code );
          $code = preg_replace( '#/\*.*?\*/#s', '', $code );
          $code = str_replace( '; ', ';', $code );
          $code = str_replace( ': ', ':', $code );
          $code = str_replace( ' {', '{', $code );
          $code = str_replace( '{ ', '{', $code );
          $code = str_replace( ', ', ',', $code );
          $code = str_replace( '} ', '}', $code );
          $code = str_replace( ';}', '}', $code );
          return trim( $code );
?>
After doing all of this I still didn’t see any changes to my fonts so I must have done something wrong.
Any ideas?

ABAP Module pool programming

Hi all plz any one send me the doc for Module pool programmiing to learn on my own
thanks & regards
vamsin

Hi,
This is the material find the attachment.
hi,
Pool table
A database table defined in the ABAP Dictionary whose database instance is assigned to more than one table defined in the ABAP Dictionary. Multiple pool tables are assigned to a table pool in the database. The key fields of a pool table have to be character-type fields. The table pool's primary key consists of two fields: TABNAME for the name of a pool table, and VARKEY for the interdependent contents of the key fields in the corresponding pool table. The non-key fields of the pool table are stored in compressed format in their own column, called VARDATA, of the table pool. The only way to access pool tables is by using Open SQL. Joins are not allowed.
Table Pool
Database table in the database that contains the data of several pool tables.
Cluster Table
Database table defined in the ABAP Dictionary, whose version on the database is not only assigned to one table defined in the ABAP Dictionary. Several cluster tables are assigned to a table cluster in the database. The intersection of the key fields of the cluster tables forms the primary key of the table cluster. The other columns of the cluster tables are stored in compressed form in a single column VARDATA of the table cluster. You can access cluster tables only via Open SQL, and only without using joins.
Table Cluster
Database table in the database that contains the data of several cluster tables.
Note: Never mix up with a database table that has the necessary structure for storing data clusters in database tables and in the shared memory. Those are called INDX-type, with reference to the database table INDX supplied by SAP. Data clusters are groupings of data objects for transient and persistent storage in a selectable storage medium. A data cluster can be processed using the statements IMPORT, EXPORT, and DELETE FROM
P.Naganjana ReddyDAY-4 CONTENTS
SCREEN PAINTER
     &#56256;&#56510;
Introduction to Dialog Programming
     &#56256;&#56510;
Transactions
Screens (dynpros)
ABAP/4 module pool
Transferring Field Data
Field Attributes
Error Dialogs
Data Consistency
Dynpro
Layout
     &#56256;&#56510;
Exercise
TABLE CONTROL
     &#56256;&#56510;
Functional scope
     &#56256;&#56510;
Programming
     &#56256;&#56510;
Attributes
     &#56256;&#56510;
EXERCISE
TABSTRIP CONTROLS
     &#56256;&#56510;
Defining the Tabstrip Control Area and Tab Titles
     &#56256;&#56510;
Assigning a Subscreen Area to a Tab Title
     &#56256;&#56510;
Paging in the SAPgui
     &#56256;&#56510;
Programming the Flow Logic
     &#56256;&#56510;
EXERCISE
P.Naganjana Reddy
SCREEN WITH FIELDS
Introduction to Dialog Programming
Transactions
A transaction is a program that conducts a dialog with the user. In a typical dialog, the
system displays a screen on which the user can enter or request information. As a reaction on
the the user input or request, the program executes the appropriate actions: it branches to the
next screen, displays an output, or changes the database.
Example
A travel agent wants to book a flight. The agent enters the corresponding data on the
screen. The system either confirms the desired request, that is, the agent can book the flight
and the customer travels on the desired day on the reserved seat to the chosen destination,
or the system displays the information that the flight is already booked up.
To fulfil such requirements, a dialog program must offer:
_a user-friendly user interface
_format and consistency checks for the data entered by the user
_easy correction of input errors
_access to data by storing it in the database.
ABAP/4 offers a variety of tools and language elements to meet the requirements stated
above in the dialog programs.
Structure of a Dialog Program
A dialog program consists of the following basic components:
P.Naganjana Reddy
Screens (dynpros)
Each dialog in an SAP system is controlled by dynpros. A dynpro (Dynamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).
The screen layout fixed in the Screen Painter determines the positions of input/output
fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.
ABAP/4 module pool
Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.
Transferring Field Data
How do I display fields known in an ABAP/4 module on the screen? How do I transfer
user entries on the screen to the module? In contrast to report programming, you cannot write field data to the screen using the WRITE statement. The system instead transfers data by comparing screen field names with ABAP/4 variable names. If both names are the same, it transfers screen field values to ABAP/4 program fields and vice versa. This happens immediately before and immediately after displaying the screen.
Field Attributes
For all screen fields of a dynpro, field attributes are defined in the Screen Painter. If a
field name in the screen corresponds to the name of an ABAP/4 Dictionary field, the system automatically establishes a reference between these two fields. Thus, a large number of field attributes in the dynpro is automatically copied from the ABAP/4 Dictionary. The field attributes together with data element and domain of the assigned Dictionary field form the basis for the standard functions the dynpro executes in a dialog (automatic format check for screen fields, automatic value range check, online help, and so on).
Error Dialogs
Another task of the dynpro processor is to conduct error dialogs. Checking the input data is carried out either automatically using check tables of the ABAP/4 Dictionary or by the ABAP/4 program itself. The dynpro processor includes the error message into the received screen and returns the screen to the user. The message may be context-sensitive, that is, the system replaces placeholders in the message text with current field contents. In addition, only fields whose contents is related to the error and for which a correction may solve the error can accept input.
P.Naganjana Reddy
Data Consistency
To keep data consistent within complex applications, ABAP/4 offers techniques for
optimizing database updates that operate independent of the underlying database and correspond to the special requests of dialog programming. For more information on database updates, see Programming Database Updates.
Dynpro
Each screen contains fields used to display or request information. Fields can be text strings, input or output fields, radio buttons, checkboxes, or pushbuttons. The screen of Transaction TZ10 contains only texts and input/output fields.
An SAP dynpro consists of several components:
Flow logic: Calls of the ABAP/4 modules for a screen.
Screen layout: Positions of the texts, fields, pushbuttons, and so on for a screen.
Screen attributes: Number of the screen, number of the subsequent screen, and others.
Field attributes: Definition of the attributes of the individual fields on a screen.
SCREEN PAINTER
You create and edit all components of a dynpro in the Screen Painter. To call the Screen
Painter, create a dynpro in the Object Browser or double-click on an existing dynpro. The Object Browser then calls the Screen Painter. There, you can enter the flow logic of the new dynpro. By pressing the corresponding pushbutton you can maintain the Screen attributes, branch to the Full Screen-Editor or you choose the pushbutton Field list and change the attributes of fields.
Screen Attributes
From the users point of view, a transaction is a sequence of screens, displayed one after
another. How do I determine this sequence? The transactionss attributes determine the first screen to be displayed. The attributes of the individual dynpros determine which screen to display
P.Naganjana Reddy
after the current screen. You can also set the number of the subsequent screen dynamically from within the ABAP/4 program.
Layout
Choose Fullscreen to go to the screen editor. Here you can determine the layout of the
screen. For Transaction TZ10, the desired fields can be copied from Table SPFLI of the
ABAP/4 Dictionary.
Field Attributes
To display and modify the attributes of the individual fields (input/output fields, input
required, possible entries button, invisible, and so on), use the Field list.The fields Company (SPFLI-CARRID) and Flight number (SPFLI-CONNID) are defined as input/output fields. All other fields are used only for outputting the flight data.
Flow Logic
The flow control code of a dynpro consists of a few statements that syntactically ressemble ABAP/4 statements. However, you cannot use flow contol keywords in ABAP/4 and vice versa. You enter the flow control code in the Screen Painter as one component of the dynpro.
The flow control for the dynpro of Transaction TZ10 looks like this:
PROCESS BEFORE OUTPUT.
MODULE SET_STATUS_0100.
PROCESS AFTER INPUT
MODULE USER_COMMAND_0100.
The PROCESS statement names the event type for the dynpro and the MODULE statement tells the system which ABAP/4 routine to call for this event. In this example, there is only one MODULE for each event PBO and PAI. However, an event can contain several statements with several keywords. (The flow control language contains only few statement types. The most important are MODULE, FIELD, CHAIN, LOOP, CALL SUBSCREEN.) To display information on the statement syntax in the flow logic, choose Utilities Help on... in the flow logic editor. In the subsequent dialog window, mark Flow logickeyword, enter the name of the desired keyword, and press ENTER.
ABAP/4 Module Pool
In the Object Browser, the module pool code belongs to one of the following categories:
Global fields: data declarations that can be used by all modules in the module pool
PBO modules: modules that are called before displaying the screen
PAI modules: modules that are called in response to the user input
Subroutines: subroutines that can be called from any position within the module pool.
You use the ABAP/4 Dictionary to store frequently used data declarations centrally. Objects defined in the Dictionary are known throughout the system. Active Dictionary definitions can be accessed by any application. Data defined in the Dictionary can be included in a screen or used by an ABAP/4 program. You declare global data in the TOP module of the transaction, using the TABLES, STRUCTURE, LIKE statements and others. Transaction TZ10 accesses the Dictionary definition of Table SPFLI to provide the desired flight data display. If the TOP include contains the TABLES: SPFLI declaration, all modules in the module pool can access the table fields of
P.Naganjana Reddy
Table SPFLI. The PAI module USER_COMMAND_0100 checks which pushbutton the user activated (CASE OK_CODE). The Display pushbutton in Transaction TZ10 has the function code
SHOW. (For more information on handling function codes, see Processing User Requests). The program then tries to select those records in the SPFLI database that correspond to the data the user entered. The WHERE condition determines matching records by comparing the fields SPFLI-CARRID and SPFLI-CONNID with the database key fields CARRID and CONNID. As soon as a matching record is found, the database transfers all accompanying SPFLI fields to the program table.
When the screen is displayed again, the complete information appears in the output fields
of the screen. The system automatically displays these fields, since the ABAP/4 field names SPFLI-CARRID and SPFLI-CONNID are the same as the screen field names.
In the PBO module STATUS_0100 of Transaction TZ10, the screen 100 receives a GUI status (using SET PF-STATUS) and a GUI title (using SET TITLEBAR):
SET PF-STATUS TZ0100.
SET TITLEBAR 100.
A GUI status is a subset of the interface elements used for a certain screen. The status
Comprise those elements that are currently needed by the transaction. The GUI status for a transaction may be composed of the following elements:
The GUI title is the screen title displayed in the title bar of the window. In contrast to the
GUI status that can be used for several screens, a GUI title belongs to one screen.To create and edit GUI status and GUI title, you use the Menu Painter. To start the Menu Painter, create a GUI status or GUI title in an object list in the Object Browser (or double-click on an existing status or title).
Interaction between Dynpro and ABAP/4 Module Pool
In its most simple form, a transaction is a collection of screens and ABAP/4 routines, controlled and executed by a dialog processor. The dialog processor processes screen after screen, thereby triggering the appropriate ABAP/4 processing for each screen. For each screen, the system executes the flow logic that contains the corresponding ABAP/4 processing. The control passes from screen flow logic to ABAP/4 code and back.
The sequence of events for Transaction TZ10, for example, looks like this:
P.Naganjana Reddy
     1.
In the PBO event, the statement MODULE STATUS_0100 passes control to the corresponding ABAP/4 module.In the ABAP/4 module pool, the screen to be displayed receives a menu interface.
2.
After processing the module STATUS_0100, control returns to the flow logic.For the PBO event, no further processing is required. The system display the screen and receives entries from the user. The entries are:
the values for the fields Company and Flight number.
the four-character function code that tells which pushbutton the user activated.
     3.
The user input triggers the PAI event. The first PAI statement passes control to the ABAP/4 module USER_COMMAND_0100.Module USER_COMMAND_0100 processes the requests of the user.
4. After processing MODULE USER_COMMAND_0100, control returns to PAI. This terminates the dialog.
P.Naganjana Reddy
EXERCISE
Goto to ABAP editor, and enter the program name ZKA_SCREEN.
Declare the tables and call the screen.
In order to create the object, double click on the screen no, you will automatically guided to the screen painter SE51.
P.Naganjana Reddy
Enter the short description and click on the FLOW LOGIC tab.
Uncomment the flow logic, both PAI and PBO.
P.Naganjana Reddy
Now click on the LAYOUT button.
Click on the DICTIONARY/PROGRAM FIELDS WINDOW F6 button. Type in the table name and click on GET FROM DIC button and select the fields required for the screen and click on the COPY button.
P.Naganjana Reddy
Now drag and place the INPUT/OUTPUT fields box on the screen.
Now click on the TEXT FIELD button and place in the screen and stretch the box for the size required. Now double click on the box, U will get the attributes screen. Enter the name and Text for the field.
P.Naganjana Reddy
Now we need to place the bush buttons. So Click on the push button on the left side and place it on the screen. Double click on it, u will get the attributes screen. Enter the name, text and the icon required and mainly the FCTCODE. It is the one which links the screen painter with the code.
Once everything is set up, SAVE, CHECK and ACTIVATE the screen.
P.Naganjana Reddy
Click on the BACK button. U will be guided to the FLOW LOGIC screen.
Double click on PAI, Because for the screen painter with the fields, Process After the Input is done and so u will guided to the Editor screen.
P.Naganjana Reddy
Now we need to set the System-Uses commands which links the code to the Editor.
So the conditions would be:
IF SY-UCOMM = 'DISPLAY'.
SELECT SINGLE * FROM ZKA_CENTER WHERE CENTERNO = ZKA_CENTER-CENTERNO.
ELSEIF SY-UCOMM ='SAVE'.
INSERT ZKA_CENTER.
ELSEIF SY-UCOMM = 'REFRESH'.
CLEAR ZKA_CENTER.
ELSEIF SY-UCOMM = 'GOTO'.
LEAVE TO SCREEN '0002'.
ELSEIF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
If u create many screens and need links between the screens then u can use GOTO to guide to the other screen.
SAVE, CHECK and ACTIVATE and click on TEST.
P.Naganjana Reddy
Now click on the DISPLAY button.
Also verify with SAVE, REFRESH and EXIT buttons. Thus the screen painter.
P.Naganjana Reddy
TABLE CONTROL
Basic form
CONTROLS ctrl TYPE TABLEVIEW USING SCREEN scr.
Effect
Creates a table control ctrl of the type TABLEVIEW . The reference screen for the initialization is the screen scr . Area of use The table control (referred to here as TC ) facilitates the display and entry of one-line, tabular data in dialog transactions. The functional scope has been defined so that you can implement many typical set operations usually handled by an elementary STEP-LOOP with the standard methods of a TC . Functional scope
Resizeable table grid for displaying and editing data.
Column width and column position modifiable by user and by program.
Storing and loading of user-specific column layout.
Selection column for line selection with color selection display.
Variable column headers as pushbuttons for column selection.
Simple selection, multiple selection, Select/deselect all.
Scrolling functions (horizontal and vertical) via scroll bar.
Fixing of any number of key columns.
Setting attributes for each cell at runtime.
Programming The data exchange between the application and the SAPgui is achieved with a STEP-LOOP , i.e. an ABAP/4 module is called to transfer data for each page.
Example
Processing without an internal table
PROCESS BEFORE OUTPUT.
LOOP WITH CONTROL ctrl.
MODULE ctrl_pbo.
ENDLOOP.
PROCESS AFTER INPUT.
LOOP WITH CONTROL ctrl.
MODULE ctrl_pai.
ENDLOOP.
In this case, the module ctrl_pbo OUTPUT is called once for each output line before the screen is displayed, in order to fill the output fields. After the user has entered data on the screen, the module ctrl_pai INPUT is executed to check the input and copy the new contents.
Example
Processing with an internal table
P.Naganjana Reddy
PROCESS BEFORE OUTPUT.
LOOP AT itab WITH CONTROL ctrl CURSOR ctrl-CURRENT_LINE.
ENDLOOP.
PROCESS AFTER INPUT.
LOOP AT itab WITH CONTROL ctrl.
MODULE ctrl_pai.
ENDLOOP.
Here, the system fills the output fields before displaying the screen by reading the internal table itab. When the user has entered data, the module ctrl_pai INPUT must be executed to check the input and to refresh the contents of the internal table. Vertical scrolling with the scroll bar is followed by the event PAI for the displayed page. Then, cntl-TOP_LINE is increased and PBO is processed for the next page. Program-driven scrolling and the most of the functionality described above is achieved by manipulating the control attributes.
Attributes The CONTROLS statement creates a complex data object of the type CXTAB_CONTROL with the name of the control. You maintain the initial values in the Screen Painter and assign the screen with the initial values for a control using the addition USING SCREEN . Initialization is achieved automatically in the "1st access to the control" (setting or reading values). You can use the customizing button (in the top right corner) to save the current setting (column widths and column positions) and use it as the initial value for the next call. All the initial values can be overwritten by the program using the MOVE ... TO TC attributes statement.
EXERCISE
Enter the Editor with SE38.
Declare the Tables and an internal table.
Then use the CONTROLS statement to have the controls for the Table control.
P.Naganjana Reddy
CONTROLS: <var> TYPE TABLEVIEW USING SCREEN '<screenno>'.
Now call the screen with the CALL SCREEN statement. Click on the screen to draw the table.
Fill in the attributes screen with the short description and click on the LAYOUT button.
Now click on the TABLE CONTROL button and draw the table to the size required. Double click on the table and enter the Attributes giving the Table-control name.
And select the check boxes for the vertical & horizontal resizing and separators.
Click on the DICTIONARY/PROGRAM FIELDS WINDOW F6 button. Type in the table name and click on GET FROM PROGRAM button and select the fields required for the screen and click on the COPY button.
P.Naganjana Reddy
Enter the header with the TEXT FIELDS button by double clicking on the TEXT FIELD and fill in the ATTRIBUTES button with the name and text.
P.Naganjana Reddy
SAVE, CHECK & ACTIVATE.
Click the BACK button and go the FLOW LOGIC screen.
P.Naganjana Reddy
REPORT ZKA_TC .
TABLES: ZKA_EMP.
DATA: ITAB LIKE ZKA_EMP OCCURS 0 WITH HEADER LINE.
CONTROLS: TC TYPE TABLEVIEW USING SCREEN '0001'.
CALL SCREEN '0001'.
*& Module STATUS_0001 OUTPUT
text
MODULE STATUS_0001 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
SELECT * FROM ZKA_EMP INTO TABLE ITAB.
ENDMODULE. " STATUS_0001 OUTPUT
*& Module USER_COMMAND_0001 INPUT
P.Naganjana Reddy
text
MODULE USER_COMMAND_0001 INPUT.
IF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
ENDMODULE. " USER_COMMAND_0001 INPUT
P.Naganjana Reddy
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
P.Naganjana Reddy
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.
P.Naganjana Reddy
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>, ... ...
P.Naganjana Reddy
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.
P.Naganjana Reddy
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.
P.Naganjana Reddy
EXERCISE
Goto SE38. Enter the tabstrip program name Eg: ZKA_TABSTRIP and click on the create button.
First we need to declare the tables.
Then use the controls for the tabstrip.
Syntax: <ctrl-name> TYPE TASTRIP.
Now call the screen. Using CALL SCREEN statement.
Double click on the screen no to draw the screen for tabstrip control.
Now uncomment the FLOW LOGIC and click on the LAYOUT.
P.Naganjana Reddy
The flow logic for the tabstrip would be as follows.
PBO:
The PBO is initiated so that the subscreen for the corresponding tab can be maintained.
Syntax:
CALL SUBSCREEEN <sub-screen name> INCLUDING SY-REPID <screen-var>.
PAI:
When the tab is clicked, the corresponding subscren should open
Syntax:
CALL SUBSCREEN <subscreen>.
P.Naganjana Reddy
DRAWING THE TABSTRIP CONTROL:
Click on the TABSTRIP button and place it on the screen for the required size.
Double click on the control and give the name for the tabstrip control in the ATTRIBUTES screen.
Now double click on the tab and fill in the attributes screen for the name and the text.
Also draw the subscreen in one of the tab and refer the same subscreen in the rest of the tabs.
P.Naganjana Reddy
Now in the sub-screens, we need to get the screen for the tabs.
So call an other screen and draw with fields and pushbuttons to perform actions very similar like SCREEN WITH FIELDS (refer screen painter).
Enter the short description and click on the FLOW LOGIC tab.
P.Naganjana Reddy
Uncomment the flow logic, both PAI and PBO.
Now click on the LAYOUT button.
Naganjana Reddy.P
Click on the DICTIONARY/PROGRAM FIELDS WINDOW F6 button. Type in the table name and click on GET FROM DIC button and select the fields required for the screen and click on the COPY button.
Now drag and place the INPUT/OUTPUT fields box on the screen.
P.Naganjana Reddy
Now click on the TEXT FIELD button and place in the screen and stretch the box for the size required. Now double click on the box, U will get the attributes screen. Enter the name and Text for the field.
Now we need to place the bush buttons. So Click on the push button on the left side and place it on the screen. Double click on it, u will get the attributes screen. Enter the name, text and the icon required and mainly the FCTCODE. It is the one which links the screen painter with the code.
P.Naganjana Reddy
Once everything is set up, SAVE, CHECK and ACTIVATE the screen.
P.Naganjana Reddy
Click on the BACK button. U will be guided to the FLOW LOGIC screen.
Double click on PAI, Because for the screen painter with the fields, Process After the Input is done and so u will guided to the Editor screen.
P.Naganjana Reddy
Now we need to set the System-Uses commands which links the code to the Editor.
So the conditions would be:
IF SY-UCOMM = 'DISPLAY'.
SELECT SINGLE * FROM ZKA_CENTER WHERE CENTERNO = ZKA_CENTER-CENTERNO.
ELSEIF SY-UCOMM ='SAVE'.
INSERT ZKA_CENTER.
ELSEIF SY-UCOMM = 'REFRESH'.
CLEAR ZKA_CENTER.
ELSEIF SY-UCOMM = 'GOTO'.
LEAVE TO SCREEN '0002'.
ELSEIF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
The same procedure for the company table as well will lead the screen in the below manner.
P.Naganjana Reddy
Summary:
REPORT ZKA_TABSTRIP .
TABLES: ZKA_EMP,ZKA_COM.
CONTROLS: TS TYPE TABSTRIP..
DATA: SCREENNO(4) TYPE N.
CALL SCREEN '0003'.
*& Module STATUS_0001 OUTPUT
text
MODULE STATUS_0001 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
IF SCREENNO IS INITIAL.
TS-ACTIVETAB = 'EMP'.
SCREENNO = '0002'.
ENDIF.
ENDMODULE. " STATUS_0001 OUTPUT
*& Module USER_COMMAND_0001 INPUT
text
MODULE USER_COMMAND_0001 INPUT.
IF SY-UCOMM = 'EMP'.
TS-ACTIVETAB = 'EMP'.
SCREENNO = '0002'.
ELSEIF SY-UCOMM = 'COM'.
TS-ACTIVETAB = 'COM'.
SCREENNO = '0003'.
ENDIF.
ENDMODULE. " USER_COMMAND_0001 INPUT
*& Module USER_COMMAND_0002 INPUT
text
MODULE USER_COMMAND_0002 INPUT.
IF SY-UCOMM = 'DISPLAY'.
SELECT SINGLE * FROM ZKA_EMP WHERE EMPNO = ZKA_EMP-EMPNO.
ELSEIF SY-UCOMM = 'SAVE'.
INSERT ZKA_EMP.
ELSEIF SY-UCOMM = 'REFRESH'.
CLEAR ZKA_EMP.
ELSEIF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
P.Naganjana Reddy

VerifyError: Error #1063: Argument count mismatch on mx.core::RSLItem(). Expected 1, got 3.

Im getting the following error when trying to run my application, which was migrated from 3.5 to 3.6A:
VerifyError: Error #1063: Argument count mismatch on mx.core::RSLItem(). Expected 1, got 3.
The original application was built with Flash Builder 4 (SDK 3.5), and imported in Flash Builder 4.6 (using SDK 3.6A).
The error is displayed only when the framework linkage type is set to RSL, when using the framework linkage "Merged into code", the application runs fine. But we need to use RSL as the application is quite large.
Any help appreciated.
Thanks.

After generating the link report, i found that the RSLItem is called from core classes, namely: RSLListLoader.as, RSLItem.as, framework.swc. Find below the XML report generated.
Can you please have a look and see if there is any anomaly in the report ?
Thanks.
<report>
<scripts>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/resources/ResourceBundle)" mod="1308335066955" size="3594" optimizedsize="1671">
      <def id="mx.resources:ResourceBundle" />
      <pre id="mx.resources:IResourceBundle" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="mx.utils:StringUtil" />
      <dep id="mx.core:mx_internal" />
      <dep id="flash.system:ApplicationDomain" />
      <dep id="Error" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/GIFImage)" mod="1264282454000" size="588" optimizedsize="296">
      <def id="org.alivepdf.images:GIFImage" />
      <pre id="org.alivepdf.images:PDFImage" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="org.alivepdf.images:ColorSpace" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/links/HTTPLink)" mod="1308306274843" size="470" optimizedsize="210">
      <def id="org.alivepdf.links:HTTPLink" />
      <pre id="Object" />
      <pre id="org.alivepdf.links:ILink" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\reports\PmsAnnexReport.as" mod="1308307027120" size="4769" optimizedsize="3101">
      <def id="modules.reports:PmsAnnexReport" />
      <pre id="modules.reports:BasePmsReport" />
      <pre id="interfaces:IDisposable" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="models:MappingScoringRemark" />
      <dep id="org.alivepdf.drawing:Joint" />
      <dep id="org.alivepdf.images:ColorSpace" />
      <dep id="mx.collections:ArrayCollection" />
      <dep id="models:Family" />
      <dep id="org.alivepdf.layout:Mode" />
      <dep id="AS3" />
      <dep id="org.alivepdf.layout:Position" />
      <dep id="org.alivepdf.data:Grid" />
      <dep id="org.alivepdf.data:GridColumn" />
      <dep id="org.alivepdf.layout:Resize" />
      <dep id="org.alivepdf.colors:RGBColor" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/FontMetrics)" mod="1264163544000" size="8666" optimizedsize="6536">
      <def id="org.alivepdf.fonts:FontMetrics" />
      <pre id="Object" />
      <dep id="org.alivepdf.fonts:FontFamily" />
      <dep id="AS3" />
      <dep id="Error" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/pages/Page)" mod="1308306275804" size="5962" optimizedsize="2628">
      <def id="org.alivepdf.pages:Page" />
      <pre id="Object" />
      <dep id="org.alivepdf.layout:Size" />
      <dep id="RangeError" />
      <dep id="AS3" />
      <dep id="org.alivepdf.layout:Orientation" />
      <dep id="org.alivepdf.events:PagingEvent" />
      <dep id="org.alivepdf.layout:Unit" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/PNGImage)" mod="1308306276248" size="2506" optimizedsize="1655">
      <def id="org.alivepdf.images:PNGImage" />
      <pre id="org.alivepdf.images:PDFImage" />
      <dep id="org.alivepdf.decoding:Filter" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="org.alivepdf.images:ColorSpace" />
      <dep id="Error" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\mx\core\RSLListLoader.as" mod="1302697093262" size="2303" optimizedsize="1135">
      <def id="mx.core:RSLListLoader" />
      <pre id="Object" />
      <dep id="flash.events:Event" />
      <dep id="mx.core:RSLItem" />
      <dep id="AS3" />
      <dep id="flash.utils:Dictionary" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_CP1252)" mod="1264282452000" size="753" optimizedsize="249">
      <def id="org.alivepdf.fonts:CodePage_CP1252" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/TIFFImage)" mod="1265032112000" size="635" optimizedsize="278">
      <def id="org.alivepdf.images:TIFFImage" />
      <pre id="org.alivepdf.images:PDFImage" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/layout/Position)" mod="1264282454000" size="562" optimizedsize="269">
      <def id="org.alivepdf.layout:Position" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/links/ILink)" mod="1264282450000" size="318" optimizedsize="104">
      <def id="org.alivepdf.links:ILink" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\models\PdfItem.as" mod="1302697106112" size="863" optimizedsize="414">
      <def id="modules.models:PdfItem" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/encoding/PNGEncoder)" mod="1264278206000" size="2218" optimizedsize="1283">
      <def id="org.alivepdf.encoding:PNGEncoder" />
      <pre id="Object" />
      <dep id="flash.display:BitmapData" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="flash.geom:Rectangle" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/ColorSpace)" mod="1264282454000" size="648" optimizedsize="331">
      <def id="org.alivepdf.images:ColorSpace" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/display/PageMode)" mod="1264282454000" size="751" optimizedsize="405">
      <def id="org.alivepdf.display:PageMode" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/visibility/Visibility)" mod="1264282452000" size="587" optimizedsize="275">
      <def id="org.alivepdf.visibility:Visibility" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/core/mx_internal)" mod="1308335051533" size="188" optimizedsize="109">
      <def id="mx.core:mx_internal" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\automation_agent_rb.swc$locale/en_US/controls.prop erties" mod="1330491712199" size="2963" optimizedsize="2848">
      <def id="en_US$controls_properties" />
      <def id="fr_FR$controls_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/layout/Size)" mod="1264282456000" size="1741" optimizedsize="1007">
      <def id="org.alivepdf.layout:Size" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/PDFImage)" mod="1308306276348" size="2560" optimizedsize="1020">
      <def id="org.alivepdf.images:PDFImage" />
      <pre id="org.alivepdf.images:IImage" />
      <pre id="Object" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/drawing/DashedLine)" mod="1264282452000" size="848" optimizedsize="426">
      <def id="org.alivepdf.drawing:DashedLine" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/events/CharacterEvent)" mod="1261661978000" size="873" optimizedsize="391">
      <def id="org.alivepdf.events:CharacterEvent" />
      <pre id="flash.events:Event" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\helpers\PdfHelper.as" mod="1313559214599" size="7275" optimizedsize="4683">
      <def id="modules.helpers:PdfHelper" />
      <pre id="Object" />
      <dep id="helpers:Translation" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="models:User" />
      <dep id="flash.errors:IllegalOperationError" />
      <dep id="flash.utils:ByteArray" />
      <dep id="views:LoaderWindow" />
      <dep id="flash.geom:Rectangle" />
      <dep id="modules.helpers:CustPDF" />
      <dep id="org.alivepdf.layout:Orientation" />
      <dep id="Math" />
      <dep id="modules.models:PdfItem" />
      <dep id="org.alivepdf.fonts:CoreFont" />
      <dep id="flash.geom:Point" />
      <dep id="mx.collections:ArrayCollection" />
      <dep id="org.alivepdf.layout:Size" />
      <dep id="org.alivepdf.fonts:Style" />
      <dep id="org.alivepdf.fonts:FontFamily" />
      <dep id="Date" />
      <dep id="AS3" />
      <dep id="org.alivepdf.saving:Method" />
      <dep id="org.alivepdf.layout:Unit" />
      <dep id="org.alivepdf.colors:RGBColor" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_CP1253)" mod="1264282452000" size="754" optimizedsize="249">
      <def id="org.alivepdf.fonts:CodePage_CP1253" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\automation_agent_rb.swc$locale/en_US/effects.prope rties" mod="1330491712215" size="551" optimizedsize="512">
      <def id="en_US$effects_properties" />
      <def id="fr_FR$effects_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/colors/IColor)" mod="1264282454000" size="327" optimizedsize="106">
      <def id="org.alivepdf.colors:IColor" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/annotations/MovieAnnotation)" mod="1265087336000" size="611" optimizedsize="259">
      <def id="org.alivepdf.annotations:MovieAnnotation" />
      <pre id="org.alivepdf.annotations:Annotation" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/IFont)" mod="1308306275234" size="1376" optimizedsize="400">
      <def id="org.alivepdf.fonts:IFont" />
      <pre id="flash.events:IEventDispatcher" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/events/ResourceEvent)" mod="1308335063174" size="1038" optimizedsize="570">
      <def id="mx.events:ResourceEvent" />
      <pre id="flash.events:ProgressEvent" />
      <dep id="flash.events:Event" />
      <dep id="AS3" />
      <dep id="mx.core:mx_internal" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/DoPNGImage)" mod="1265035590000" size="1023" optimizedsize="629">
      <def id="org.alivepdf.images:DoPNGImage" />
      <pre id="org.alivepdf.images:PNGImage" />
      <dep id="flash.display:BitmapData" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="org.alivepdf.images:ColorSpace" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/annotations/Annotation)" mod="1265082924000" size="1280" optimizedsize="507">
      <def id="org.alivepdf.annotations:Annotation" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/encoding/IntBlock)" mod="1264282452000" size="1381" optimizedsize="860">
      <def id="org.alivepdf.encoding:IntBlock" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="Error" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\reports\BasePmsReport.as" mod="1305264212432" size="4225" optimizedsize="2696">
      <def id="modules.reports:BasePmsReport" />
      <pre id="modules.interfaces:IPdfReport" />
      <pre id="Object" />
      <dep id="helpers:Translation" />
      <dep id="flash.events:Event" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="flash.utils:ByteArray" />
      <dep id="flash.net:URLRequest" />
      <dep id="flash.display:BitmapData" />
      <dep id="mx.controls:Alert" />
      <dep id="flash.events:IOErrorEvent" />
      <dep id="org.alivepdf.images:ColorSpace" />
      <dep id="Error" />
      <dep id="flash.utils:setTimeout" />
      <dep id="mx.collections:ArrayCollection" />
      <dep id="flash.net:URLLoaderDataFormat" />
      <dep id="org.alivepdf.encoding:JPEGEncoder" />
      <dep id="modules.helpers:PdfHelper" />
      <dep id="org.alivepdf.layout:Mode" />
      <dep id="AS3" />
      <dep id="org.alivepdf.layout:Position" />
      <dep id="flash.net:URLLoader" />
      <dep id="org.alivepdf.layout:Resize" />
      <dep id="org.alivepdf.colors:RGBColor" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_CP1254)" mod="1264282452000" size="754" optimizedsize="249">
      <def id="org.alivepdf.fonts:CodePage_CP1254" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/serializer/ISerializer)" mod="1264282454000" size="548" optimizedsize="201">
      <def id="org.alivepdf.serializer:ISerializer" />
      <pre id="Object" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
    </script>
    <script name="modules\reports\PmsAppraisalReport_icon_report_ok.as" mod="1302697102570" size="871" optimizedsize="352">
      <def id="modules.reports:PmsAppraisalReport_icon_report_ok" />
      <pre id="mx.core:BitmapAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\automation_agent_rb.swc$locale/en_US/skins.propert ies" mod="1330491712245" size="429" optimizedsize="392">
      <def id="en_US$skins_properties" />
      <def id="fr_FR$skins_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/operators/Drawing)" mod="1264282456000" size="675" optimizedsize="344">
      <def id="org.alivepdf.operators:Drawing" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/colors/RGBColor)" mod="1264282454000" size="932" optimizedsize="518">
      <def id="org.alivepdf.colors:RGBColor" />
      <pre id="org.alivepdf.colors:IColor" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/gif/events/FileTypeEvent)" mod="1264282454000" size="721" optimizedsize="322">
      <def id="org.alivepdf.images.gif.events:FileTypeEvent" />
      <pre id="flash.events:Event" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/tools/sprintf)" mod="1264282454000" size="3636" optimizedsize="2442">
      <def id="org.alivepdf.tools:sprintf" />
      <dep id="AS3" />
      <dep id="String" />
      <dep id="Number" />
      <dep id="int" />
      <dep id="Math" />
      <dep id="Boolean" />
      <dep id="uint" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/utils/LoaderUtil)" mod="1308335055471" size="1990" optimizedsize="1169">
      <def id="mx.utils:LoaderUtil" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="Math" />
      <dep id="flash.display:LoaderInfo" />
      <dep id="mx.core:mx_internal" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/FontType)" mod="1308306275524" size="515" optimizedsize="243">
      <def id="org.alivepdf.fonts:FontType" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\automation_agent_rb.swc$locale/en_US/containers.pr operties" mod="1330491712191" size="614" optimizedsize="571">
      <def id="fr_FR$containers_properties" />
      <def id="en_US$containers_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/Style)" mod="1262664974000" size="563" optimizedsize="269">
      <def id="org.alivepdf.fonts:Style" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/core/IFlexModuleFactory)" mod="1308335051502" size="972" optimizedsize="297">
      <def id="mx.core:IFlexModuleFactory" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="flash.utils:Dictionary" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/gif/decoder/GIFDecoder)" mod="1308306276171" size="11444" optimizedsize="5893">
      <def id="org.alivepdf.images.gif.decoder:GIFDecoder" />
      <pre id="Object" />
      <dep id="RangeError" />
      <dep id="flash.display:BitmapData" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="flash.geom:Rectangle" />
      <dep id="org.alivepdf.images.gif.frames:GIFFrame" />
      <dep id="org.alivepdf.images.gif.errors:FileTypeError" />
      <dep id="Error" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/resources/IResourceBundle)" mod="1308335066987" size="736" optimizedsize="221">
      <def id="mx.resources:IResourceBundle" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/EmbeddedFont)" mod="1264666580000" size="2550" optimizedsize="1383">
      <def id="org.alivepdf.fonts:EmbeddedFont" />
      <pre id="org.alivepdf.fonts:IFont" />
      <pre id="org.alivepdf.fonts:CoreFont" />
      <dep id="org.alivepdf.fonts:FontMetrics" />
      <dep id="org.alivepdf.fonts:AFMParser" />
      <dep id="org.alivepdf.fonts:FontType" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="org.alivepdf.fonts:FontDescription" />
      <dep id="org.alivepdf.events:CharacterEvent" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/cells/CellVO)" mod="1264282454000" size="838" optimizedsize="462">
      <def id="org.alivepdf.cells:CellVO" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="org.alivepdf.fonts:IFont" />
      <dep id="org.alivepdf.colors:IColor" />
      <dep id="org.alivepdf.links:ILink" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\reports\PmsMergedReferenceReport.as" mod="1329369707783" size="11739" optimizedsize="8300">
      <def id="modules.reports:PmsMergedReferenceReport" />
      <pre id="modules.reports:BasePmsReport" />
      <pre id="interfaces:IDisposable" />
      <dep id="helpers:Translation" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="models:Globals" />
      <dep id="org.alivepdf.drawing:Joint" />
      <dep id="modules.models:PdfItem" />
      <dep id="models:GenericQuery" />
      <dep id="org.alivepdf.events:PageEvent" />
      <dep id="uccore.utils:DateParser" />
      <dep id="models:AppraisalDetail" />
      <dep id="org.alivepdf.fonts:Style" />
      <dep id="mx.collections:ArrayCollection" />
      <dep id="mx.formatters:NumberFormatter" />
      <dep id="org.alivepdf.layout:Mode" />
      <dep id="AS3" />
      <dep id="mx.formatters:NumberBaseRoundType" />
      <dep id="org.alivepdf.layout:Position" />
      <dep id="org.alivepdf.layout:Resize" />
      <dep id="org.alivepdf.data:GridColumn" />
      <dep id="org.alivepdf.data:Grid" />
      <dep id="flash.utils:Dictionary" />
      <dep id="org.alivepdf.colors:RGBColor" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_CP1255)" mod="1264282452000" size="754" optimizedsize="249">
      <def id="org.alivepdf.fonts:CodePage_CP1255" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/resources/ResourceManager)" mod="1308335066971" size="946" optimizedsize="518">
      <def id="mx.resources:ResourceManager" />
      <pre id="Object" />
      <dep id="mx.resources:IResourceManager" />
      <dep id="AS3" />
      <dep id="mx.resources:ResourceManagerImpl" />
      <dep id="mx.core:Singleton" />
      <dep id="mx.core:mx_internal" />
      <dep id="Error" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/DoTIFFImage)" mod="1265035054000" size="848" optimizedsize="459">
      <def id="org.alivepdf.images:DoTIFFImage" />
      <pre id="org.alivepdf.images:TIFFImage" />
      <dep id="flash.display:BitmapData" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="org.alivepdf.images:ColorSpace" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/encoding/BitString)" mod="1264282452000" size="525" optimizedsize="226">
      <def id="org.alivepdf.encoding:BitString" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/html/HTMLTag)" mod="1308306275923" size="524" optimizedsize="232">
      <def id="org.alivepdf.html:HTMLTag" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/colors/GrayColor)" mod="1264282454000" size="483" optimizedsize="215">
      <def id="org.alivepdf.colors:GrayColor" />
      <pre id="org.alivepdf.colors:IColor" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/events/PageEvent)" mod="1264282454000" size="689" optimizedsize="337">
      <def id="org.alivepdf.events:PageEvent" />
      <pre id="flash.events:Event" />
      <dep id="org.alivepdf.pages:Page" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_KOI8R)" mod="1264282452000" size="748" optimizedsize="247">
      <def id="org.alivepdf.fonts:CodePage_KOI8R" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/core/Singleton)" mod="1308335052487" size="1087" optimizedsize="555">
      <def id="mx.core:Singleton" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="mx.core:mx_internal" />
      <dep id="Error" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/annotations/TextAnnotation)" mod="1265087094000" size="886" optimizedsize="368">
      <def id="org.alivepdf.annotations:TextAnnotation" />
      <pre id="org.alivepdf.annotations:Annotation" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/core/FlexVersion)" mod="1308335052315" size="2696" optimizedsize="1439">
      <def id="mx.core:FlexVersion" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="fr_FR$core_properties" />
      <dep id="en_US$core_properties" />
      <dep id="mx.core:mx_internal" />
      <dep id="mx.resources:ResourceManager" />
      <dep id="Error" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage)" mod="1262727576000" size="1477" optimizedsize="577">
      <def id="org.alivepdf.fonts:CodePage" />
      <pre id="Object" />
      <dep id="org.alivepdf.fonts:CodePage_CP1257" />
      <dep id="org.alivepdf.fonts:CodePage_KOI8U" />
      <dep id="org.alivepdf.fonts:CodePage_CP1258" />
      <dep id="org.alivepdf.fonts:CodePage_CP1255" />
      <dep id="org.alivepdf.fonts:CodePage_KOI8R" />
      <dep id="org.alivepdf.fonts:CodePage_CP1253" />
      <dep id="org.alivepdf.fonts:CodePage_CP1254" />
      <dep id="AS3" />
      <dep id="org.alivepdf.fonts:CodePage_CP1251" />
      <dep id="org.alivepdf.fonts:CodePage_CP1252" />
      <dep id="org.alivepdf.fonts:CodePage_CP1250" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/drawing/WindingRule)" mod="1264282452000" size="553" optimizedsize="263">
      <def id="org.alivepdf.drawing:WindingRule" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/AFMParser)" mod="1308306275328" size="8118" optimizedsize="4757">
      <def id="org.alivepdf.fonts:AFMParser" />
      <pre id="flash.events:EventDispatcher" />
      <dep id="org.alivepdf.fonts:FontType" />
      <dep id="flash.utils:ByteArray" />
      <dep id="org.alivepdf.fonts:CodePage" />
      <dep id="AS3" />
      <dep id="RegExp" />
      <dep id="flash.utils:Dictionary" />
      <dep id="Error" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/core/IFlexModule)" mod="1308335052362" size="568" optimizedsize="188">
      <def id="mx.core:IFlexModule" />
      <pre id="Object" />
      <dep id="mx.core:IFlexModuleFactory" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/export/CSVExport)" mod="1308306274976" size="1314" optimizedsize="783">
      <def id="org.alivepdf.export:CSVExport" />
      <pre id="org.alivepdf.serializer:ISerializer" />
      <pre id="Object" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="org.alivepdf.data:GridColumn" />
      <dep id="Error" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/modules/ModuleManagerGlobals)" mod="1308335065565" size="518" optimizedsize="211">
      <def id="mx.modules:ModuleManagerGlobals" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\reports\Pms360Report.as" mod="1317802148831" size="7875" optimizedsize="5680">
      <def id="modules.reports:Pms360Report" />
      <pre id="modules.reports:BasePmsReport" />
      <pre id="interfaces:IDisposable" />
      <dep id="mx.containers:VBox" />
      <dep id="helpers:Translation" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="Math" />
      <dep id="org.alivepdf.drawing:Joint" />
      <dep id="modules.models:PdfItem" />
      <dep id="XMLList" />
      <dep id="org.alivepdf.events:PageEvent" />
      <dep id="models:FeedbackReport" />
      <dep id="uccore.utils:DateParser" />
      <dep id="Error" />
      <dep id="org.alivepdf.fonts:Style" />
      <dep id="mx.collections:ArrayCollection" />
      <dep id="org.alivepdf.layout:Mode" />
      <dep id="AS3" />
      <dep id="org.alivepdf.layout:Position" />
      <dep id="XML" />
      <dep id="org.alivepdf.layout:Resize" />
      <dep id="org.alivepdf.data:GridColumn" />
      <dep id="org.alivepdf.data:Grid" />
      <dep id="org.alivepdf.colors:RGBColor" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\automation_agent_rb.swc$locale/en_US/core.properti es" mod="1330491712207" size="1078" optimizedsize="1025">
      <def id="fr_FR$core_properties" />
      <def id="en_US$core_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/pdf/PDF)" mod="1317801532942" size="66728" optimizedsize="40851">
      <def id="org.alivepdf.pdf:PDF" />
      <pre id="flash.events:IEventDispatcher" />
      <pre id="Object" />
      <dep id="flash.utils:ByteArray" />
      <dep id="Math" />
      <dep id="org.alivepdf.images:DoTIFFImage" />
      <dep id="org.alivepdf.images:ColorSpace" />
      <dep id="org.alivepdf.images:PDFImage" />
      <dep id="org.alivepdf.images:PNGImage" />
      <dep id="flash.display:Shape" />
      <dep id="org.alivepdf.pages:Page" />
      <dep id="org.alivepdf.layout:Size" />
      <dep id="org.alivepdf.images:GIFImage" />
      <dep id="Date" />
      <dep id="flash.geom:Matrix" />
      <dep id="org.alivepdf.links:Outline" />
      <dep id="org.alivepdf.colors:IColor" />
      <dep id="org.alivepdf.layout:Resize" />
      <dep id="org.alivepdf.links:HTTPLink" />
      <dep id="org.alivepdf.html:HTMLTag" />
      <dep id="org.alivepdf.links:ILink" />
      <dep id="org.alivepdf.drawing:DashedLine" />
      <dep id="flash.geom:Rectangle" />
      <dep id="org.alivepdf.encoding:Base64" />
      <dep id="org.alivepdf.colors:SpotColor" />
      <dep id="flash.net:navigateToURL" />
      <dep id="org.alivepdf.operators:Drawing" />
      <dep id="org.alivepdf.events:ProcessingEvent" />
      <dep id="XMLList" />
      <dep id="flash.geom:Point" />
      <dep id="org.alivepdf.images:JPEGImage" />
      <dep id="org.alivepdf.layout:Mode" />
      <dep id="org.alivepdf.images:DoJPEGImage" />
      <dep id="flash.system:Capabilities" />
      <dep id="flash.display:DisplayObject" />
      <dep id="org.alivepdf.data:Grid" />
      <dep id="org.alivepdf.data:GridColumn" />
      <dep id="org.alivepdf.fonts:EmbeddedFont" />
      <dep id="org.alivepdf.annotations:TextAnnotation" />
      <dep id="org.alivepdf.images:TIFFImage" />
      <dep id="flash.events:Event" />
      <dep id="org.alivepdf.links:InternalLink" />
      <dep id="org.alivepdf.drawing:WindingRule" />
      <dep id="org.alivepdf.fonts:FontType" />
      <dep id="flash.display:BitmapData" />
      <dep id="org.alivepdf.fonts:IFont" />
      <dep id="org.alivepdf.colors:GrayColor" />
      <dep id="org.alivepdf.colors:CMYKColor" />
      <dep id="flash.net:URLRequestMethod" />
      <dep id="org.alivepdf.fonts:FontMetrics" />
      <dep id="org.alivepdf.cells:CellVO" />
      <dep id="org.alivepdf.decoding:Filter" />
      <dep id="org.alivepdf.annotations:Annotation" />
      <dep id="org.alivepdf.images:DoPNGImage" />
      <dep id="AS3" />
      <dep id="org.alivepdf.annotations:MovieAnnotation" />
      <dep id="org.alivepdf.layout:Position" />
      <dep id="org.alivepdf.display:Display" />
      <dep id="flash.utils:Dictionary" />
      <dep id="org.alivepdf.images.gif.player:GIFPlayer" />
      <dep id="org.alivepdf.display:PageMode" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="org.alivepdf.images:ImageFormat" />
      <dep id="RangeError" />
      <dep id="org.alivepdf.encoding:PNGEncoder" />
      <dep id="org.alivepdf.encoding:TIFFEncoder" />
      <dep id="flash.net:URLRequest" />
      <dep id="org.alivepdf.tools:sprintf" />
      <dep id="flash.utils:getTimer" />
      <dep id="org.alivepdf.fonts:CoreFont" />
      <dep id="org.alivepdf.events:PageEvent" />
      <dep id="Error" />
      <dep id="flash.net:URLRequestHeader" />
      <dep id="org.alivepdf.encoding:JPEGEncoder" />
      <dep id="flash.events:EventDispatcher" />
      <dep id="org.alivepdf.fonts:FontFamily" />
      <dep id="org.alivepdf.layout:Layout" />
      <dep id="org.alivepdf.visibility:Visibility" />
      <dep id="flash.utils:Endian" />
      <dep id="org.alivepdf.saving:Method" />
      <dep id="org.alivepdf.fonts:FontDescription" />
      <dep id="XML" />
      <dep id="org.alivepdf.layout:Unit" />
      <dep id="org.alivepdf.colors:RGBColor" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/events/PagingEvent)" mod="1264282454000" size="681" optimizedsize="320">
      <def id="org.alivepdf.events:PagingEvent" />
      <pre id="flash.events:Event" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\reports\PmsAppraisalReport.as" mod="1329369707767" size="24879" optimizedsize="17825">
      <def id="modules.reports:PmsAppraisalReport" />
      <pre id="flash.events:IEventDispatcher" />
      <pre id="modules.reports:BasePmsReport" />
      <pre id="interfaces:IDisposable" />
      <dep id="flash.events:Event" />
      <dep id="flash.utils:ByteArray" />
      <dep id="flash.display:BitmapData" />
      <dep id="models:AppraisalNotes" />
      <dep id="mx.utils:StringUtil" />
      <dep id="models:Scoring" />
      <dep id="Math" />
      <dep id="modules.models:PdfItem" />
      <dep id="models:GenericQuery" />
      <dep id="org.alivepdf.images:ColorSpace" />
      <dep id="uccore.utils:DateParser" />
      <dep id="mx.formatters:NumberFormatter" />
      <dep id="AS3" />
      <dep id="org.alivepdf.layout:Position" />
      <dep id="org.alivepdf.layout:Resize" />
      <dep id="mx.events:PropertyChangeEvent" />
      <dep id="flash.utils:Dictionary" />
      <dep id="helpers:Translation" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="mx.core:BitmapAsset" />
      <dep id="models:Globals" />
      <dep id="org.alivepdf.drawing:Joint" />
      <dep id="org.alivepdf.events:PageEvent" />
      <dep id="models:DevelopmentPlan" />
      <dep id="models:AppraisalDetail" />
      <dep id="org.alivepdf.fonts:Style" />
      <dep id="mx.collections:ArrayCollection" />
      <dep id="org.alivepdf.encoding:JPEGEncoder" />
      <dep id="flash.events:EventDispatcher" />
      <dep id="org.alivepdf.layout:Mode" />
      <dep id="mx.formatters:NumberBaseRoundType" />
      <dep id="org.alivepdf.data:Grid" />
      <dep id="org.alivepdf.data:GridColumn" />
      <dep id="org.alivepdf.colors:RGBColor" />
      <dep id="modules.reports:PmsAppraisalReport_icon_report_ok" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/saving/Method)" mod="1264282452000" size="550" optimizedsize="266">
      <def id="org.alivepdf.saving:Method" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/events/ProcessingEvent)" mod="1264282454000" size="876" optimizedsize="444">
      <def id="org.alivepdf.events:ProcessingEvent" />
      <pre id="flash.events:Event" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/encoding/Base64)" mod="1264282452000" size="3130" optimizedsize="1666">
      <def id="org.alivepdf.encoding:Base64" />
      <pre id="Object" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="Math" />
      <dep id="flash.utils:Dictionary" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/layout/Orientation)" mod="1264282456000" size="546" optimizedsize="258">
      <def id="org.alivepdf.layout:Orientation" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_KOI8U)" mod="1264282452000" size="748" optimizedsize="247">
      <def id="org.alivepdf.fonts:CodePage_KOI8U" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/layout/Align)" mod="1308306276705" size="650" optimizedsize="319">
      <def id="org.alivepdf.layout:Align" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\rpc_rb.swc$locale/en_US/messaging.properties" mod="1330491712835" size="6422" optimizedsize="6242">
      <def id="fr_FR$messaging_properties" />
      <def id="en_US$messaging_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/FontFamily)" mod="1264282452000" size="1307" optimizedsize="801">
      <def id="org.alivepdf.fonts:FontFamily" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/gif/events/FrameEvent)" mod="1264282454000" size="805" optimizedsize="391">
      <def id="org.alivepdf.images.gif.events:FrameEvent" />
      <pre id="flash.events:Event" />
      <dep id="AS3" />
      <dep id="org.alivepdf.images.gif.frames:GIFFrame" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\reports\PmsBlankReport.as" mod="1302697108152" size="5236" optimizedsize="3486">
      <def id="modules.reports:PmsBlankReport" />
      <pre id="modules.reports:BasePmsReport" />
      <pre id="interfaces:IDisposable" />
      <dep id="mx.collections:ArrayCollection" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="org.alivepdf.fonts:Style" />
      <dep id="models:Item" />
      <dep id="models:Family" />
      <dep id="AS3" />
      <dep id="mx.utils:StringUtil" />
      <dep id="models:Scoring" />
      <dep id="Math" />
      <dep id="modules.models:PdfItem" />
      <dep id="org.alivepdf.colors:RGBColor" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/gif/events/GIFPlayerEvent)" mod="1264282454000" size="806" optimizedsize="373">
      <def id="org.alivepdf.images.gif.events:GIFPlayerEvent" />
      <pre id="flash.events:Event" />
      <dep id="AS3" />
      <dep id="flash.geom:Rectangle" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\automation_rb.swc$locale/en_US/collections.propert ies" mod="1330491712183" size="1555" optimizedsize="1484">
      <def id="en_US$collections_properties" />
      <def id="fr_FR$collections_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/gif/player/GIFPlayer)" mod="1264282454000" size="5820" optimizedsize="3442">
      <def id="org.alivepdf.images.gif.player:GIFPlayer" />
      <pre id="flash.display:Bitmap" />
      <dep id="flash.events:Event" />
      <dep id="RangeError" />
      <dep id="org.alivepdf.images.gif.events:TimeoutEvent" />
      <dep id="flash.utils:ByteArray" />
      <dep id="flash.display:BitmapData" />
      <dep id="flash.net:URLRequest" />
      <dep id="org.alivepdf.images.gif.events:GIFPlayerEvent" />
      <dep id="flash.errors:ScriptTimeoutError" />
      <dep id="org.alivepdf.images.gif.frames:GIFFrame" />
      <dep id="flash.events:IOErrorEvent" />
      <dep id="org.alivepdf.images.gif.errors:FileTypeError" />
      <dep id="Error" />
      <dep id="org.alivepdf.images.gif.events:FrameEvent" />
      <dep id="flash.net:URLLoaderDataFormat" />
      <dep id="AS3" />
      <dep id="org.alivepdf.images.gif.events:FileTypeEvent" />
      <dep id="flash.utils:Timer" />
      <dep id="flash.events:TimerEvent" />
      <dep id="flash.net:URLLoader" />
      <dep id="org.alivepdf.images.gif.decoder:GIFDecoder" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/decoding/Filter)" mod="1264282454000" size="586" optimizedsize="296">
      <def id="org.alivepdf.decoding:Filter" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_CP1257)" mod="1264282452000" size="754" optimizedsize="249">
      <def id="org.alivepdf.fonts:CodePage_CP1257" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/events/RSLEvent)" mod="1308335063487" size="1272" optimizedsize="735">
      <def id="mx.events:RSLEvent" />
      <pre id="flash.events:ProgressEvent" />
      <dep id="flash.events:Event" />
      <dep id="flash.net:URLRequest" />
      <dep id="AS3" />
      <dep id="flash.display:LoaderInfo" />
      <dep id="mx.core:mx_internal" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/utils/StringUtil)" mod="1308335055408" size="1699" optimizedsize="953">
      <def id="mx.utils:StringUtil" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="mx.core:mx_internal" />
      <dep id="RegExp" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/gif/frames/GIFFrame)" mod="1264282454000" size="609" optimizedsize="278">
      <def id="org.alivepdf.images.gif.frames:GIFFrame" />
      <pre id="Object" />
      <dep id="flash.display:BitmapData" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/JPEGImage)" mod="1265035468000" size="2427" optimizedsize="1489">
      <def id="org.alivepdf.images:JPEGImage" />
      <pre id="org.alivepdf.images:PDFImage" />
      <dep id="org.alivepdf.decoding:Filter" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="org.alivepdf.images:ColorSpace" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/export/Export)" mod="1264282452000" size="453" optimizedsize="203">
      <def id="org.alivepdf.export:Export" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/resources/LocaleSorter)" mod="1308335066940" size="10128" optimizedsize="6820">
      <def id="mx.resources:LocaleSorter" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="mx.core:mx_internal" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/links/Outline)" mod="1264282450000" size="859" optimizedsize="424">
      <def id="org.alivepdf.links:Outline" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\framework_rb.swc$locale/en_US/logging.properties" mod="1330491712230" size="898" optimizedsize="851">
      <def id="fr_FR$logging_properties" />
      <def id="en_US$logging_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/encoding/JPEGEncoder)" mod="1264282452000" size="13095" optimizedsize="7727">
      <def id="org.alivepdf.encoding:JPEGEncoder" />
      <pre id="Object" />
      <dep id="org.alivepdf.encoding:BitString" />
      <dep id="flash.display:BitmapData" />
      <dep id="flash.utils:ByteArray" />
      <dep id="AS3" />
      <dep id="org.alivepdf.encoding:IntList" />
      <dep id="org.alivepdf.encoding:IntBlock" />
      <dep id="flash.filters:ColorMatrixFilter" />
      <dep id="flash.geom:Point" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\locale\en_US\automation_agent_rb.swc$locale/en_US/styles.proper ties" mod="1330491712260" size="445" optimizedsize="408">
      <def id="en_US$styles_properties" />
      <def id="fr_FR$styles_properties" />
      <pre id="mx.resources:ResourceBundle" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/display/Display)" mod="1264282454000" size="618" optimizedsize="310">
      <def id="org.alivepdf.display:Display" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\reports\PmsGraphsReport.as" mod="1302697108143" size="3971" optimizedsize="2709">
      <def id="modules.reports:PmsGraphsReport" />
      <pre id="modules.reports:BasePmsReport" />
      <pre id="interfaces:IDisposable" />
      <dep id="mx.collections:ArrayCollection" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="org.alivepdf.fonts:Style" />
      <dep id="org.alivepdf.layout:Mode" />
      <dep id="Date" />
      <dep id="AS3" />
      <dep id="org.alivepdf.layout:Position" />
      <dep id="modules.models:PdfItem" />
      <dep id="org.alivepdf.layout:Resize" />
      <dep id="uccore.utils:DateParser" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_CP1258)" mod="1264282452000" size="754" optimizedsize="249">
      <def id="org.alivepdf.fonts:CodePage_CP1258" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Program Files\Adobe Flash Builder 4.6\sdks\3.6.0\frameworks\libs\framework.swc(mx/resources/IResourceManager)" mod="1308335067002" size="3595" optimizedsize="1031">
      <def id="mx.resources:IResourceManager" />
      <pre id="flash.events:IEventDispatcher" />
      <pre id="Object" />
      <dep id="flash.system:SecurityDomain" />
      <dep id="AS3" />
      <dep id="mx.resources:IResourceBundle" />
      <dep id="flash.system:ApplicationDomain" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\helpers\CustPDF.as" mod="1308544824310" size="1422" optimizedsize="942">
      <def id="modules.helpers:CustPDF" />
      <pre id="org.alivepdf.pdf:PDF" />
      <dep id="org.alivepdf.layout:Size" />
      <dep id="org.alivepdf.layout:Align" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/images/ImageFormat)" mod="1264282454000" size="552" optimizedsize="248">
      <def id="org.alivepdf.images:ImageFormat" />
      <pre id="Object" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/colors/SpotColor)" mod="1264282454000" size="646" optimizedsize="313">
      <def id="org.alivepdf.colors:SpotColor" />
      <pre id="org.alivepdf.colors:IColor" />
      <pre id="Object" />
      <dep id="AS3" />
      <dep id="org.alivepdf.colors:CMYKColor" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/fonts/CodePage_CP1251)" mod="1264282452000" size="753" optimizedsize="249">
      <def id="org.alivepdf.fonts:CodePage_CP1251" />
      <pre id="mx.core:ByteArrayAsset" />
      <dep id="AS3" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\src\modules\PmsReport.as" mod="1316150559806" size="1365" optimizedsize="895">
      <def id="modules:PmsReport" />
      <pre id="modules.interfaces:IUniModule" />
      <pre id="mx.modules:ModuleBase" />
      <pre id="interfaces:IDisposable" />
      <dep id="modules.reports:PmsAppraisalReport" />
      <dep id="modules.reports:PmsBlankReport" />
      <dep id="AS3" />
      <dep id="modules.reports:PmsAnnexReport" />
      <dep id="modules.interfaces:IPdfReport" />
      <dep id="flash.utils:getDefinitionByName" />
      <dep id="modules.reports:PmsGraphsReport" />
      <dep id="modules.reports:Pms360Report" />
      <dep id="modules.reports:PmsMergedReferenceReport" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/data/Grid)" mod="1308555326771" size="2876" optimizedsize="1409">
      <def id="org.alivepdf.data:Grid" />
      <pre id="Object" />
      <dep id="org.alivepdf.export:Export" />
      <dep id="flash.utils:ByteArray" />
      <dep id="org.alivepdf.serializer:ISerializer" />
      <dep id="AS3" />
      <dep id="org.alivepdf.export:CSVExport" />
      <dep id="org.alivepdf.colors:IColor" />
    </script>
    <script name="D:\Dev\Flex 4.6\my_project\libs\AlivePDF.swc(org/alivepdf/encoding/

Layout Positioning

Similar Messages

Maybe you are looking for