EventListener function specific to generated display object container

This has to be simple, if only I knew how. I'm an AS3 newbie,
and am having difficulty setting up multiple specific
EventListeners within a code generated display object container.
I am generating a 'page' (Sprite) with a heap of 'cards'
(Sprites) on it. Each of those cards, in turn, contains a selection
of text boxes and other objects generated from database output
using a 'for' loop.
My hope is to attach an EventListener to each 'card' so that
a MouseEvent will let me manipulate the data that lead to the
content of that actual card (the i-th iteration of my for loop).
I've been playing with everything I can think of (limited
repertoire of thoughts though) and the best I've managed is for my
EventListener to access the final set of data, whichever 'card' I
click on.
I've summarised and attached my code for the function, and
would appreciate any advice (however basic) on how to get back to
the i-set of data from the EventListener attached to the i-th card.
I can handle the PHP and MySQL side of things but am fumbling my
way into the OOP of AS3.
Cheers
Dougal

Another way would be to extend Sprite and add an id value.
Something like:
package{
import flash.display.Sprite;
public class MySprite extends Sprite {
private var _id:int;
public function MySprite(id:int){ _id = id; }
public function get id():int { return _id; }
And then in your code you'd just make instance of MySprite,
passing it i:
// build the cards and text boxes and add them to the
reviewPage
for (var i:int = 1; i < (cardsRequired+1); i++) {
// setup the locations for all the objects
var displayCard:Sprite = new MySprite(i);
You can then get i in the event listener function by using
the id getter:
function accessThisData(e:MouseEvent):void{
trace(e.target.parent.id);
Dave -
www.offroadfire.com
Head Developer
http://www.blurredistinction.com
Adobe Community Expert
http://www.adobe.com/communities/experts/

Similar Messages

  • [svn:fx-trunk] 6350: Remove sharing restriction on display object container being a group with BasicLayout .

    Revision: 6350
    Author:   [email protected]
    Date:     2009-04-28 12:57:53 -0700 (Tue, 28 Apr 2009)
    Log Message:

    FYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989

  • Functional specifications for sales reports

    Hi
    please kindly give me some functional specifications to generate sales reports
    Regards
    srinivas

    Srinivas,
    This is a very vague question.
    There are 'n' number of sales reports.
    You would need to explain your question and business scenario in detail to get the best solution here.
    -Maverick

  • IDOC : Message Function 003: Delete Object contains message to be deleted.

    Hi,
    I am trying to process a Customer master Icreation DOC (OILDEB06) which has a Message function 003: with the description Delete Object contains message to be deleted.
    I am testing my IDOC, when should I be using this message function.
    If you can detail with the example,
    it does not mark the customer for deletion for sure. when it is recommended to use this message function.
    Thanks
    Regards

    yes   your object was  locked  in the  another session ... please  close  all the  remaining sessions  ...
    and for cross check  in  SM12   tcode   ....see the  lock list  ...delete  all the list  ...
    now you can  delete the object from the  list ..
    it happens  some  times  for all   ... when you work  with multiple sessions.
    reward points  if is is usefull .
    Girish

  • Applying a filter to multiple display objects

    I have a large amount of btn's that load full size images when clicked. I simply want to add a filter, scaleX and scaleY to each of those buttons and  I know there is a better method then typing each btn name with an eventListener for the Mouse_Over and Mouse_Out events. I understand that I need to create a variable of a new filter and then apply it to the display object. Like so..
    var glow:GlowFilter = new GlowFilter(0x0066FF, 1, 10, 10);
    function hover(event:MouseEvent):void
    pic1_btn.filter = new Array(glow);
    pic1_btn.scaleX = 1.02;
    pic1_btn.scaleY = 1.02;
    pic1_btn.addEventListener(MouseEvent.MOUSE_OVER, hover);
    function noHover(event:MouseEvent):void
    pic1_btn.filter = new Array();
    pic1_btn.scaleX = 1;
    pic1_btn.scaleY = 1;
    pic1_btn.addEventListener(MouseEvent.MOUSE_OUT, noHover);
    So if I were to continue this, I would have to type out pic1_btn, pic2_btn, pic3_btn and so on to apply a filter to each object and also type out the object name for each listener. NUTS! So my question is what is the best way to approach this? Thanks for your help.

    Thank you for that information yesterday, it was really helpful.
    OK so what I have is a pretty simple album. At the top of hierarchy I have a file named "loader.swf" that requires a password and then loads the "album.swf" then depending on the button that is selected on the "album.swf" an additional .swf is loaded. These additional .swf's contain the thumbnail buttons which we are discussing and when those buttons are clicked an external full size .jpg is loaded. Following are the actions from the main timeline.
    var picLoader:Loader = new Loader();
    bar_mc.alpha = 0;
    function progressHandler(event:ProgressEvent):void
          var myprogress:Number = event.target.bytesLoaded/event.target.bytesTotal;
          addChild(bar_mc);
          addChild(myTextField_txt);
          bar_mc.alpha = 100;
          bar_mc.scaleY = myprogress;
          myTextField_txt.text = Math.round(myprogress*100)+"%";
    picLoader.contentLoaderInfo.addEventListener(ProgressEvent.PROGRESS, progressHandler);
    function imageLoaded(event:Event):void
          addChild(picLoader);
          removeChild(myTextField_txt);
          removeChild(bar_mc);
          picLoader.x = (stage.stageWidth - picLoader.width)/2;
          picLoader.y = (stage.stageHeight - picLoader.height)/2;
    picLoader.contentLoaderInfo.addEventListener(Event.COMPLETE, imageLoaded);
    function removeFull(event:MouseEvent):void
          picLoader.unload();
          removeChild(picLoader);
    picLoader.addEventListener(MouseEvent.CLICK, removeFull);
    On the main timeline I have an instance of a movie clip called "mcThumbs". Within this movieclip I have different pages on different layers and 12 thumbnails per page.
    And the actions for mcThumbs
    stop();
    function picClick(event:MouseEvent):void
          this.parent.picLoader.load(new URLRequest(event.target.name + ".jpg"));
    for(var a:uint=1; a<=76; a++)
          this["newborn"+String(a)].addEventListener(MouseEvent.CLICK, picClick);
    function hover(event:MouseEvent):void
          event.currentTarget.scaleX = 1.02;
          event.currentTarget.scaleY = 1.02;
    function noHover(event:MouseEvent):void
          event.currentTarget.scaleX = 1;
          event.currentTarget.scaleY = 1;
    for(var i:uint=1; i<=76; i++)
          this["newborn"+String(i)].addEventListener(MouseEvent.MOUSE_OVER, hover);
          this["newborn"+String(i)].addEventListener(MouseEvent.MOUSE_OUT, noHover);
    function goBack(event:MouseEvent):void
          if(currentFrame == 1)
                gotoAndStop(totalFrames);
          else
                prevFrame();
    function goForward(event:MouseEvent):void
          if(currentFrame == totalFrames)
                gotoAndStop(1);
          else
                nextFrame();
    prev_btn.addEventListener(MouseEvent.CLICK, goBack);
    next_btn.addEventListener(MouseEvent.CLICK, goForward);
    This is where the issue arises. If you hover over a thumbnail button and then go to an different page, that same thumbnail button will remain visible behind the thumbnails of that page.

  • Smart Form Functional Specification

    Hi Gurus,
    I have to design a smart form functional specification, but i don't have any idea about how to prepare the functional specification?
    can anybody send me the smart form functional specification template ?
    which helps me to prepare the specification

    Hi Devi,
    Here is the FS for Form,
    Functional Specification Document for Forms
    Authors     
    Approved By     
    TABLE OF CONTENTS
    1     OVERVIEW SECTION:     3
    1.1     DOCUMENT OVERVIEW:     3
    1.2     REVISION HISTORY:     3
    1.3     OPEN ISSUES:     3
    1.4     EXTERNAL REFERENCES:     3
    1.5     REQUEST OVERVIEW:     3
    1.6     GENERAL PROCESSING REQUIREMENTS:     4
    2     BUSINESS/FUNCTIONAL REQUIREMENTS     5
    2.1     REQUIREMENT DESCRIPTIONS:     5
    2.2     BUSINESS DRIVER     5
    2.3     TO-BE BUSINESS PROCESS:     5
    2.4     TO-BE BUSINESS PROCESS FLOW DIAGRAM:     5
    2.5     ASSUMPTIONS:     5
    2.6     DEPENDENCIES:     5
    2.7     RISKS:     5
    2.8     SECURITY:     6
    2.9     OTHER REQUIREMENTS:     6
    3     FORM SECTION     7
    3.1     REPORT SELECTION SCREEN:     7
    3.2     STANDARD FORM NAME:     7
    3.3     FORM LAYOUT:     7
    3.4     DATA SOURCE:     7
    3.5     SPECIAL REQUIREMENTS PROCESSING:     7
    3.6     HOW TO EXECUTE THE FORM:     8
    4     UNIT TEST PLAN SECTION     9
    4.1     FUNCTIONAL UNIT TEST PLAN:     9
    5     USER GUIDE REQUIREMENTS     10
    5.1     USER GUIDE REQUIREMENTS:     10
    6     APPENDIX     11
    6.1     APPENDIX:     11
    1     Overview Section:
    1.1     Document Overview:
    (Provide the high level identification information about the object to be developed. Id, title, Release etc)
    Project      Project Atlas
    Development Object ID:     SC-F-125
    Development Object Title:     Purchase Order Form
    Release:     
    Process Team:     Supply Chain
    Process Area:     Procure-to-Pay
    1.2     Revision History:
    {This section should be filled with other details about the owner of functional specs, current status of document as explained in the status key etc}
    Date Modified     Version     Modified By     Description of Change(s)
    1.3     Open Issues:
    (Any open issues should be reported in this section)
    Issue #     Issue Date     Issue Title / Description     Priority     Resolved Date     Any Other Comments
    1.4     External References: 
    (Identify any documents referenced in any part of this document.  (Attach documents where possible.)
    Document Title     Filename     Author     Identifier (Version/Date)
    Process Flow diagram      N/A          
    Screen Shots if any     N/A          
    Sample data file     PO Form Layout (Single Page)     Erik Kraus     1/ (10/11/2006)
    Sample data file     PO Form Layout (Multiple Pages)     Erik Kraus     1/ (10/11/2006)
    1.5     Request Overview:
    Complexity     0   High
    1   Medium
    0   Low
    System(s) Impacted     1   R/3
    0   CRM
    0   BW

         0   Other
    Existing SAP transaction(s) involved?     ME22N, ME23N
    New SAP transaction(s) involved?     ME22N; then click “Messages” to print or “Print Preview” to view.
    Menu path for transaction(s)     Logistics &#61664; Materials Management &#61664; Purchasing &#61664; Change
    1.6     General Processing Requirements:
    (Check the appropriate boxes for e.g. if the development object is an batch report that runs monthly, then check the Online and Monthly boxes in the Processing mode and frequency section and also provide the expected data volume if known)
    Processing Mode:     1   Online
    0   Batch
    Frequency     0   Annually
    0   Quarterly
    0   Monthly
    1   Daily
         1   Real Time 
    1   Ad-Hoc
    1   Others
    Expected Data Volume     
    2     Business/Functional Requirements
    Section 2 describes what is needed.  This information is used to build the design (how to do it) in Sections 3 and on
    2.1     Requirement Descriptions:
    Describe the purpose of the object.  Brief overview
    The purchase order form is used to display the purchase order in SAP. This form can also be sent to the supplier via e-mail or fax in SAP. The PO can also be displayed in the “Print Preview” screen and printed out as well.
    2.2     Business Driver
    The PO Form is standard in SAP. Modifications to the form will be necessary to meet the needs of the purchasing organizations at Sage. The PO form is necessary so that all the details of the purchase order can be faxed/ emailed to the supplier and also can be printed out into a hard copy form for internal purposes. The PO form also needs to be able to be viewed via the print preview icon in SAP.
    2.3     To-Be business process:
    Describe the To-Be business process
    Customized Sage Purchase Order Form.
    2.4     To-Be business process flow diagram:
    Describe the To-Be business process flow diagram
    N/A
    2.5     Assumptions:
    List all the assumptions that were made when developing this object
    1)     Standard SAP PO Form will need to be modified from its standard layout.
    2)     Font for Purchase Order form will be Times New Roman
    3)     PO Form will be created in English
    2.6     Dependencies:
    List all the dependencies that were made when developing this object
    N/A
    2.7     Risks: 
    (What are the risks that make this development unique?  What risks need to be proactively dealt with in order to be successful? What data sources are needed but not readily available?  Are there any risks or concerns that make this development out of the ordinary?)
    N/A
    2.8     Security: 
    (Any security requirement for this object)
    2.9     Other Requirements: 
    (If there are any other requirement which is not covered under section 2)
    N/A
    3     Form Section
    Type:      0  SAP Script     1  Smart forms   
    3.1     Report Selection Screen: 
    Describe the selection screen of the program.  Specify fields for selection and what checks are needed after the user has entered their criteria.
    Field Name     Select Options / Parameters / Radio Buttons / Check Boxes     Default Values
    From – To     Validation
         Required /Optional     F4 Values
    N/A     N/A     N/A     N/A     N/A     N/A
    3.2     Standard form name: 
    Give the name of the SAP Script or Smart form name if copied from SAP
    “MEDRUCK” Form in SAP
    3.3     Form Layout: 
    Describe the form layout for each page.
    The PO form will contain information at the Header Level, Item Level, and Authorizations levels.
    Header Level:
    The header level will contain all the supplier, bill-to party/address, and ship-to party/address information.  The header level will also contain the payment and shipping terms, logo, page number, purchase order title, purchase order number, supplier number in SAP, and the PO date.
    Item Level:
    The item level will contain the item number, material and description, order unit, quantities, date required, unit cost, and the total amount of the line-item.  The item-level will also contain the line-item text of purchase order.
    Authorization:
    The authorization section of the form will contain the name, telephone number, and email address of the purchasing agent.
    Other:
    -The Total Amount and Currency will be displayed to the right of the Authorization information.
    -The layout will include sections and fields with borders. For example the Ship-To, Bill-To, and Supplier will be enclosed in rounded edge boxes. The Layout can be viewed in the Attachments section:
    portion of section 3.4. which will show an example of  a PO with only one page and a PO with multiple pages.
    3.4     Data Source: 
    Identify the data that has to be appeared in the forms. Table Name-Field Name
    All the fields will be available on the SAP standard form “MEDRUCK”. Any additional fields that are not on the standard form will need to be added.  The mapping for additional fields not in the standard form will be shown below in each section (Header Level, Item-Level, and Authoriztions) if required.
    Please see below for the required fields in the form:
    This Section will contain details on the Header, Line-Item, and Authorization sections of the form. A section for attachements will also be inlcuded at the end.
    I. Header Information:
    The following fields will be displayed for the header information.
    -     Title: Purchase Order
    -     Logo: The Sage Software logo will appear in the top left corner of the form.
    -     PO Creation Date (MM/DD/YYYY)
    -     Supplier Number
    -     PO Number
    -     Page Number
    -     Bill to Name and Address
    -     Supplier Name and Address
    -     Ship to Name and Adress
    -     Payment Terms: (not on standard form, see field mapping section below)
    -     Shipping Terms: (not on standard form, see field mapping section below). The shipping terms are the same as the “incoterms” in SAP. There are two fields for the incoterms and both will be used for the shipping terms.
    -     Header Text
    Additional Notes for Header Fields:
    PO creation date should be in format “MM/DD/YYYY”
    Page Number should be in format “Page 1 of 1, Page 2 of 3, etc” format
    The “Bill To” name and address will come from the company code  that is assigned to the plant in the purchase order.
    The “Ship To” name and address will come from the storage location in the first line-item on the purchase order if the “SC Vendor” box is not checked on the delivery address tab of the purchase order. If the “SC Vendor” box is checked on the delivery address tab, then the “Ship To” address will come from the delivery address tab on the purhcase order from the central address management system.
    The “Supplier” name and address will come from the vendor master in the purchase order.
    The central address management system will need to be queried when looking up the “Bill To”, “Deliver”, and “Supplier” addresses.
    Header Text: The text to be inserted here will be pulled from the Header Text in the purchase order.
    Example: Text is pulled from the Header text with the green checkmark.
    If the PO Form requires additional pages, then the header information should be duplicated on the subsequent pages.
    Additional Fields :
    Field Mapping for additional header fields that are not on the Standard SAP PO (MEDRUCK) Form . These fields can also be viewed on the PO Forms in the Attachments section.
    PO Form Additional  Fields
    Field Name     SAP Table/ Field Name
    Payment Terms     MEPO1226-ZTERM
    Shipping Terms (incoterms1)     MEPO1226-INCO1
    Shipping Terms (incoterms 2)     MEPO1226-INCO2
    II. Item Level Information
    The following fields will be on the PO form for the item-level:
    -     Item Number
    -     Material
    -     Material Description
    -     Unit (Unit of Measure)
    -     Quantity
    -     Date Req’d (MM/DD/YYYY)
    -     Unit Cost
    -     Amount
    Each field will have an allotted amount of characters, so that all the text can fit on the line-item. Using .5 inch margins with times new roman 10pt font; there are 105 possible characters in microsoft word for the line-item details to fit on the line. The fields are broken down as follows with their allotted characters to accommodate the 105 allowed spaces:
    Characters:
    Item Number:  1-3
    Material: 6-18
    Descriptoin: 6-36
    Unit: 39-49
    Quantity: 44-56
    Date Required: 60-69
    Unit Cost: 77-86 (Commas and Delimals will be included in the Price. Two total decimal Spaces)
    Amount: 92-103 (Commas and Delimals will be included in the Price. Two total decimal Spaces)
    The Numbering Ranges above can be viewed below line-item 040 in the “PO Form Outline (Sinlge Page)” document in the Attachments section.
    Note: These number ranges are shown as an example of what the form should like. They do not have to match up identicle to the specifications listed above.
    Additional Notes for Line-Item Fields:
    - Material Description will be displayed directly below the Material on the next line.
    - Item Text: The Item text will be displayed if there are any item texts from the Purchase order. The text will be displayed two lines below the Material description. So there will be one line without any text. Also, the next line-item on the PO form will be displayed  two lines below the item-level text; so there will be only one line with no text between the line-item with text and the subsequent line-item.  Line items 020 and 030 depict this in the “PO Form Outline_v1” document in the attachments section. The Line Item text will come from the “Material PO text” (identified below with a green checkmark) from the line-item on the purchase order as shown below.
    - The Date Required Format will be “MM/DD/YYYY”.
    - For every item in the purchase order, the program should loop through each item and check to see if the “returns item” box is checked (MEPO1211-RETPO). If this box is flagged on the purchase order, then the purchase order form needs to be updated with a return indicator. This indicator can be viewed on ‘line-item 030’ of the attached word document ““PO Form Outline (Single Page)” in the Attachments section.
    - The line-item fields should have the following alignment:
    Material: Left
    Material Description: Left
    Unit: Left
    Qty.: Right
    Date Required: Left
    Unit Cost: Right
    Amount: Right
    - If the line-items do not fit on one page, then they should continue on to subsequent pages. The Header information should be copied to all the subsequent pages and the authorization section will be displayed on the last page as well as the total amount and currency. This example can be viewed in document “PO Form Outline (Multiple Pages)” in the Attachments section.
    Dislclaimer:
    A disclaimer will also be included in this section and after all the line-items. The disclaimer text is still pending. An example of a disclaimer is shown in the “PO Form Outline (Single Page)” after line-item 040. This document can be found in the Attachments section.
    If a PO requires multple pages, the the disclaimer will be displayed on the last page after the last line-item.
    III. Authorization Information
    This section will contain the purchasing agent: The purchasing agent will be the person who created the purchase order. This section will also contain their telephone number and email address.
    The first and last name of the person who created the purchase order should be displayed here. This can be looked up in the users profile. The user profile will also contain their email and telephone number.
    The field names for can be viewed below or in the “PO Form Outline (Single Page)” document in the Attachments section.
    PO Form Additional  Fields
    Field Name     SAP Table/ Field Name
    First Name     ADDR3_DATA-NAME_FIRST
    Last Name     ADDR3_DATA-NAME_LAST
    Telephone Number     SZA5_D0700-TEL_NUMBER
    Email     SZA5_D0700-SMTP_ADDR`
    Attachments:
    3.5     Special Requirements Processing: 
    Describe the processing required to support any special requirements (e.g. signatures, logos, OCR, bar coding etc.).
    3.6     How to execute the form: 
    Describe how to trigger the form e.g. Standard SAP transaction code or custom transaction code etc. If standard SAP transaction code describe the menu path
    The form needs to be able to be viewed and printed.
    To View:
    Transaction ME22N or ME23N; Then Click the Print Preview   icon to view the Form.
    To Print:
    1) Transaction  ME22N.
    2) Click Messages
    3) Select Output “NEU” and medium “1 Print output”
    4) Click the “Further data” button as shown in the screen shot above
    5) Select  “4 Send immediately (when saving the application)”
    6) Click Back   then Click Save  
    7) Select “LOCAL” for logical Destination
    8) Click “Save” again  
    4     Unit Test Plan Section
    4.1     Functional Unit Test Plan:
    Document the criteria to be used for validating programming accuracy and positive/ negative results
    Step     Scenario     Expected Results
    Number     Description of what is being tested in this step     Description of what is expected to happen in this step
    1     Go to Transaction ME22N and Display PO Form by clicking the Print Preview Icon     Form should mirror the forms in the Attachments section.
    2     Go to Transaction ME22N and Print PO Form     PO Form should print as showed in the Print Preview Screen and the forms the Attachments section.
    3     Create PO that will force PO form to cross multiple pages and then click Print Preview     PO Form should have Header information on all pages and line-item shoulds continue on to the subsequent pages. Authorization, Total Amount, Currency, and Disclaimer will be on the last page. The page numbers should also be correct and in the right format. This should mirror the “PO Form Outline (Multiple Pages)” document in the Attachments section.
    4     Go to Transaction ME22N and print PO as in step 3     PO Form shoul print as showed in the Print Preview Screen and the “PO Form Outline (Multiple Pages)” document in the Attachments section.
    5     User Guide Requirements
    A User Guide must be provided to assist the person responsible for running the program(s).  The User Guide must be in cookbook-style (required elements with step by step instructions) and annotated screen prints.  The User Guide will be required in the running of the object in the Production environment as well as the QA and Test environments.
    5.1     User guide Requirements:
    N/A
    6     Appendix
    6.1     Appendix:
    N/A
    Hope it will help ..
    Regards,
    Arjun.
    <b>Reward the points if it hepls</b>

  • Is there a way to detect redraw regions or at the very least when a display object is redrawn?

    I have a layered window system that produces Windows 7 Aero Glass effect in Flash.
    It consists of nested display objects, with overlays as so.
    Root [
        GlassWindowTop [
           RenderedEffectBackground
         BackgroundForGlassWindowTop [
             GlassWindowMiddle [
               RenderedEffectBackground
            BackgroundForGlassWindowMiddle [
                 GlassWindowBottom [
                    RenderedEffectBackground
                 BackgroundForGlassWindowBottom (e.g. the DesktopBackground)
    Windows can be raised and lowered by changing their order in the hierarchy and adding new levels.
    Each glass window has a designated background (containing all lower windows) .  It draws to an off-screen Bitmap the region of the background that is under the window, and applies a blur filter, tint, and parallax effects to it, and then displays that as it's own background as RenderedEffectBackground.
    The problem is that "RenderedEffectBackground" is a static rendering of the window background, so in order to update it in real time, I need to detect when it's background display object (e.g. BackgroudnForGlassWindowTop) or any nested display objects are rendered.
    I could simply update all RenderedEffectBackgrounds from the bottom up each frame, but that would be inefficient.   Ideally, I could detect when a particular background changes (e.g. when a textfield cursor is flashing, or a MovieClip changes frames), and then only render from that object up.  The rendering of course always has to take place from back to front, starting with the lowest window that has changed.  If I could detect the redraw regions of the Flash Player (e.g. when a textfield cursor is flashing, or a MovieClip is playing), I could optimize this system even further by checking for layer overlaps and only rendering layers whose windows intersect the redraw regions, but obtaining that level of information would probably not be possible or logical since this this essentially needs to happen during some kind of pre render phase, which Flash may not support.  Such a pre-render phase would itself be causing new redraw regions, but as long as it is processed from the bottom up, it could work.
    Is there any AS3 function of the flash player that allows my code to obtain information about the display list as far as which display objects are due to be rendered, and then intercept some kind of "onRenderComplete" event for them right before rendering takes place so that I can render the higher display objects.
    I originally tried to implement this as a filter, but pixel bender shaders in AS3 don't seem to allow sampling of an underlying object that would allow for blurring (i.e. the shader can access only the current point being rendered, coordinates passed to the sampling methods are ignored (this is documented behavior).
    Any ideas?

    The feature that shows the link you are mousing over hasn't been removed in 29. Maybe the add-on you are using to restore the add-on bar is covering it. I've tested the Classic Theme Restorer and it seems to work correctly in this situation - https://addons.mozilla.org/firefox/addon/classicthemerestorer/

  • Class display objects visible=false

    Hi there,
    I have an app that displays XML as items. I am taking the createLayout() and trying to create a class that i can call from my custom component rather than having tons of code in the same file. The issue i am having is that when i call it, and run/debug, the display objects (text,links,date..) all have their visible property set to false. This happens even though I set the property to true in my code. Please help!
    package com.ryancanulla.utils
         import flash.display.Sprite;
         import flash.events.MouseEvent;
         import flash.net.URLRequest;
         import flash.net.navigateToURL;
         import flash.text.TextFormat;
         import mx.collections.XMLListCollection;
         import mx.containers.Canvas;
         import mx.containers.HBox;
         import mx.containers.VBox;
         import mx.controls.CheckBox;
         import mx.controls.ComboBox;
         import mx.controls.LinkButton;
         import mx.controls.Text;
         public class CreateLayout extends Sprite {
         //     Display Vars
              private var vBox:VBox;
              private var hBox:HBox;
              private var titleText:LinkButton;
              private var itemInfo:Text;
              private var abstract:Text;
              private var archive:CheckBox;
              private var rateItem:ComboBox;
              private var category:ComboBox;
              private var container:VBox;
              private var clickURL:Text;
              private var canvas:Canvas;
              private var titleFormat:TextFormat;
              public function CreateLayout(listCollection:XMLListCollection)
                   listCollection = listCollection;
                   container = new VBox();
                   var categoryLabels:Array = new Array("Health","Industrial","Emerging Tech","Food & Ag");
                   var rateLabels:Array = new Array("Positive","Neutral","Negative");
                   for(var i:int=0; i<listCollection.length; i++) {
                        canvas = new Canvas();
                        hBox = new HBox();
                        titleText = new LinkButton();
                        titleFormat = new TextFormat();
                        itemInfo = new Text();
                        abstract = new Text();
                        archive = new CheckBox();
                        rateItem = new ComboBox();
                        category = new ComboBox();
                        clickURL = new Text();
                        titleText.label = listCollection.getItemAt(i).title;
                        titleText.addEventListener(MouseEvent.CLICK, getURL);
                        titleText.width = 400;
                        clickURL.text = listCollection.getItemAt(i).clickurl;
                        clickURL.visible = false;
                        clickURL.includeInLayout = false;
                        itemInfo.text = listCollection.getItemAt(i).source + " | " + listCollection.getItemAt(i).date;
                        itemInfo.y = 25;
                        abstract.text = listCollection.getItemAt(i).abstract;
                        abstract.y = 42;
                        abstract.visible = true;
                        abstract.includeInLayout = true;
                        abstract.width = 400;
                        abstract.height= 60;;
                        archive.label = "Archive";
                        category.prompt = "Category";
                        category.dataProvider = categoryLabels;
                        category.rowCount = categoryLabels.length;
                        category.visible = false;
                        category.includeInLayout = false;
                        category.width = 95;
                        category.height = 20;
                        rateItem.prompt = "Rate";
                        rateItem.dataProvider = rateLabels;
                        rateItem.visible = false;
                        rateItem.includeInLayout = false;
                        rateItem.width = 95;
                        rateItem.height = 20;
                        canvas.addChild(titleText);
                        canvas.addChild(clickURL);
                        canvas.addChild(itemInfo);
                        canvas.addChild(abstract);
                        canvas.addChild(hBox);
                        hBox.addChild(archive);    
                        hBox.addChild(category);
                        hBox.addChild(rateItem);
                        hBox.y = abstract.y + 60;
                        hBox.percentWidth = 80;
                        hBox.percentHeight = 80;
                        //archive.addEventListener(Event.CHANGE, toggleArchive);    
                        container.addChild(canvas);         
                   container.x = 10;
                   container.y = 10;
                   container.visible = true;
                   addChild(container);
            // Called when someone clicks on the titleLink. This function pulls the
            // origional website URL up in a seperate browser window
            private function getURL(e:MouseEvent):void {
                      var link:LinkButton = e.currentTarget as LinkButton;
                      var canvas:Canvas = link.parent as Canvas;
                      var clickURL:Text = canvas.getChildAt(1) as Text;
                      var url:URLRequest = new URLRequest(clickURL.text);
                      navigateToURL(url);
                   trace(clickURL.text);
    Where I instantiate the class. List collection is an XMLListCollection which contains XML data.
    private var createLayout:CreateLayout;
    createLayout = new CreateLayout(listCollection);

    container is from the Vbox class so I don't see that here and there might be something in there that is causing some problem.
    But I don't think that is the only problem. I think this seems like the same problem that you have going in your other post.
    I don't see anyplace that you addChild your CreateLayout instance. container has been added to your CreateLayout instance, but where is the CreateLayout instance added to some other display list.
    Also it looks like almost everything you add to canvas is set to be invisible. So without knowing what is in a Canvas instance it is hard to know what would show up anyways.

  • Object ID and Object ID Version fields in Displaying Object Properties - XI

    Hi,
    In displaying Object Properties in XI we can see different fields like Type, Description, SCV, Object ID, Object ID Version, Status, Person Responsible, Changed On, Changed By, Display Language, Original Language.
    But when i refer to the SAP Library documentation for these fields, Object ID and Object ID Version are not included. Here is the link for the documentation
    http://help.sap.com/saphelp_nw04/helpdata/en/f0/fc9a3de2ec0753e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_nw04s/helpdata/en/f0/fc9a3de2ec0753e10000000a114084/frameset.htm
    With that said, i have no information on those two fields, only assumptions i've made that i would like to verify in this forum with the questions below
    1.
    Please correct me if i'm wrong, the Object ID is the unique identifier for the object and the Object ID Version is directly connected with the versioning concept for IR and ID, so the Object ID is generated when you create the object  (e.g. MM) and the Object ID Version changes every time that object is edited and change list activated for it. Is this correct?
    Or does the Object ID change every time the object is edited and change list activated for it?
    What is the behavior of these two fields when transported? e.g. dev to qa...  are they both retained on the target IB's?  (specifically for ID objects because the change list needs to be activated first on the target ID)
    2.
    Does any one know where the Object ID and Object ID Version gets stored?  (saved on a table in the ABAP stack or saved somewhere in the Java stack? e.g. can be viewed in Visual Admin or a URL)  I am thinking of extracting all the XI objects with their corresponding Object ID and Object ID Version (per system) in one step.  I know this is possible only if the Object ID & Object ID Version are stored in an ABAP table...
    Kindly give me some inputs.
    Please answer directly with the questions above. I will reward points for it.
    Thanks in advance.

    HI,
    >Please correct me if i'm wrong, the Object ID is the unique identifier for the object and the Object ID Version is directly connected with the versioning concept for IR and ID, so the Object ID is generated when you create the object (e.g. MM) and the Object ID Version changes every time that object is edited and change list activated for it. Is this correct?
    The Object Id is created the first time you create the object.
    Object Version Id is created the first time you save/activate a object.
    Now suppose if you modify the object a new Object Version Id will be created but the Object ID will remain the same.
    For IR Objects the Object Id & Object Version ID will remain the same across systems.
    For ID Objects the Object Id & Object Version ID is not the same across systems.
    Not sure about the table. Can you try in SE11 and check all tables with SXMS*. Could be also that tables might not be available from GUI i.e you might have to login to DB to find out.
    Regards,
    Sumit

  • JNI - Passing an object containing an array field

    I need to pass an object to a native method. The object contains several int fields and a field that is an int array (contains 32 int).
    I have no problem with the int fields, but do not know how to access the int array field in the C code. What approach should be used to get/set values in the int array field?
    Any suggestions are appreciated.

    I have been reading up on the subject, but I guess I'm just an idiot. If all the answers were obvious from reading the specification then there wouldn't be much point to this forum.
    For int fields in the object passed to the native function I do the following to set the value:
    fid = (*env)->GetFieldID(env, cls, "intFieldName", "I");
    (*env)->SetIntField(env, myObj, fid, newValue);
    For a field that is an array of int, it seems that I can get the field ID as follows:
    fid = (*env)->GetFieldID(env, cls, "arrayFieldName", "[I");
    The "Get<Type>Field" and "Set<Type>Field" methods can be used for object, boolean, byte, char, short, int, long, float, double. Nothing specific here for array. Should I use the GetObjectField method, if so can the object field then be handled as an array? This is where I am missing something. I have experimented with using the SetIntArrayRegion method but this causes an exception - obviously missing a necessary step here. I am hoping someone here can provide guidance on what I am missing, what JNI functions I should be using, or refer me to the appropriate page of the specification or other document where it is explained (for idiots like me).

  • What is the significance of Functional Specification.

    Please do mail me at [email protected]

    Dear FARHAN FAROOQ,
    The Functional Specification describes the features of the desired functinality.
    It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
    The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
    The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
    The functional specification translates the Software Requirements template into a technical description which
    a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement process.
    b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
    A functional specification (or sometimes functional specifications) is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. (At least one major product development group used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for a word processing system, then declared that the user's guide was the functional specification. The developers were challenged to create a product that matched what the user's guide described.) Typically, the functional specification for an application program with a series of interactive windows and dialogs with a user would show the visual appearance of the user interface and describe each of the possible user input actions and the program response actions. A functional specification may also contain formal descriptions of user tasks, dependencies on other products, and usability criteria. Many companies have a guide for developers that describes what topics any product's functional specification should contain.
    For a sense of where the functional specification fits into the development process, here are a typical series of steps in developing a software product:
    • Requirements. This is a formal statement of what the product planners informed by their knowledge of the marketplace and specific input from existing or potential customers believe is needed for a new product or a new version of an existing product. Requirements are usually expressed in terms of narrative statements and in a relatively general way.
    • Objectives. Objectives are written by product designers in response to the Requirements. They describe in a more specific way what the product will look like. Objectives may describe architectures, protocols, and standards to which the product will conform. Measurable objectives are those that set some criteria by which the end product can be judged. Measurability can be in terms of some index of customer satisfaction or in terms of capabilities and task times. Objectives must recognize time and resource constraints. The development schedule is often part or a corollary of the Objectives.
    • Functional specification. The functional specification (usually functional spec or just spec for short) is the formal response to the objectives. It describes all external user and programming interfaces that the product must support.
    • Design change requests. Throughout the development process, as the need for change to the functional specification is recognized, a formal change is described in a design change request.
    • Logic specification. The structure of the programming (for example, major groups of code modules that support a similar function), individual code modules and their relationships, and the data parameters that they pass to each other may be described in a formal document called a logic specification. The logic specification describes internal interfaces and is for use only by the developers, testers, and, later, to some extent, the programmers that service the product and provide code fixes to the field.
    • User documentation. In general, all of the preceding documents (except the logic specification) are used as source material for the technical manuals and online information (such as help pages) that are prepared for the product's users.
    • Test plan. Most development groups have a formal test plan that describes test cases that will exercise the programming that is written. Testing is done at the module (or unit) level, at the component level, and at the system level in context with other products. This can be thought of as alpha testing. The plan may also allow for beta test. Some companies provide an early version of the product to a selected group of customers for testing in a "real world" situation.
    • The final product. Ideally, the final product is a complete implementation of the functional specification and design change requests, some of which may result from formal testing and beta testing.
    The cycle is then repeated for the next version of the product, beginning with a new Requirements statement, which ideally uses feedback from customers about the current product to determine what customers need or want next.
    Hope this helps you.
    Do award points if you found them useful.
    Regards,
    Rakesh
    P.S. you can send me a mail at my mail id [email protected] for any specific details

  • BI ETL Integration Functional Specifications

    Hi All,
    I am into implementation project, Currently Design Phase is in progress. 
    Need suggestions to understand about the BI ETL Integration Functional Specification
    can any one through some light on BI ETL FS document and its content.
    Please provide me detailed information to understand the functional specifications in SAP BI.
    Thanks in advance.
    Thanks and Regards,
    Venkat Ganni.

    Thanks for your response, but we are looking for integration between SAP NW BI (or BW) not BusinessObjects.
    Sorry for the post. I can't seem to be able to present in the format I wanted.
    I believe that is it a limitation on SDN form messaging format where I can't go beyond a certain number of texts automatically forcing the message in one big chunk.
    But the summary requirements is to build a bi-directional bridge between GIS and BI u2018seamlesslyu2019 whereby:
    1. A user can select an area of the ESRI-GIS map through a polygon containing combinations of characteristics and values (e.g. project, WBS, functional location, equipment, asset number etc.)
    2. Then with a click on button somewhere on the map with execute a BI report (can be Web-based or Excel-based) processing these characteristics for display.
    3. Then a user can navigate on this existing (or new) BI report (web or excel-workbook) to reach a new results set (like maybe smaller number of projects previously passed on and then with a click on a button in the BI report
    4. Users will be able to view the graphical representation on these characteristics on the ESRI-GIS map.
    In short, we are trying to find a way to pass list of values of any number to a BW report (either web or excel-workbook) for processing before execution and vice versa with an ESRI-GIS map.

  • Functional Specification meaning

    hi all,
    In one of my functional specification some Functional consultant has written like this,
    To get Supervisor
    Table HRP1001:
    From Object Type P -
    > Relationship A008 to Object type S where ENDDA = 31.12.9999 -
    > Object Type S (e.g., 123).
    From Object Type S(123) -
    > Relationship type A002 to Object type S where ENDDA = 31.12.9999 -
    > Object Type S(e.g., 124)
    From Object Type S(124) -
    > Relationship Type A008 to Object Type P where ENDDA = 31.12.9999. Get Target Object ID
    Check PERNR in PA0001(Target Object Id ), table fields to be displayed for Supervisor Name is ""PA0001-SNAME"""     
    Can anyone explain what he means?
    regards
    Jose

    Hi,
    I think what i tries to explain is
    To get Supervisor
    1. (From Object Type P -
    > Relationship A008 to Object type S where ENDDA = 31.12.9999 -
    > Object Type S (e.g., 123). )
    Get the position of the person in table HRP1001 by passing evaluation path
    A008 and personal Number.
    Get OBJID by passing Object Type -S,Type of Related Object ->P,SOBID -Personal Number whose supervisor need to determine and RSIGN -A and RELAT - 008. from HRP1001.lets say 123 is the position.
    2. (From Object Type S(123) -
    > Relationship type A002 to Object type S where ENDDA = 31.12.9999 -
    > Object Type S(e.g., 124) )
    Pass the position get from point 1 to OBJID  , RSIGN -A and RELAT - 008 ,Object Type -S,Type of Related Object -S and get SOBID from table HRP1001.Lets c 124
    3. (From Object Type S(124) -
    > Relationship Type A008 to Object Type P where ENDDA = 31.12.9999. Get Target Object ID)
    Pass this position (124) to OBJID Object Type -S,Type of Related Object ->P,RSIGN -A and RELAT - 008 and get SOBID from table HRP1001.
    4. (Check PERNR in PA0001(Target Object Id ), table fields to be displayed for Supervisor Name is ""PA0001-SNAME""")
    Get the name(Sname) of the pernr you got from the (3) by passing the pernr from table pa0001.
    Hope this is clear to u.
    Cheers,
    Manoj.

  • Functional Specification Invoice

    Hi Guru's
    Any Bady Could u Pls Send Functional Specification For Invoice With Tax.
    My Mail ID is [email protected]
    Regards
    Sriram

    A functional specification (or sometimes functional specifications) is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. (At least one major product development group used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for a word processing system, then declared that the user's guide was the functional specification. The developers were challenged to create a product that matched what the user's guide described.) Typically, the functional specification for an application program with a series of interactive windows and dialogs with a user would show the visual appearance of the user interface and describe each of the possible user input actions and the program response actions. A functional specification may also contain formal descriptions of user tasks, dependencies on other products, and usability criteria. Many companies have a guide for developers that describes what topics any product's functional specification should contain.
    For a sense of where the functional specification fits into the development process, here are a typical series of steps in developing a software product:
    Requirements. This is a formal statement of what the product planners informed by their knowledge of the marketplace and specific input from existing or potential customers believe is needed for a new product or a new version of an existing product. Requirements are usually expressed in terms of narrative statements and in a relatively general way.
    Objectives. Objectives are written by product designers in response to the Requirements. They describe in a more specific way what the product will look like. Objectives may describe architectures, protocols, and standards to which the product will conform. Measurable objectives are those that set some criteria by which the end product can be judged. Measurability can be in terms of some index of customer satisfaction or in terms of capabilities and task times. Objectives must recognize time and resource constraints. The development schedule is often part or a corollary of the Objectives.
    Functional specification. The functional specification (usually functional spec or just spec for short) is the formal response to the objectives. It describes all external user and programming interfaces that the product must support.
    Design change requests. Throughout the development process, as the need for change to the functional specification is recognized, a formal change is described in a design change request.
    Logic specification. The structure of the programming (for example, major groups of code modules that support a similar function), individual code modules and their relationships, and the data parameters that they pass to each other may be described in a formal document called a logic specification. The logic specification describes internal interfaces and is for use only by the developers, testers, and, later, to some extent, the programmers that service the product and provide code fixes to the field.
    User documentation. In general, all of the preceding documents (except the logic specification) are used as source material for the technical manuals and online information (such as help pages) that are prepared for the product's users.
    Test plan. Most development groups have a formal test plan that describes test cases that will exercise the programming that is written. Testing is done at the module (or unit) level, at the component level, and at the system level in context with other products. This can be thought of as alpha testing. The plan may also allow for beta test. Some companies provide an early version of the product to a selected group of customers for testing in a "real world" situation.
    The final product. Ideally, the final product is a complete implementation of the functional specification and design change requests, some of which may result from formal testing and beta testing.
    The cycle is then repeated for the next version of the product, beginning with a new Requirements statement, which ideally uses feedback from customers about the current product to determine what customers need or want next.
    Most software makers adhere to a formal development process similar to the one described above. The hardware development process is similar but includes some additional considerations for the outsourcing of parts and verification of the manufacturing process itself.
    Regards,
    Rajesh Banka

  • What is the functional specification

    hai
    sap gurus please tell me the functional specification how can we write the functional specification
    can anbody explain in details and give me one good  example for functional specification?
    thanks
    regards
    anwar

    Functional Specification:
    To speak at macro level that is at project manager or at senior levels. The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhere organizations combine these two documents into a single document.
    The Functional Specification describes the features of the desired functionality. It describes the product's features as seen by the stake holders, and contains the technical information and the data needed for the design and development.
    The Functional Specification defines what the functionality will be of a particular area that is to be precise a transaction in SAP terminology.
    The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
    The functional specification translates the Software Requirements template into a technical description which
    a) Ensures that the product feature requirements are correctly understood before moving into the next step that is technical development process.
    b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
    At the consultant level the functional specs are prepared by functional consultants on any functionality for the purpose of getting the same functionality designed by the technical people as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
    Let me throw some light on documentation which is prepared before and in a project:
    1) Templates
    2) Heat Analysis -
    3) Fit Gap or Gap Analysis
    4) Business Process Design
    5) Business Process Model
    6) Business Change & Impact
    7) Configuration Design, which is just 5 % of Total SAP- have different names -
    8) Future Impact & Change Assessment
    9) Functional Design (Module Wise)
    10) Risk Assessment
    11) Process Metrics and Many More-- Which has impact on Business and its work flow
    Regards,
    Rajesh Banka

Maybe you are looking for

  • No Export options and Place not working correctly. InDesign CC 2014.

    I cannot place a file into a frame with cmd+d or File > Place. I get the preview on the cursor but won't place into a frame which I need to keep the frame effects and size options. - Also - I am not getting any options on Export - to change the outpu

  • Is there a limit date of support or upgrade for ipad 2 ?

    I'm about to buy a ipad2 for christmas (for someone else, i already have one) and a vendor say to me that it will be supported only for 1 year so next generation is a better choice ? Is it true ? Never heard anything about that...

  • Need help, no idea what's wrong...

    Hi, ummm i'm really not expierenced with this computer stuff... all I know is I hadn't used my ipod mini in a while and I updated the software for itunes/quicktime. Now itunes seems to work fine, but everywhere quicktime should run stuff... it just g

  • Disk Quota not enabling

    Folks, We're having a problem with enabling quotas on our client accounts. I've set everyone's account limit in workgroup manager, then under server admin i've ticked the box to enable quotas, but it won't save. At first, this didn't seem to be a pro

  • One sytem rollback segment though AUM

    Hello guys, i know from oracle documentation and experience that there exists one rollback segment in system until the initial installation... but why? Why can oracle not use the undo tablespace for this rollback segment if i use AUM? Can i delete th