OSX 10.5.5 screws up jogl's  text renderer

I narrowed down a problem I am having with jogl's text renderer (com.sun.opengl.util.j2d.TextRenderer).
It displays gibberish text with OSX 10.5.5 update. (tested on multiple macs).
I'm stuck and I decided to post here to see if anyone else have the same issues, and perhaps find a solution.
To summarize: com.sun.opengl.util.j2d.TextRenderer displays gibberish text when using OSX 10.5.5 while works fine on previous versions of OSX (and PC).

I ran the gears + text demo form the jogl demo page. My text was extremely corrupted. If I could include an image, I would. It was as if black boxes were overlaid on top of all the characters, making it hard to discern on character from another. Also, the lower-right simply showed FPS: FFF.FF
Source: https://jogl-demos.dev.java.net/
Direct Link: http://download.java.net/media/jogl/builds/archive/jsr-231-webstart-current/Test TextRenderer.jnlp

Similar Messages

  • OSX 10.6.7 screws up PDF print from preview

    Since the update to 10.6.7 we cannot print PDF's correctly any more on our Canon MP620 printer scanner hocked up via ethernet. The fonts are not correctly printed any more, the lines are of wrong thickness and some letters show wrong filled triangles.
    It is related to the update to OSX 10.6.7 and the preview app, files we could print correctly before we cannot print correctly any more. It works with Adobe reader without problem.
    Other people have reported problems with Canon printers and PDF's as well since the update.

    I just tried to print a PDF containing both TrueType and Postscript fonts from my 10.6.7 machine to a Canon IP5200 shared by another 10.6.7 machine. It printed fine.
    Then I tried to print the same file to a Canon MX300 shared by the same 10.6.7 machine. It failed to print.
    Then I tried to print a PDF having only the text "This is a test of Times" in the TrueType Times font to the Canon MX300 shared by the same 10.6.7 machine. It failed to print.
    Both documents print fine from a 10.6.6 machine to the same printers shared by the 10,6.7 machine.
    The same documents printed fine from 10.6.7 to the Canon MX300 while attached locally.
    So, 10.6.7 seems to break networked printing for some Canon printers.
    So far, I am 0 for 3 on the 10.6.7 bug issue. It is time to admit defeat. My official recommendation is to roll back to 10.6.6. I will be filing yet another bug report with Apple.

  • Safari 5.1.7 and OSX 10.6.8 (Snow Leopard) - Text rendering problem with Zoom

    After updating to Safari 5.1.7, all of my web pages do not render properly when I use zoom feature of OSX 10.6.8.  I am nearsighted, and like to increase the size of web pages.  Until this update, Safari was fine--zoom, and the page zooms properly (e.g., text fits in address bar, pictures/text are not cut off, etc.).  After this update, Safari opens up text in smaller font, running in a narrow line down the page, and doesn't use the full screen, as does Firefox for example.  I like Safari, and would like to remedy this.  Any suggestions?

    I fixed this by unchecking "Zoom Text Only" in Safari > View menu.

  • I have two different accounts on my iMac 2011 OSX 10.8.2. When you type text in one account, he dialed in the second account at a time. how to solve it?

    I have two different accounts on my iMac 2011 OCX 10.8.2. When you type text in one account, he dialed in the second account at a time. how to solve it?

    I have 2 users on the imac. when entering text in the first account it is duplicated in the second

  • I group messaged from my ipad and this has screwed up the way my messages are reveived by my friends (it creates new threads in their phones with my email in place of my contact name) I've stopped messaging from my ipad but the problem remains. Any help?

    I have an iPhone 4S and use the group texting feature ALL THE TIME. I recently updated my iPad to the latest software and made the colossal mistake of continuing my group messaging from my iPad while connected to wifi. Doing this has successfully screwed but every group text thread I am in, to the point where its very hard for those involved in the thread to keep up. When I initially messaged those I was already engaged in text threads with it created a new thread in their phones replacing my name in their phones with my email. At first this was not a big deal but ever since then the people I am messaging have become increasingly frustrated with how my messages come through. If I am messaged in a group text and respond to it, sometimes when I respond it will create an entirely different thread in my recipients phones. So at that point they have to switch threads in order to read what I wrote. The new thread that my phone creates will send the message under my email not my name (related to the contact they have me saved as in their phones). The worst part about it is that there seems to be no rhyme or reason to why or when my phone will send the message as normal or under my email like it did with my iPad. I haven’t messaged from my iPad since these problems immediately began a month ago but the issues still continue. I have tried everything to get this to stop, I’ve turned off my wifi, I’ve had my friends delete the threads that my messages create in their phones. I’ve had them delete my email in their contact lists and nothing has worked. Can you help me? Any info you could provide would be greatly appreciated.
    Note: My phone message no different whatsoever. All the threads have remained the same. The issue is what it is doing to the people that I am messaging.
        Best Regards
             Rick Mulhern
    Message was edited by: Rickapplehelp19

    I have this identical problem.  For a while my group texts didnt show up on my ipad.  Then one day they did, maybe everyone in the group started using the same os version or something.  Ever since my first reply to the group there have been complaints of multiple threads.  I can not find a pattern for when my group text's decide they want to create a new thread. (it doesnt happen every time)  Everyone in the group has deleted the thread, we've all toggled imessage on/off etc.  There still hasn't been a solution.
    Any help would be appreciated.
    Thanks

  • Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.

    This is a project that I have been successfully encoding in short segments until now.  Now when encoding, session runs about 10-15 minutes and then ends without error messages. 
    Removing effects and changing to Mercury PB Engine SW did not help. 
    Also tried disabling metadata as suggested in another forum. 
    When CUDA used, logged as "Encoding failed."  When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
    Premiere Pro Build 8.1.0 (81)
    Media Encoder Build 8.1.0.122
    Windows 7 Professional
    Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
    8 GB RAM
    NVIDIA GeForce GT 610 (9.18.13.3788)

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

    Running out of options and ideas...
    Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode.  The crash is a software crash, Windows continues to run fine.
    I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc.  https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
    Windows event is not that helpful to me:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x00007ff5ecb4de40
    Faulting process id: 0x1dc8
    Faulting application start time: 0x01d04a503cd82df2
    Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: unknown
    Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
    Faulting package full name:
    Faulting package-relative application ID:
    I have wiped adobe off the machine and reinstalled - same problem.  I have tried projects that crash the machine on other machines and it works fine.
    The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
    Spec:
    5K iMac running bootcamp and Windows 8.1
    Intel Core i7-4790K @ 4.0 GHz
    32 GB ram
    1TB SSD
    AMD Radeon R9 M295X 4GB GDDR5
    I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great.  Guess it was my time for a problem, but I'm open to new ideas to try...
    Finally - I hope someone from Adobe reads this.  I have spent 2 nights on the phone with support.  The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem).  Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
    Thanks in advance to anyone with ideas on things to try,
    Cheers!

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • Premiere Pro CC 2014 and Medie Encoder CC 2014 problem

    Hello there,
    Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
    I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing  problems with the New Mac Pro. Is that true? Or is there other issue?
    Thank you and looking forward to hear back,
    Maruf

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • Premire Pro CC 2014 and Media Encoder Crash During Launch

    Premire Pro and Media Encoder crash during startup and are unusable. I am using Windows 7 Ultimate and already tried reinstalling Adobe Creative Cloud from scratch and it's still happening. I also tried following Adobes KB articles directions to rename the Adobe folder in my documents and appdata to no avail. When I try to launch either application, I get a generic windows crash message "Adobe Premire Pro CC 2014.0 has stopped working" and when I click problem details, it lists this:
    Problem signature:
      Problem Event Name: APPCRASH
      Application Name: Adobe Premiere Pro.exe
      Application Version: 8.0.0.169
      Application Timestamp: 536f4f89
      Fault Module Name: ImageRenderer.dll
      Fault Module Version: 8.0.0.169
      Fault Module Timestamp: 536f2c18
      Exception Code: c000001d
      Exception Offset: 00000000001f5382
      OS Version: 6.1.7600.2.0.0.256.1
      Locale ID: 1033
      Additional Information 1: 0b2d
      Additional Information 2: 0b2df4702c3fc6489bf922fb8e966350
      Additional Information 3: fa9f
      Additional Information 4: fa9f59f642d335ee71c6667e52000d39

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • Premiere cc 2014+ENCODER cc 2014

    ЗДРАВСТВУТЕ появился вопрос:используя Premiere cc 2014 вместе с ENCODER. при экспорте в него и выводе образуются офлайн кадры!
    какова вероятность, что это глюк или я не правильно настроил что-то не так?  ENCODER cc 2014 - обновился до версии где голубой интерфейс, а Premiere- нет!

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • How do I share my Mac's Wifi Internet with my xbox (connected through Ethernet) in 10.8 Mountain Lion?

    I am trying to use my MAC's wifi connection for my Xbox 360 using the Ethernet Cable.  I've done it in the past in an earlier version of OSX which I saved the settings in a text file for later use... those settings do not work.
    First Question:  Do I use a Regular or Crossover Ethernet Cable?
    Second Question:  How do I get it to work?
    I've tried all the 10.7 tutorials I could find (couldn't find any 10.8) as well as older ones but none seem to do the trick.
    I have turned on Internet Sharing and Disable Little Snitch while testing, OSX Firewall is Disabled.
    I tried Automatic Settings and also Manual ones from the tutorials...
    Thanks for any help!

    One workaround here. If you monitor the "More Like This" box (top right), other threads appear. Opening them usually displays other threads.
    https://discussions.apple.com/message/15725285#15725285

  • HP Color LaserJet Pro MFP M177fw Scanning

    I bought and jsut setup an HP Color LaserJet Pro MFP M177fw.  
    We are a Mac household, and we connect via wireless to the printer, which works great. 
    My issue is scanning.  On the little screen on the printer, I can copy, print and even fax.  No option for scanning.  There is some bullsh*t app that I've had to download via HP called Readiris, which is useless.  There is no apparent way to initiate a scan via this app. 
    So I've bought a multifunction printer that doesn't scan.  Any help?  

    It doesn't scan?! 
    Below is the text from the first page of the first link one clicks on about this printer.  How _on earth_ is one supposed to deduce pre-purchase that it doesn't scan from the main menu?  Argh.  As an HP employee myself, this is aggravating in the extreme. 
    Ok, venting aside, this link <http://h10025.www1.hp.com/ewfrf/wc/document?cc=us&lc=en&docname=c03967506#N229> is not offering a solution. 
    I am running OSX 10.9.1. I am unable to find the Full Driver to donwload in order to connect to this printer in a manner that would enable any of the 3 methods of scanning (Via Preview, Image Capture, etc.) to work.  Can you please provide a link to the Full Driver for this MFP M177fw for Mac OSX 10.9?  Thanks.
    ***  Start copied text from online website on HP printer ***
    This affordable HP Color LaserJet Pro MFP brings vibrant color printing
    in-house, and boosts productivity with Ethernet connectivity. Enable easy
    printing at work, home, or on the go with mobile printing features.1
    Print speed:4
    Black: Up to 17 ppm; Color: Up to 4 ppm
    Scan resolution: Up to 1200 x 1200 dpi (hardware); Up to 1200 x 1200 dpi
    (optical)
    Copy resolution: Black (text): Up to 300 x 300 dpi; Black (graphics): Up to
    400 x 600 dpi; Color (text and graphics): Up to 300 x 300 dpi
    Display: 3.0" LCD (color graphics)
    Standard connectivity: Hi-Speed USB 2.0 port; built-in Fast Ethernet
    10/100Base-TX network port; Wireless 802.11b/g/n
    Duty cycle:5
    Up to 20,000 pages

  • Android, backspace doesn't work properly in a flash.text.TextField

    Hello,
    I have a bug on my Nexus 5 Android 4.4 Air 4.0.
    when I scroll the text in the textField and I select the text (in my example near "subclass" word), the TextField get focus, if I put on the backspace key, the character deleted is the previous character the first time, and if I put again on the backspace key, the caracter deleted is the first character and not the previous character.
    package{
    import flash.text.TextField;
    import flash.display.Sprite;
    import flash.events.Event;
    import flash.display.StageAlign;
    import flash.display.StageScaleMode;
    public class Main extends Sprite {
      private var myTextField:TextField = new TextField();
      public function Main() {
        stage.scaleMode = StageScaleMode.NO_SCALE;
        stage.align = StageAlign.TOP_LEFT;
        addEventListener(Event.ADDED_TO_STAGE, init);
      private function init(event:Event):void {
        myTextField.type="input";
        myTextField.text="The TextField class is used to create display objects for text display and input. You can give a text field an instance name in the Property inspector and use the methods and properties of the TextField class to manipulate it with ActionScript. TextField instance names are displayed in the Movie Explorer and in the Insert Target Path dialog box in the Actions panel.\nTo create a text field dynamically, use the TextField() constructor.\n\nThe methods of the TextField class let you set, select, and manipulate text in a dynamic or input text field that you create during authoring or at runtime.\n\nActionScript provides several ways to format your text at runtime. The TextFormat class lets you set character and paragraph formatting for TextField objects. You can apply Cascading Style Sheets (CSS) styles to text fields by using the TextField.styleSheet property and the StyleSheet class. You can use CSS to style built-in HTML tags, define new formatting tags, or apply styles. You can assign HTML formatted text, which optionally uses CSS styles, directly to a text field. HTML text that you assign to a text field can contain embedded media (movie clips, SWF files, GIF files, PNG files, and JPEG files). The text wraps around the embedded media in the same way that a web browser wraps text around media embedded in an HTML document.\n\nFlash Player supports a subset of HTML tags that you can use to format text. See the list of supported HTML tags in the description of the htmlText property.\n\nView the examples\n\nMore examples\n\nModifying the text field contents\nDisplaying HTML text\nUsing images in text fields\nScrolling text in a text field\nSelecting and manipulating text\nCapturing text input\nRestricting text input\nFormatting text\nWorking with static text\nTextField Example: Newspaper-style text formatting\nLearn more\n\nUse native features with a soft keyboard\nDisplay programming\nBasics of display programming\nCore display classes\nChoosing a DisplayObject subclass\nBasics of Working with text\nUsing the TextField class\nDisplaying text\nAdvanced text rendering\nRelated API Elements\n\nflash.text.TextFormat\nflash.text.StyleSheet\nhtmlText\n\nPublic Properties\n Show Inherited Public Properties\n   Property  Defined By\n      alwaysShowSelection : Boolean\nWhen set to true and the text field is not in focus, Flash Player highlights the selection in the text field in gray.\nTextField\n      antiAliasType : String\nThe type of anti-aliasing used for this text field.\nTextField\n      autoSize : String\nControls automatic sizing and alignment of text fields.\nTextField\n      background : Boolean\nSpecifies whether the text field has a background fill.\nTextField\n      backgroundColor : uint\nThe color of the text field background.\nTextField\n      border : Boolean\nSpecifies whether the text field has a border.\nTextField\n      borderColor : uint\nThe color of the text field border.\nTextField\n      bottomScrollV : int\n[read-only] An integer (1-based index) that indicates the bottommost line that is currently visible in the specified text field.\nTextField\n      caretIndex : int\n[read-only] The index of the insertion point (caret) position.\nTextField\n      condenseWhite : Boolean\nA Boolean value that specifies whether extra white space (spaces, line breaks, and so on) in a text field with HTML text is removed.\nTextField\n      defaultTextFormat : flash.text:TextFormat\nSpecifies the format applied to newly inserted text, such as text entered by a user or text inserted with the replaceSelectedText() method.\nTextField\n      displayAsPassword : Boolean\nSpecifies whether the text field is a password text field.\nTextField\n      embedFonts : Boolean\nSpecifies whether to render by using embedded font outlines.\nTextField\n      gridFitType : String\nThe type of grid fitting used for this text field.\nTextField\n      htmlText : String\nContains the HTML representation of the text field contents.\nTextField\n      length : int\n[read-only] The number of characters in a text field.\nTextField\n      maxChars : int\nThe maximum number of characters that the text field can contain, as entered by a user.\nTextField\n      maxScrollH : int\n[read-only] The maximum value of scrollH.\nTextField\n      maxScrollV : int\n[read-only] The maximum value of scrollV.\nTextField\n      mouseWheelEnabled : Boolean\nA Boolean value that indicates whether Flash Player automatically scrolls multiline text fields when the user clicks a text field and rolls the mouse wheel.\nTextField\n      multiline : Boolean\nIndicates whether field is a multiline text field.\nTextField\n      numLines : int\n[read-only] Defines the number of text lines in a multiline text field.\nTextField\n      restrict : String\nIndicates the set of characters that a user can enter into the text field.\nTextField\n      scrollH : int\nThe current horizontal scrolling position.\nTextField\n      scrollV : int\nThe vertical position of text in a text field.\nTextField\n      selectable : Boolean\nA Boolean value that indicates whether the text field is selectable.\nTextField\n      selectionBeginIndex : int\n[read-only] The zero-based character index value of the first character in the current selection.\nTextField\n      selectionEndIndex : int\n[read-only] The zero-based character index value of the last character in the current selection.\nTextField\n      sharpness : Number\nThe sharpness of the glyph edges in this text field.\nTextField\n      styleSheet : StyleSheet\nAttaches a style sheet to the text field.\nTextField\n      text : String\nA string that is the current text in the text field.\nTextField\n      textColor : uint\nThe color of the text in a text field, in hexadecimal format.\nTextField\n      textHeight : Number\n[read-only] The height of the text in pixels.\nTextField\n      textInteractionMode : String\n[read-only] The interaction mode property, Default value is TextInteractionMode.NORMAL.\nTextField\n      textWidth : Number\n[read-only] The width of the text in pixels.\nTextField\n      thickness : Number\nThe thickness of the glyph edges in this text field.\nTextField\n      type : String\nThe type of the text field.\nTextField\n      useRichTextClipboard : Boolean\nSpecifies whether to copy and paste the text formatting along with the text.\nTextField\n      wordWrap : Boolean\nA Boolean value that indicates whether the text field has word wrap.\nTextField";
        myTextField.border=true;
        myTextField.width=myTextField.height=300;
        addChild(myTextField);
    Thanks.

    I have this bug on Galaxy Nexus Android 4.3, I don't have this bug on Galaxy S Android 2.3, the bug occurs with the new Google Keyboard 3.0
    the app descriptor
    <?xml version="1.0" encoding="utf-8" standalone="no"?>
    <application xmlns="http://ns.adobe.com/air/application/4.0">
    <!-- Adobe AIR Application Descriptor File Template.
              Specifies parameters for identifying, installing, and launching AIR applications.
              xmlns - The Adobe AIR namespace: http://ns.adobe.com/air/application/3.5
                                  The last segment of the namespace specifies the version
                                  of the AIR runtime required for this application to run.
              minimumPatchLevel - The minimum patch level of the AIR runtime required to run
                                  the application. Optional.
    -->
              <!-- A universally unique application identifier. Must be unique across all AIR applications.
              Using a reverse DNS-style name as the id is recommended. (Eg. com.example.ExampleApplication.) Required. -->
              <id>TextFieldFB</id>
              <!-- Used as the filename for the application. Required. -->
              <filename>TextFieldFB</filename>
              <!-- The name that is displayed in the AIR application installer.
              May have multiple values for each language. See samples or xsd schema file. Optional. -->
              <name>TextFieldFB</name>
              <!-- A string value of the format <0-999>.<0-999>.<0-999> that represents application version which can be used to check for application upgrade.
              Values can also be 1-part or 2-part. It is not necessary to have a 3-part value.
              An updated version of application must have a versionNumber value higher than the previous version. Required for namespace >= 2.5 . -->
              <versionNumber>0.0.1</versionNumber>
              <!-- A string value (such as "v1", "2.5", or "Alpha 1") that represents the version of the application, as it should be shown to users. Optional. -->
              <!-- <versionLabel></versionLabel> -->
              <!-- Description, displayed in the AIR application installer.
              May have multiple values for each language. See samples or xsd schema file. Optional. -->
              <!-- <description></description> -->
              <!-- Copyright information. Optional -->
              <!-- <copyright></copyright> -->
              <!-- Publisher ID. Used if you're updating an application created prior to 1.5.3 -->
              <!-- <publisherID></publisherID> -->
              <!-- Settings for the application's initial window. Required. -->
              <initialWindow>
                        <!-- The main SWF or HTML file of the application. Required. -->
                        <!-- Note: In Flash Builder, the SWF reference is set automatically. -->
                        <content>[Cette valeur sera remplacée par Flash Builder dans le fichier app.xml de sortie]</content>
                        <!-- The title of the main window. Optional. -->
                        <!-- <title></title> -->
                        <!-- The type of system chrome to use (either "standard" or "none"). Optional. Default standard. -->
                        <!-- <systemChrome></systemChrome> -->
                        <!-- Whether the window is transparent. Only applicable when systemChrome is none. Optional. Default false. -->
                        <!-- <transparent></transparent> -->
                        <!-- Whether the window is initially visible. Optional. Default false. -->
                        <!-- <visible></visible> -->
                        <!-- Whether the user can minimize the window. Optional. Default true. -->
                        <!-- <minimizable></minimizable> -->
                        <!-- Whether the user can maximize the window. Optional. Default true. -->
                        <!-- <maximizable></maximizable> -->
                        <!-- Whether the user can resize the window. Optional. Default true. -->
                        <!-- <resizable></resizable> -->
                        <!-- The window's initial width in pixels. Optional. -->
                        <!-- <width></width> -->
                        <!-- The window's initial height in pixels. Optional. -->
                        <!-- <height></height> -->
                        <!-- The window's initial x position. Optional. -->
                        <!-- <x></x> -->
                        <!-- The window's initial y position. Optional. -->
                        <!-- <y></y> -->
                        <!-- The window's minimum size, specified as a width/height pair in pixels, such as "400 200". Optional. -->
                        <!-- <minSize></minSize> -->
                        <!-- The window's initial maximum size, specified as a width/height pair in pixels, such as "1600 1200". Optional. -->
                        <!-- <maxSize></maxSize> -->
            <!-- The aspect ratio of the app ("portrait" or "landscape" or "any"). Optional. Mobile only. Default is the natural orientation of the device -->
            <!-- <aspectRatio></aspectRatio> -->
            <!-- Whether the app will begin auto-orienting on launch. Optional. Mobile only. Default false -->
            <!-- <autoOrients></autoOrients> -->
            <!-- Whether the app launches in full screen. Optional. Mobile only. Default false -->
            <!-- <fullScreen></fullScreen> -->
            <!-- The render mode for the app (either auto, cpu, gpu, or direct). Optional. Default auto -->
            <!-- <renderMode></renderMode> -->
            <!-- Whether the default direct mode rendering context allocates storage for depth and stencil buffers.  Optional.  Default false. -->
            <!-- <depthAndStencil></depthAndStencil> -->
                        <!-- Whether or not to pan when a soft keyboard is raised or lowered (either "pan" or "none").  Optional.  Defaults "pan." -->
                        <!-- <softKeyboardBehavior></softKeyboardBehavior> -->
                        <!-- Display Resolution for the app (either "standard" or "high"). Optional, OSX-only. Default "standard" -->
                        <!-- <requestedDisplayResolution></requestedDisplayResolution> -->
              <autoOrients>true</autoOrients>
            <fullScreen>false</fullScreen>
            <visible>true</visible>
        </initialWindow>
              <!-- We recommend omitting the supportedProfiles element, -->
              <!-- which in turn permits your application to be deployed to all -->
              <!-- devices supported by AIR. If you wish to restrict deployment -->
              <!-- (i.e., to only mobile devices) then add this element and list -->
              <!-- only the profiles which your application does support. -->
              <!-- <supportedProfiles>desktop extendedDesktop mobileDevice extendedMobileDevice</supportedProfiles> -->
              <!-- Languages supported by application -->
              <!-- Only these languages can be specified -->
              <!-- <supportedLanguages>en de cs es fr it ja ko nl pl pt ru sv tr zh</supportedLanguages> -->
              <!-- The subpath of the standard default installation location to use. Optional. -->
              <!-- <installFolder></installFolder> -->
              <!-- The subpath of the Programs menu to use. (Ignored on operating systems without a Programs menu.) Optional. -->
              <!-- <programMenuFolder></programMenuFolder> -->
              <!-- The icon the system uses for the application. For at least one resolution,
              specify the path to a PNG file included in the AIR package. Optional. -->
              <!-- <icon>
                        <image16x16></image16x16>
                        <image29x29></image29x29>
                        <image32x32></image32x32>
                        <image36x36></image36x36>
                        <image40x40></image40x40>
                        <image48x48></image48x48>
                        <image50x50></image50x50>
                        <image57x57></image57x57>
                        <image58x58></image58x58>
                        <image72x72></image72x72>
                        <image76x76></image76x76>
                        <image80x80></image80x80>
                        <image96x96></image96x96>
                        <image100x100></image100x100>
                        <image114x114></image114x114>
                        <image120x120></image120x120>
                        <image128x128></image128x128>
                        <image144x144></image144x144>
                        <image152x152></image152x152>
                        <image512x512></image512x512>
                        <image732x412></image732x412>
                        <image1024x1024></image1024x1024>
              </icon> -->
              <!-- Whether the application handles the update when a user double-clicks an update version
              of the AIR file (true), or the default AIR application installer handles the update (false).
              Optional. Default false. -->
              <!-- <customUpdateUI></customUpdateUI> -->
              <!-- Whether the application can be launched when the user clicks a link in a web browser.
              Optional. Default false. -->
              <!-- <allowBrowserInvocation></allowBrowserInvocation> -->
              <!-- Listing of file types for which the application can register. Optional. -->
              <!-- <fileTypes> -->
                        <!-- Defines one file type. Optional. -->
                        <!-- <fileType> -->
                                  <!-- The name that the system displays for the registered file type. Required. -->
                                  <!-- <name></name> -->
                                  <!-- The extension to register. Required. -->
                                  <!-- <extension></extension> -->
                                  <!-- The description of the file type. Optional. -->
                                  <!-- <description></description> -->
                                  <!-- The MIME content type. -->
                                  <!-- <contentType></contentType> -->
                                  <!-- The icon to display for the file type. Optional. -->
                                  <!-- <icon>
                                            <image16x16></image16x16>
                                            <image32x32></image32x32>
                                            <image48x48></image48x48>
                                            <image128x128></image128x128>
                                  </icon> -->
                        <!-- </fileType> -->
              <!-- </fileTypes> -->
        <!-- iOS specific capabilities -->
              <!-- <iPhone> -->
                        <!-- A list of plist key/value pairs to be added to the application Info.plist -->
                        <!-- <InfoAdditions>
                <![CDATA[
                    <key>UIDeviceFamily</key>
                    <array>
                        <string>1</string>
                        <string>2</string>
                    </array>
                    <key>UIStatusBarStyle</key>
                    <string>UIStatusBarStyleBlackOpaque</string>
                    <key>UIRequiresPersistentWiFi</key>
                    <string>YES</string>
                ]]>
            </InfoAdditions> -->
            <!-- A list of plist key/value pairs to be added to the application Entitlements.plist -->
                        <!-- <Entitlements>
                <![CDATA[
                    <key>keychain-access-groups</key>
                    <array>
                        <string></string>
                        <string></string>
                    </array>
                ]]>
            </Entitlements> -->
              <!-- Display Resolution for the app (either "standard" or "high"). Optional. Default "standard" -->
              <!-- <requestedDisplayResolution></requestedDisplayResolution> -->
              <!-- Forcing Render Mode CPU for the devices mentioned. Optional  -->
              <!-- <forceCPURenderModeForDevices></forceCPURenderModeForDevices> -->
              <!-- File containing line separated list of external swf paths. These swfs won't be
              packaged inside the application and corresponding stripped swfs will be output in
              externalStrippedSwfs folder. -->
              <!-- <externalSwfs></externalSwfs> -->
              <!-- </iPhone> -->
              <!-- Specify Android specific tags that get passed to AndroidManifest.xml file. -->
        <!--<android> -->
        <!--          <manifestAdditions>
                        <![CDATA[
                                  <manifest android:installLocation="auto">
                                            <uses-permission android:name="android.permission.INTERNET"/>
                                            <uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
                                            <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>
                                            <uses-feature android:required="true" android:name="android.hardware.touchscreen.multitouch"/>
                                            <application android:enabled="true">
                                                      <activity android:excludeFromRecents="false">
                                                                <intent-filter>
                                                                          <action android:name="android.intent.action.MAIN"/>
                                                                          <category android:name="android.intent.category.LAUNCHER"/>
                                                                </intent-filter>
                                                      </activity>
                                            </application>
                </manifest>
                        ]]>
            </manifestAdditions> -->
                  <!-- Color depth for the app (either "32bit" or "16bit"). Optional. Default 16bit before namespace 3.0, 32bit after -->
            <!-- <colorDepth></colorDepth> -->
            <!-- Indicates if the app contains video or not. Necessary for ordering of video planes with graphics plane, especially in Jellybean - if you app does video this must be set to true - valid values are true or false -->
            <!-- <containsVideo></containsVideo> -->
        <!-- </android> -->
              <!-- End of the schema for adding the android specific tags in AndroidManifest.xml file -->
    <android>
            <manifestAdditions><![CDATA[
                                  <manifest android:installLocation="auto">
                                      <!--See the Adobe AIR documentation for more information about setting Google Android permissions-->
                                      <!--La suppression de l’autorisation android.permission.INTERNET aura comme effet secondaire
                        de vous empêcher de déboguer l’application sur le périphérique.-->
                                      <!--<uses-permission android:name="android.permission.INTERNET"/>-->
                                      <!--<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>-->
                                      <!--<uses-permission android:name="android.permission.READ_PHONE_STATE"/>-->
                                      <!--<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/>-->
                                      <!--Les autorisations DISABLE_KEYGUARD et WAKE_LOCK doivent être permutées
                        afin d’accéder aux API SystemIdleMode d’AIR.-->
                                      <!--<uses-permission android:name="android.permission.DISABLE_KEYGUARD"/>-->
                                      <!--<uses-permission android:name="android.permission.WAKE_LOCK"/>-->
                                      <!--<uses-permission android:name="android.permission.CAMERA"/>-->
                                      <!--<uses-permission android:name="android.permission.RECORD_AUDIO"/>-->
                                      <!--Les autorisations ACCESS_NETWORK_STATE et ACCESS_WIFI_STATE doivent être
                        permutées afin d’utiliser les API NetworkInfo d’AIR.-->
                                      <!--<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>-->
                                      <!--<uses-permission android:name="android.permission.ACCESS_WIFI_STATE"/>-->
                                  </manifest>
                        ]]></manifestAdditions>
        </android>
        <iPhone>
            <InfoAdditions><![CDATA[
                                  <key>UIDeviceFamily</key>
                                  <array>
                                            <string>1</string>
                                            <string>2</string>
                                  </array>
                        ]]></InfoAdditions>
            <requestedDisplayResolution>high</requestedDisplayResolution>
        </iPhone>
    </application>

  • Is there a way to stop iCal moving address info from event text into 'location'??

    Hi, I've just come back to the forum after a long time away, so sorry if this has already been covered, but...
    When I create a new event in iCal and type in text which includes an address, the address segnment is automatically moved into 'location'. I find this infuriating as for work reasons I later need to copy and paste all the event text into another app, and the address is now in a different place! As an additional irritation, iCal also screws with the address text and switches the postal code into upper and lower case, so I have to re-type part of it when I move it back into the main event text. Any way to stop this happening? Thanks!

    as far as i understand iCal it is on the "receivers/subscribers" side to deal with email-updates (and not on the "senders/changers" side):
    snippet from my Re: How do you stop receiving notifications about updated calendar events?:
    to NOT get email notification about updated events from a shared calendar you subscribed to you have to uncheck "events affect availability" in that calendars "info" (mac os X.7 and X.8: iCal —> calendars dropdown —> right click on the subscribed calendar —> choose "get info" from the context-menu —> uncheck "events affect availability")

  • What is wrong with as3

    this is not a question about 'how i do X'. is rather a 'discussion' (flame or whatever, but to defend or argue about aspects, not people) about 'what is wrong with as3' and what aspects whould be taken into consideration for updates. right now i am using as3, and since i paid for this license, i choose this tool over some alternatives and i am using it to do stuff for other people who pay me to do it, i think it can be helpful for all of us if some actions are started in the right direction. i have already posted about 'all people in adobe are dumbasses that do not know how to make a scripting tool and are messing up my work', but i was pissed at the time (i still am pissed) but i believe this is not the right aproach. instead, if this goes to the right people in adobe, we all may get something in the future, like better and easier todo apps and web presentations.
    pre: not only about the as3 specification, but COMPLY with the specification that you set. for example, some time ago there were problems with matrix transforms. this was corrected later with a patch. but this means it is not even doing what is is supposed to do
    1. scriptable masks and movement, sprites and child sprites: there is a sprite with a mask, the mask is a shape drawn via script, something like
    somemask=new shape();
    somemask.graphics.beginfill();
    (...etc)
    somesprite.mask=somemask;
    just like that. now add some child sprites to 'somesprite', and make 'somesprite' move, scale and rotate. there you will have something like a kaleidoscope, but not what you expected to do with your script. as the child sprites move in the parent mask, you will see that the child sprites appear or dissapear kind of randomly, and if the child sprites are textfields, it may be that the text is rendered outside the mask, or partially rendered outside the mask (as in only part of the text), rendered with the wrongf rotation or in the wrong place. some child sprites are clipped correctly, some dissapear totally when only a part should dissapear (clipped) etc.
    way around: have not tried it yet, but i have the impression that bitmaps have different criteria for clipping, so i am thinking of trying this: appli an empty filter (a filter with params so it does not have any effect on the sprite or in the textfield) so the sprite is rendered as bitmap before doing anything else with it. as i said, i have not done it yet, but it may be a way around this problem, to avoid all this inconsistency with clipping
    1-b. inconsistency between hierarchy and coordinates, specially masks: you apply a mask to a sprite, yet the sprite has a set of coordinates (so 'x' in the sprite means an x relative to its container), yet the mask applied to the very same sprite, as another reference as reference for coordinates (like the stage)
    2. painting via script: in any other languaje, in any other situation, something like:
    beginFill(params);
    (...stuff 1)
    endFill();
    beginFill(params);
    (...stuff 2)
    endFill();
    (...etc)
    means: render region of block 1, then render region of block 2 etc, and no matter what, it should be consistent, since there is noplace for ambiguity. if you read it, you may think what that means, even if you dont run it you may have an idea of the picture you want to draw, but not with as3. as3 somehow manages to screw something that simple, and mixes all the blocks, and somehow uses the boundaries of one block as boundaries for other block. is like all blocks are dumped into whatever, and then uses all lines defined into it as boundaries for a unique block. it changes all boundaries and generates inconsistency between what is shown and redraw regions of the resulting picture, like lines that go to the end of the screen and then dont go away in the next frames, even tough the beginfill endfill block should prevent it
    3. event flow: i dont know what was the policy behind as3 event flow design. it is in no way similar or an extension to previous event flow, neither with any event flow in any other plattform. i dont know how most people start with as3; in my case, i unpacked, installed and when i tried to do something with what i already knew i could not, so i started reading the as3 docs, and since is like 800 pages long, i just read the basics and the rest i would 'wing it'. in the part of the event flow, there was something about bubbling and stuff, it was not clear at all and when i tried to do what is was said in the documentation (like preventing events to 'bubble', as is called in the documentation), i could not see any effect but i could see it was a mess. flash is not the only thing out there to work with pictures or to work with mouse events, but is the only one that deals with things like 'target' and 'currentTarget'. my first experience on needing this was when i was dealing with my own event handlers (so the only thing that had control over mouse was the stage, and i would admin everything via script). there were events generated everywhere, the stage got events that were not genrated directly over the stage, but got there not with stage coordinates but the coordinates relative to the sprite that generated the event. so if i hover the mopuse over the stage, and the stage has some things on it how does it work? i get multiple event calls, like it was hovering multiple times over the stage in a single frame, but in each call with different coordinates? and what if i set all child sprites as mouseenabled=false or compare like 'if (event.target != event.currenttarget)', what if i move the mouse over a child, does it prevent the move mouse event at all? or does it filter only the event call with only stage coordinates? in my case, every time i move over another clip (with mouseenabled = true), the stage gets it as 'mouse up', even tough there was never a mouse release, what the hell? do even the people at adobe know how to handle events with their own tool when they require it? why does an event 'bubble' when i have not specifically tell it to do it? mi thought is that this event flow was very poorly conceived, and tough the intention may have been that there were different cases and it shopuld cover all cases, they actually introduced new problems that were not present in traditional ways to handle it, and it is neither the easier way to handle things, and this way, a very simple problem turns into a very ugly thing because it must handle things that were not neccesary to handle, or were implicit in other situations.
    4. legacy: since as3, all interaction is different, and if you want to do things in the new plattform, using the new features, what you already knew just goes to the garbage can. when a new tool arrives, it should be an extension to previous tools (which is a reason to update instead of just buying a new tool from a different vendor). if everything i had or knew just means nothing from now on, then i can not say 'i know flash script', and my previous knowledge gives me no advantage when aproaching the new version. as3 is a new aproach that requires doc reading and stuff, even if you knew something about previous as specifications or other oo languajes. if you decide to change things from now on, like the things mentioned in this post, instead of just throwing away everything the users alerady knew about the tool, do like in java releases, they mark some things as 'deprecated', they keep working as they should, give a warning, but also a message saying this feature is deprecated, we suggest you use this library instead.
    5. lack of previous functionality: if you 'update' something, it meand all previos functionality is still there (probably improved, but not with bugs if it was working fine), plus something else. now it seems backwards, there are some things that could be done in previous versions but not in this one, like 'duplicatemovieclip'
    6. inconsistency with scripting/programming paradigms: (ok, fancy work, but fits perfectly here): as3 proposed ways to handle things, but the people who designed it got 'too creative', and they did something that is not consistent neither with previous versions of as or with other languajes. the documentations is full of things like 'it looks like x languaje or languaje family, but instead of using XXX word, you must use YYY'. great, what is this? namespaces 'work like', but 'differently' for example from java, .net, .c. its got the idea that a namespace means a grouped functionality but there are rules about where should be placed the file (ok, java has this also, .net takes care of it automatically if all files are registered in the project), but what you got is a mess that 'if you know other languajes you got the general idea, but nonetheless, even if you knew this or previosu versions of as, you still have to read whatever we decided arbitrarily just to be different'. namespaces, event handling, vars definition which is not like previous scripting neither like fully typed languajes.. is just a mess.
    7. lack of scripting and graphics integration: unlike flash and adobe tools that just got on the graphics side leaving all the scripting integratuion apart, most tools from other vendors integrate very well interacton with what is on the screen. the script editor: very poor. autocompletion? a drop down list that does not heklp at all, appears in the wrong places, and when you need it to go, it does not go (so if i want to move away from the uncalled drop down list, i have to click somewhere else, making developement slowewr instead of helping, so the drop down list does not capture all events when i dont want to). in other ides you double click somewhere and it will go to the part of code relevant to that event or whatever. for example microsoft tools, ok i am antimicrosoft, and one of the reasons was that when windows 95 got to market proposing itself as the ONLY pc os you could use if you wanted to keep useing the apps you already had, it was a lousy product full of flaws but you had to keep using it because you had no choice. what is so different from what is happening with flash just now? yet the ide of c# is awesome, works very well and seems reliable.
    adobe people: not all user are designers that just make pretty pictures. if it is not intended for scripting then why is it there. and if there are corrections to be done, they should patch all versions, not only the last one. previous version users also paid for their versions.

    Well, there is no point in arguing.
    I personally believe AS3 does exactly what it promises to do within limits (read: reasonable limits) of ECMA type of language. And sometimes it doesn’t do what we expect it to for it cannot possibly emulate everyone’s thinking process. The task, I guess, is to learn to think in terms of AS3 – not to try to make AS3 think like us. No language covers all the grounds. And no, it is not Java - with no negative or positive connotation. It is what it is. Period. I just hope that AS5 will be more Java like.
    You are right about the fact that it is not necessary to know all the aspects of language in order to perform the majority of tasks. But it is paramount to have a clear idea about such fundamental concepts as display list model and events. For instance, depth swap has no meaning in terms of AS3 because display list object stacking is controlled automatically and there is no need for all these jumping through hoops one has to perform in order to control depth in AS2. There no more gaps in depths and one always know where to find things.
    Similarly, there is no point in having duplicateMovieClip method. More conventional OOP ways of object instantiation accomplishes just that and much more. Just because OOP object instantiation needs to be learned doesn’t mean past hacks have place in modern times. duplicateMovieClip is a horse carriage standing next to SUV. What one should choose to travel?
    Events are implemented to the tee in the context of ECMA specifications. I consider Events model as very solid, it works great (exactly as expected) and never failed me. True, it takes time to get used to it. But what doesn’t?
    By the way, speaking about events, contrary to believe in Adobe’s inconsideration to their following. Events are implemented with weakly reference set to false although it would be better to have it set to true. I think this is because there are smart and considerate people out there who knew how difficult it would be for programming novices to deal with lost listeners.
    I think AS3 is million times better than AS2. And one of the reasons it came out this way is that Adobe made a very brave and wise decision to break totally loose from AS2’s inherent crap. They have created a totally new and very solid language. If they had tried to make it backward compatible – it would be a huge screw up, similar to how our friends at Microsoft are prostituting VB and VBA – extremely irritating approach IMHO.
    Also, Flash legacy issues shouldn’t be overlooked. Flash did not start as a platform for programmers. Entire timeline concept in many ways is not compatible with the best OOP practices and advancements. I think for anyone who is used to writing classes the very fact of coding on timeline sounds awkward. It feels like a hack (and AS2 IS a pile of hacks) – the same things can be nicely packaged into classes and scale indefinitely. As such I wouldn’t expect Adobe to waste time on hacking timeline concept issues by making smarter editor. They have made a new one – FlexBuilder – instead. Serious programmers realize very soon that Flash IDE is not for developing industrial strength applications anyway. So, why bother with channeling great minds into polishing path to the dead end?
    I would like to state that all this is coming form a person who knew Flash when there was no AS at all. And I applaud every new generation of this wonderful tool.
    I believe Adobe does a great job making transition from timeline paradigm to total OOP venue as smooth as possible. And no, they don’t leave their devoted followers behind contrary to many claims. They are working on making developing Flash applications as easy as possible for people of all walks. Welcome Catalyst!
    Of course there is not enough information about AS3 capabilities and features. But, on the other hand, I don’t know any area of human kind activities that does.

Maybe you are looking for

  • Servlet  encoding problem

    Hi, I have a servlet which need to send xml(Which can have any unicode characters) as response. Below are my trails. *1>>>* PrintWriter out = response.getWriter(); response.setContentType("text/xml;charset=ISO-8859-1"); out.write("<?xml version=\"1.0

  • Problems in Transformation !!!

    I configured Transformation for a local database. And By using the following query , I checked transformation statistics. SQL> SELECT 2 RULE_NAME, 3 AC.NVN_NAME ACTION_CONTEXT_NAME, 4 AC.NVN_VALUE.ACCESSVARCHAR2() ACTION_CONTEXT_VALUE 5 FROM DBA_RULE

  • Photoshop CS4 Extended Upgrade Problem

    I tried to install CS4 Extended Upgrade, and when it asks what previous version I have, the only version that is listed is CS3 Extended. I have Photoshop CS. How do I go about upgrading? I hope I purchased the proper version, as there is no mention o

  • How to maintain route text in spanish or any other language..

    Hi All, I have defined a new route in SPRO under ' Define Routes' and now I need to maintain the route description in four other languages other than english. I could not find any such customizing in SPRO.. Can anyone please tell how do I maintain ro

  • UDF to sum the line items

    Hi, I am looking for UDF to add data from multiple line items and create single target item. The line items are in order. We need to keep adding the value until their is change in key. Source Field1  key-Field2 Filed3 name1   1001          100 name1