Re: TLF IME

But if a component implements IIMESupport, why should the FocusManager turn off IME if it does not implement IFocusManagerComponent? It seems to me that the code should be something like this (which also has the advantage of being clearer and more concise): _lastFocus =

Re: TLF IME

On 9/10/15, 3:06 AM, "Harbs" wrote: >But if a component implements IIMESupport, why should the FocusManager >turn off IME if it does not implement IFocusManagerComponent? > >It seems to me that the code should be something like this (which also >has the advantage of being

Re: TLF IME

On 9/10/15, 7:05 AM, "Harbs" wrote: >Sure. But even if the focus is not going to be handled by FocusManager, >why is it disabling the IME mode? I don’t have a clear recollection of why the code looks like this. I’d have to go digging through the commits to see if it

Re: TLF IME

Sure. But even if the focus is not going to be handled by FocusManager, why is it disabling the IME mode? In my case, setting the focus was probably a mistake. If there’s no focusable objects, shouldn’t the FocusManager fail silently? On Sep 10, 2015, at 4:19 PM, Alex Harui

Re: TLF IME

Yep, that’s the point of IFocusManagerComponent. The thing we think of as the component rarely has focus. Even a TextInput wraps the TextField or RichTextEditor. -Alex On 9/9/15, 2:42 PM, "Harbs" wrote: >Of course, the component does not handle focus itself. That’s

Re: TLF IME

I found the culprit: FocusManager. It has the following code: _lastFocus = findFocusManagerComponent(InteractiveObject(target)); if (Capabilities.hasIME) { var usesIME:Boolean; if (_lastFocus is IIMESupport) {

Re: TLF IME

What is target? findFocusManagerComponent does a walk up the tree looking for certain flags. -Alex On 9/9/15, 2:31 PM, "Harbs" wrote: >I found the culprit: FocusManager. > >It has the following code: >_lastFocus =

Re: TLF IME

Here’s the full class that’s the target: public class TLFContainer extends SpriteVisualElement implements IIMESupport { private var _imeMode:String; public function TLFContainer() { super();

Re: TLF IME

Apparently, the way to go would have been to implement IFocusManagerComponent as well… On Sep 10, 2015, at 12:37 AM, Harbs wrote: > Here’s the full class that’s the target: > > public class TLFContainer extends SpriteVisualElement implements > IIMESupport >

Re: TLF IME

Of course, the component does not handle focus itself. That’s handled by the SelectionManager… On Sep 10, 2015, at 12:41 AM, Harbs wrote: > Apparently, the way to go would have been to implement IFocusManagerComponent > as well… > > On Sep 10, 2015, at 12:37 AM, Harbs

Re: TLF IME

FWIW, I did not figure out what was disabling the IME. I did figure out how to get the IME working though. When the TextFlow gets focus, I just added IME.enabled = true; For the sake of completeness I’m documenting my observations of IME behavior: IME works inline on all Windows browsers and

Re: TLF IME

Can you switch back to Adobe Flex 4.6? Or whatever version of Apache Flex was before we started deferring focus changes to TextInputs? -Alex On 9/2/15, 2:29 AM, "Harbs" wrote: >Neither of those two seem to be in use. I’m exploring other focus >redirecting possibilities,

Re: TLF IME

Neither of those two seem to be in use. I’m exploring other focus redirecting possibilities, but so far no luck… On Sep 2, 2015, at 8:03 AM, Alex Harui wrote: > IIRC, there can be issues if parent display objects have tabEnabled and/or > tabChildren set to false. > > -Alex >

Re: TLF IME

IIRC, there can be issues if parent display objects have tabEnabled and/or tabChildren set to false. -Alex On 9/1/15, 9:32 AM, "Harbs" wrote: >OK. > >I just put together a non-Flex case and it seems to work in all three Mac >browsers: > >package >{ > import

Re: TLF IME

OK. I just put together a non-Flex case and it seems to work in all three Mac browsers: package { import flash.display.Sprite; import flash.system.Capabilities; import flash.system.IME; import flash.text.TextField; import flash.text.TextFieldType;

Re: TLF IME

First, build a non-Flex test case. Then file that test case at bugbase.adobe.com. -Alex On 9/1/15, 7:48 AM, "Harbs" wrote: >I’m not sure if this is a TLF issue or a Flash player issue. > >I’m getting different results in different browsers. Who would we contact >at

Re: TLF IME

I’m not sure if this is a TLF issue or a Flash player issue. I’m getting different results in different browsers. Who would we contact at Adobe to report this issue in Flash? On Aug 31, 2015, at 11:59 AM, Harbs wrote: > It looks to me that IME is completely broken in

TLF IME

It looks to me that IME is completely broken in the recent versions of TLF. It seems to work in Firefox and Safari on Mac (at least at the bottom of the screen), but does not work in Chrome on Mac or any browser on Windows. Has anyone else noticed this? Harbs