Key_down and key_up events works for English letters but with Russian
handler doesn't receive this events. It's very interesting. Yes, IME works
only for CJK, there are 3 languages for it as I know.
For stage textinputskin a little correction: softkeyboardtype is working,
but I can't prevent softke
IME is only necessary for CJK languages. Cyrillic languages should work with
regular input.
On Jun 16, 2016, at 12:03 AM, jude wrote:
> For some languages you may need to set the IME mode. But that seems to be
> only for specific languages. I haven't used IME mode before but it looks
> like you
before this new skin i used mobile skin for android and ios, which used
stagetextinputskin. But using hem i had a problem with softkeyboard. i
couldnt use number keyboard for example. its just ignored setting. Also in
some cases i couldnt prevent softkeyboardectivating event. thats why i
dicided t
For some languages you may need to set the IME mode. But that seems to be
only for specific languages. I haven't used IME mode before but it looks
like you may need to set those properties. Harbs may know more about this.
http://flex.apache.org/asdoc/spark/components/supportClasses/SkinnableTextBa
RichEditableText is a lot of code, but if you want to keep debugging, try
following whether it is getting the keyDown event or not and what happens
to it after it gets it.
-Alex
On 6/15/16, 1:21 PM, "Anton Bondarenko" wrote:
>i watched all i use and found that in textinputskin im using
>richedi
i watched all i use and found that in textinputskin im using
richeditabletext
2016-06-16 0:15 GMT+04:00 Alex Harui :
> I couldn't find any mention of this problem on the internet so I don't
> think it is a known issue. If you want to debug into it, try putting
> keyDown, keyUp, and textInput eve
I couldn't find any mention of this problem on the internet so I don't
think it is a known issue. If you want to debug into it, try putting
keyDown, keyUp, and textInput event listeners and see what happens.
-Alex
On 6/15/16, 12:46 PM, "Anton Bondarenko" wrote:
>forgot to add than on PC works
forgot to add than on PC works fine. thats problem on android device and i
didnt test on ios device
2016-06-15 23:36 GMT+04:00 Anton Bondarenko :
> 1. Russian letters are showed in soft keyboard.
> 2. if im using input.text = "{%russian text%}" than all is fine.
> 3. when i want to enter text fro
1. Russian letters are showed in soft keyboard.
2. if im using input.text = "{%russian text%}" than all is fine.
3. when i want to enter text from softkeyboard letters are animated by
click but no text adding to input. if i change soft keyboard locale to
english letters are adding to input correct.
On 6/15/16, 11:03 AM, "Anton Bondarenko" wrote:
>Hey guys!
>I have a question on Apache Flex. The problem is next. Simple
>spark.componentes.TextInput didnt understand utf letters. I mean that i
>can
>enter only numbers and english letters from softkeyboard. but from other
>languages i cant, fo
If I do not set applicationDPI or customRuntimeDPIProvider on desktop then
the only way to "fix" my issue with textinputs is to set:
s|TextInput{
fontSize: 13;
}
in defaults.css in my library project. Then it fixes the issue I have in
desktop version (mobile version was already OK without using
I think the issue is that I am using a library project. In that is most of
my code. Then I have a desktop project and mobile project but because
mobile is set at 160 dpi and default for desktop is 120 that I'm getting
the differences in component layouts. So this was my initial problem.
On Fri, Ma
I fixed my issue by not setting applicationDPI="160" but instead returning
160 always for a custom runtimeDPIProvider for desktop. This seems to work
On Thu, May 19, 2016 at 5:28 PM, Fréderic Cox wrote:
> I found the issue. It is only affecting the desktop preview so not an SDK
> issue but an is
I found the issue. It is only affecting the desktop preview so not an SDK
issue but an issue with scaling. See
https://issues.apache.org/jira/browse/FLEX-34653
I could easily fix this by setting applicationDPI in my desktop app but
that causes the scaling bug as reported in
https://issues.apache.o
Please file a JIRA issue and attach a simple test case including the
-app.xml file.
Thanks,
-Alex
On 5/18/16, 4:15 AM, "Fréderic Cox" wrote:
>I only edited the AIR version since a compiler error showed up when I
>switched. No other changes made.
>
>On Tue, May 17, 2016 at 5:19 PM, Alex Harui w
I only edited the AIR version since a compiler error showed up when I
switched. No other changes made.
On Tue, May 17, 2016 at 5:19 PM, Alex Harui wrote:
> Did you upgrade the -app.xml file? I'm wondering if there are settings in
> there affecting how it shows up.
>
> -Alex
>
> On 5/17/16, 3:23
Did you upgrade the -app.xml file? I'm wondering if there are settings in
there affecting how it shows up.
-Alex
On 5/17/16, 3:23 AM, "Fréderic Cox" wrote:
>MacBook Pro (15-inch, Early 2011)
>
>On Sun, May 15, 2016 at 7:44 AM, Alex Harui wrote:
>
>> What kind of computer do you have? I'm won
MacBook Pro (15-inch, Early 2011)
On Sun, May 15, 2016 at 7:44 AM, Alex Harui wrote:
> What kind of computer do you have? I'm wondering if it is Retina display
> support.
>
> -Alex
>
> On 5/14/16, 11:36 AM, "Fréderic Cox" wrote:
>
> >AIR desktop, but it is a library project which is included i
What kind of computer do you have? I'm wondering if it is Retina display
support.
-Alex
On 5/14/16, 11:36 AM, "Fréderic Cox" wrote:
>AIR desktop, but it is a library project which is included in AIR desktop
>and AIR mobile. Both AIR mobile simulator and desktop show the issue. I'll
>try to fin
AIR desktop, but it is a library project which is included in AIR desktop
and AIR mobile. Both AIR mobile simulator and desktop show the issue. I'll
try to find some time on monday to create a reproducable scenario and file
a JIRA bug. Good to know that it is not an intended change as you noted.
O
On 5/13/16, 5:41 PM, "Fréderic Cox" wrote:
>It is a bit of a guess but I'd say from 13 to 26. I fixed it by setting
>s|TextInput to fontSize:13 in my CSS. Just found it odd that the default
>has changed and I can't find any references about that in release note
>(maybe I'm overlooking it). If n
It is a bit of a guess but I'd say from 13 to 26. I fixed it by setting
s|TextInput to fontSize:13 in my CSS. Just found it odd that the default
has changed and I can't find any references about that in release note
(maybe I'm overlooking it). If nobody else reported this I think it's not
that big
Dramatically? How many pixels?
On 5/13/16, 7:58 AM, "Fréderic Cox" wrote:
>Hi,
>
>I upgraded an existing project from 4.10 to 4.15 and now without any code
>adjustments the TextInput has a higher default height (I did not specify
>any height in the code) and also the font size increased dramati
Hi,
When used on mobile, the ScrollableStageText class is the implementation of the
textDisplay:IEditableText, which is a SkinPart of TextInput, unfortunately the
ScrollableStageText class doesn't support MXML, so you cannot use it in your
own TextInputSkin.mxml
The workaround I found is:
1.
But would flattening our namespaces get around package name collisions
that Carlos ran into? Doing so wouldn't negatively affect Closure's
output, or would it?
-Alex
On 3/8/14 8:54 AM, "Erik de Bruin" wrote:
>The Closure compiler flattens namespaces (dot notation) for us, among many
>other opt
The Closure compiler flattens namespaces (dot notation) for us, among many
other optimisations. There is really no need to be worry about stuff like
that.
The GCC is really an awesome tool, you should check out it's output
sometime, you'll be amazed how much optimisation it achieves if fed a
prope
Hi Alex,
I think this is right since as I see it, generated code for JS takes the
role of somewhat like compiled code, regarding there's no developer use and
it's final. So whatever we do to get more speed the better, id we could get
speed with tricks like that we should change from dot notation t
FWIW, what subsystems or anything requires us to use dot.path expressions
for packages? The original FalconJS developer mentioned to me once that
we should consider having FalconJX flatten the packages
(org_apache_flex_TextInput instead of org.apache.flex.TextInput) because
it looks up faster in J
Hi Erik,
finally refactored and committed the todo list sample to package
"sample.todo" and change the rest to plural ("controllers", "events", and
so on... in this regard I think we have a compiler bug since if I left
singular, the compiler throw warnings that signals "incomplete alias" (over
17
If you are going to use 'org.apache.flex' for you app you run the risk of
collisions with the SDK, which also uses that namespace.
Also, the plural ("events") makes more sense - to me at least - as there
will likely be more classes in that one package: events.firstEvent,
events.secondEvent, events
Hi Erik,
I see the point and I was thinking to introduce "org.apache.flex" to solve
a similar problem I send to this list some days ago thinking that it was a
bug in the compiler, but the problem is the package structure. I prefer
introduce "org.apache.flex" and then maintain packages in singular
As a first try, I'd suggest you rename the "event" package to something
less collision prone, like "events"...
EdB
On Thu, Mar 6, 2014 at 1:29 PM, Erik de Bruin wrote:
> Carlos,
>
> I'm currently looking at the example application. You use 'event' as part
> of the namespace. In FlexJS JS, al
Carlos,
I'm currently looking at the example application. You use 'event' as part
of the namespace. In FlexJS JS, all objects are fully qualified, so where
in AS you would have "new TodoListEvent(TodoListEvent.LOG_TODO)", in JS
that will become "new event.TodoListEvent(event.TodoListEvent.LOG_TODO
Hi Erik,
thanks, I have a version locally without the need of InputHandler goog
class to remove that dependency, but although I'm with you that this
solution should be the right from a design perspective it's not working for
me. The method is getting called due to MXMLDataInterpreter setup interna
Carlos,
In your JS implementation I see you already set up a handler that catches
"input" events and re-casts them as "change" events. This seems like a
perfectly acceptable solution to this issue and much more clean and
intuitive than trying to get the AS side to emit "input" instead of change,
a
Hi Carlos,
We don't have a strict policy on that yet. We could just call event
"input" and kill the textInput event on the SWF side and dispatch it as
"input". That would have backward compatibility problems for Flex users
expecting "textInput", but FlexJS doesn't promise 100% compatibility.
I
I'll try to have a look at this tomorrow.
EdB
On Wed, Mar 5, 2014 at 6:19 PM, Carlos Rovira wrote:
> Hi,
>
> I'm trying to deal with events in JS and I'm finding some troubles. Maybe
> you guys more experienced with google closure could help me to find the
> way.
>
> In old Flex SDK, TextInpu
37 matches
Mail list logo
