TextInput Bug?
I noticed a bug when using the qnx.ui.text.TextInput and flash.text.TextField (type entry) using SDK 0.9.1 under Mac OS X.
If the input field is located in the lower part of the screen, where the keyboard displayed, after the input field is pushed upward above the keyboard each entered character will diminish its position Y, pushing further to the top of the screen with every keystroke. This does not occur if the original location of the input field is in half top of the screen.
In addition, if the flash.text.TextField (input type) is used, its position there will also decrease with each strike no matter where she's original position is.
A known bug that is similar to the following with regard to the panels of the dialog box has been reported. It could be related.
Tags: BlackBerry Developers
Similar Questions
-
TextInput bug when the desktop deployment
Hi, I test my application locally and on the Simulator. Since the new SDK I can no longer test my application locally correctly, since I can instantiate is no longer the TextInput class. This is the error:
VerifyError: Error #1014: Class qnx.pps::PPSChannel could not be found. at qnx.ui.text::TextInput/init()[E:\hudson\workspace\SDK092_deckard_sdk\src\screen\src\qnx\ui\text\TextInput.as:486] at qnx.ui.core::UIComponent()[E:\hudson\workspace\SDK092_deckard_sdk\src\screen\src\qnx\ui\core\UIComponent.as:162] at qnx.ui.core::SkinnableComponent()[E:\hudson\workspace\SDK092_deckard_sdk\src\screen\src\qnx\ui\core\SkinnableComponent.as:43] at qnx.ui.text::TextInput()[E:\hudson\workspace\SDK092_deckard_sdk\src\screen\src\qnx\ui\text\TextInput.as:370] at Diagram.mindmap::MindmapElement/onClick()[C:\Users\Bram\Adobe Flash Builder Burrito Preview\Mindmaps\src\Diagram\mindmap\MindmapElement.as:169]This line 169:
textInput = new TextInput();
other people here have already said that they, too, can no longer test locally since the new SDK.
I suggest replace the QNX TextInput with a Flash / MX / component Spark TextInput for local testing, then just throw in when you want to test on the Simulator.
-
Hello
I have a textinput limited to '0-9' (per textInput.restrict). On android, it works. The office, it works. On iOS emulator flex, it works. On a real iPad, I can type any character in the field.
I can't find information on this parameter not supported on iOS, so it's probably a bug. Have you noticed this problem? I could probably code a workaround to the onChange event solution, but it should be difficult, or the less documented.
In addition, it would be nice to have a function to change the softKeyboard layout (native applications can trigger a keyboard with numbers only for example).
Post edited by: Rangora (more details)
Hello
I'm sorry you are facing this problem. This issue is known and will be corrected in the next major release of AIR.
Thank you
Samia
-
Bug when you set the text of a TextInput in MXML
Hello
I upgraded my Playbook Tablet OS version 2.0.0.6149 previous beta (I think it was 2.0.0.4xxx). Since then, my application written in Flash Builder 4.6 target AIR 3 fails when I put the text into a TextInput in MXML.
The MXML code is:
<>
ID = "frequencyText" text = "440,000" / >
When I run it, I get the following error:
TypeError: Error #1009: cannot access a property or method of a null object reference.
at qnx.stagetext.ui.text::EditableText/setAreaOfInterest() [/ home/builder/hudson/workspace/GR2_0_0_CE2-SWF_StageText/src/stagetext/src/qnx/stagetext/ui/text/EditableText.as:792]
at qnx.stagetext.ui.text::EditableText/insertText() [/ home/builder/hudson/workspace/GR2_0_0_CE2-SWF_StageText/src/stagetext/src/qnx/stagetext/ui/text/EditableText.as:1015]
to qnx.stagetext.ui.text::EditableText/set text() [/ home/builder/hudson/workspace/GR2_0_0_CE2-SWF_StageText/src/stagetext/src/qnx/stagetext/ui/text/EditableText.as:303]
to flash.text:
tageText/set text()to spark.components.supportClasses:
tyleableStageText/set text() [E:\dev\4.y\frameworks\projects\mobilecomponents\src\spark\components\supportClasses\StyleableStageText.as:1143]to spark.components.supportClasses:
kinnableTextBase / textDisplayAdded () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\supportClasses\SkinnableTextBase.as:2315]to spark.components.supportClasses:
kinnableTextBase / partAdded () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\supportClasses\SkinnableTextBase.as:1751]at::TextInput/partAdded() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\TextInput.as:354] spark.components
to spark.components.supportClasses:
kinnableComponent / findSkinParts () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\supportClasses\SkinnableComponent.as:736]to spark.components.supportClasses:
kinnableComponent / attachSkin () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\supportClasses\SkinnableComponent.as:701]to spark.components.supportClasses:
kinnableComponent / validateSkinChange () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\supportClasses\SkinnableComponent.as:443]to spark.components.supportClasses:
kinnableComponent / createChildren() () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\supportClasses\SkinnableComponent.as:406]at mx.core::UIComponent/initialize() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7634]
to mx.core::UIComponent /() http://www.adobe.com/2006/flex/mx/internal:childAdded [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7495]
at mx.core::UIComponent/addChildAt() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7199]
at::Group/addDisplayObjectToDisplayList() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:2037] spark.components
to spark.components::Group /() http://www.adobe.com/2006/flex/mx/internal:elementAdded [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:1628]
at::Group/setMXMLContent() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:633] spark.components
at::Group/createChildren() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:855] spark.components
at mx.core::UIComponent/initialize() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7634]
to mx.core::UIComponent /() http://www.adobe.com/2006/flex/mx/internal:childAdded [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7495]
at mx.core::UIComponent/addChildAt() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7199]
at::Group/addDisplayObjectToDisplayList() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:2037] spark.components
to spark.components::Group /() http://www.adobe.com/2006/flex/mx/internal:elementAdded [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:1628]
at::Group/setMXMLContent() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:633] spark.components
at::Group/createChildren() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:855] spark.components
at mx.core::UIComponent/initialize() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7634]
to mx.core::UIComponent /() http://www.adobe.com/2006/flex/mx/internal:childAdded [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7495]
at mx.core::UIComponent/addChildAt() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7199]
at::Group/addDisplayObjectToDisplayList() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:2037] spark.components
to spark.components::Group /() http://www.adobe.com/2006/flex/mx/internal:elementAdded [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:1624]
at::Group/setMXMLContent() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:633] spark.components
at::Group/createChildren() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:855] spark.components
at mx.core::UIComponent/initialize() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7634]
to mx.core::UIComponent /() http://www.adobe.com/2006/flex/mx/internal:childAdded [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7495]
at mx.core::UIComponent/addChildAt() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7199]
at::Group/addDisplayObjectToDisplayList() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:2037] spark.components
to spark.components::Group /() http://www.adobe.com/2006/flex/mx/internal:elementAdded [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:1624]
at::Group/setMXMLContent() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:633] spark.components
at::Group/createChildren() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:855] spark.components
at mx.core::UIComponent/initialize() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7634]
to mx.core::UIComponent /() http://www.adobe.com/2006/flex/mx/internal:childAdded [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7495]
at mx.core::UIComponent/addChildAt() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7199]
at::Group/addDisplayObjectToDisplayList() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:2037] spark.components
to spark.components::Group /() http://www.adobe.com/2006/flex/mx/internal:elementAdded [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:1628]
at::Group/setMXMLContent() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:633] spark.components
to spark.components::Group / set mxmlContent() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:573]
to spark.components:
kinnableContainer/set mxmlContent() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\SkinnableContainer.as:657]to spark.components:
kinnableContainer / createDeferredContent () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\SkinnableContainer.as:1050]to spark.components:
kinnableContainer / createContentIfNeeded () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\SkinnableContainer.as:1078]to spark.components:
kinnableContainer / createChildren() () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\SkinnableContainer.as:885]at mx.core::UIComponent/initialize() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7634]
at::View/initialize() [E:\dev\4.y\frameworks\projects\mobilecomponents\src\spark\components\View.as:999] spark.components
views: InstrumentTunerHome / initialize)
to mx.core::UIComponent /() http://www.adobe.com/2006/flex/mx/internal:childAdded [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7495]
at mx.core::UIComponent/addChildAt() [E:\dev\4.y\frameworks\projects\framework\src\mx\core\UIComponent.as:7199]
at::Group/addDisplayObjectToDisplayList() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:2037] spark.components
to spark.components::Group /() http://www.adobe.com/2006/flex/mx/internal:elementAdded [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:1628]
at::Group/addElementAt() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:1387] spark.components
at::Group/addElement() [E:\dev\4.y\frameworks\projects\spark\src\spark\components\Group.as:1345] spark.components
to spark.components:
kinnableContainer / addElement () [E:\dev\4.y\frameworks\projects\spark\src\spark\components\SkinnableContainer.as:761]at::ViewNavigator/createViewInstance() [E:\dev\4.y\frameworks\projects\mobilecomponents\src\spark\components\ViewNavigator.as:2018] spark.components
at::ViewNavigator/commitNavigatorAction() [E:\dev\4.y\frameworks\projects\mobilecomponents\src\spark\components\ViewNavigator.as:1932] spark.components
at::ViewNavigator/commitProperties() [E:\dev\4.y\frameworks\projects\mobilecomponents\src\spark\components\ViewNavigator.as:1301] spark.components
Best regards
Ben
In Flex 4.6 Adobe had changed the TextInput control to use StageText instead of TextField. The native implementation of StageText PlayBook is basically a version not stripped of the qnx.fuse.ui.TextInput. There are some use cases that throws an error our implementation of StageText.
The solution for now is to put a skin.
We are working on a fix for version 2.0 of the final tablet. It is also worth noting that this error comes from a code that is on the device and not in the SDK.
-
As it seems that the FocusManager is null of a TextInput tends in a pop up-> skin causes bad state of the TextInput - normal istead of normalWithPrompt and if the promptDisplay is not displayed as it should. The question is how properly configure the TextInput focus Manager is not null when it is a pop up? When the TextInput is not in a-pop, it works perfectly...
The pop up is defined like this:
< s:PopUpAnchor id = "popUpAnchor" left = "20" right = "0" top = low "0" = "0".
popUpPosition = "bottom" >
< s:Group id = menu "dropdown" >
< s:TextInput id = "otherPhoneTI" width = "100" height = "23".
prompt = "Enter phone number" / >
< / s:Group >
< / s:PopUpAnchor >
I add the pop using the DropDownController like this:
dropDownController = new DropDownController();
dropDownController.openButton = openButton;
dropDownController.dropDown = drop-down list.
dropDownController.addEventListener (DropDownEvent.OPEN, dropDownController_openHandler);
dropDownController.addEventListener (DropDownEvent.CLOSE, dropDownController_closeHandler);
private void dropDownController_openHandler(event:DropDownEvent):void
{
callButtonView.popUpAnchor.displayPopUp = true;
}
private void dropDownController_closeHandler(event:DropDownEvent):void
{
callButtonView.popUpAnchor.displayPopUp = false;
}
I fixed that with a group extended as a drop down list which is the first element inside the popUpAnchor. It looks like this:
package com.dialog.voxi.components.common
{
Import mx.core.IFlexDisplayObject;
Import mx.managers.IFocusManagerContainer;
Import spark.components.Group.
SerializableAttribute public class PopUpGroup extends implements Group IFocusManagerContainer
{
public void PopUpGroup()
{
Super();
}
public function get defaultButton (): IFlexDisplayObject
{
Returns a null value.
}
public function set defaultButton(value:IFlexDisplayObject):void
{
}
}
}
If anyone knows if this is the right way to do it or there is a better one, please let me know. Thank you!
-
I'm working on a text messaging system and I want to erase the TextInput, after that the user sends the message. The message can be sent using the "send" button or by pressing the RETURN key when the "newMessage" TextInput has focus.
It is the corresponding code:
MXML:
<mx:TextInput id="newMessage" width="100%" keyDown="{messageKeyPressed(event);}" />
<mx:Button id="send" label="Send" click="{sendMessage();}" />AS:
private function sendMessage():void {
_comm.sendMessage(newMessage.text);
newMessage.text = "";
}
private function messageKeyPressed(event:KeyboardEvent):void {
if(event.keyCode == Keyboard.ENTER) sendMessage();
}The strange thing is that, if the message is sent using the button 'send' the newMessage text gets deleted, but if the message is sent using the RETURN key, the message is sent (I receive in the other end of the app) but the "newMessage.text" remains with the entered text.
If I have debug him, in the Variables window, I see that the text property of the newMessage object is erased, but the real object is with the same text.
I guessed that it had something to do with the update, so I tried to change the focus to another object before deleting the newMessage.text. It works if I do not change the focus to the object TextInput, but if I change the focus to the "newMessage" TextInput, it isn't clear the text (although it gets highlighted). I could change just concentrate on another object, but is not good from the point of view ease of use.
Any ideas?
Use rather than keyDown keyUp , I think that textField has not finished text changing when keyDown
Another interesting thing is that if you put extra code as popup a warning in your SendMessage() call window, you will get what you want event if you use keyDown.
-
Hi all
can someone please clear my doubt.
Why the input text statement giving a screen empty for playbook, which is the bug with who and how should it be defined, if it works very well.
I checked for playbook of text it displays a screen of blak with textInput, and if I use textField his work well, but the Promt feature will not work with textfield...
Can someone help me please...
I thank in advance
Can you show us an example of code you are using? The TextInput should work fine as a lot of people have used in their applications so far.
Make sure that you have configured using the TextInput correctly.
Make sure that you import the TextInput QNX
Import qnx.ui.text.TextInput;Then, when you want to use
public var myInputBox:TextInput = new TextInput();
myInputBox.prompt = "Type of stuff here."
myInputBox.width = 300;
myInputBox.height = 40;
myInputBox.x = 100;
myInputBox.y = 50;
myInputBox.addEventListener (KeyboardEvent.KEY_UP, myInputHandler);
addChild (myInputBox);then, if necessary, manage the keyboard entry
private void myInputHandler(event:KeyboardEvent):KeyboardEvent {}
//...
} -
Interesting several container Bug in TLF
Hi all
I hit a bit of a roadbump in the development of an AIR application (2.5.1.17730 runtime) by using the TLF and wonder if everyone has seen and come up with a workaround. Examine the mxmxl below. When you run the application, you two columns of text that you expect. Editing (cut, paste, type, undo, redo) all work fine everywhere except when you change the second line of the second column. Then the whole second column is pushed down to the value is in the first column, until what you do a somehwere else edit in the window (for example, put a space in the first column somewhere). I have pored on it for quite a while and arrived at the thoughtful opinion that (a) it's a bug, and (b) I have not the slightest idea what is the cause or how to work around it.
Any suggestions?
Thank you!
<?xml version="1.0" encoding="utf-8"?> <s:WindowedApplication xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" creationComplete="init(event)" viewSourceURL="srcview/index.html"> <fx:Script> <![CDATA[ import flashx.textLayout.container.ContainerController; import flashx.textLayout.conversion.ITextImporter; import flashx.textLayout.conversion.TextConverter; import flashx.textLayout.edit.EditManager; import flashx.textLayout.elements.TextFlow; import flashx.undo.UndoManager; import mx.events.FlexEvent; private var _textContainer:SpriteVisualElement = null; private static const textInput:XML = <TextFlow xmlns="http://ns.adobe.com/textLayout/2008"> <div> <p><span>Qui magna velit consequat, lobortis iriure autem augue duis exerci blandit esse laoreet ex eros, adipiscing aliquip, ut, vel eum. Vero consectetuer dolor feugait dolore lobortis delenit nibh eu, te et in, dolore. Nulla ut enim consequat diam adipiscing nulla facilisis zzril te laoreet at. Iusto quis esse nulla et, aliquam quis, facilisi euismod, diam eros ut dolore commodo erat et ad tation, illum. Autem, qui wisi odio ad vel esse ad ad. Velit vel facilisis iriure, et nisl aliquip iriure zzril. Praesent tincidunt blandit nulla, odio, sed vulputate ipsum dolore duis in veniam iriure zzril minim odio suscipit dignissim wisi. Feugiat, volutpat duis vero ut elit zzril, te commodo duis. Molestie ea erat et volutpat dolore vel molestie consequat tincidunt hendrerit consequat. Euismod, consequat blandit nostrud facilisi qui delenit duis, molestie tation illum accumsan amet dolor feugait molestie ea consectetuer wisi. Adipiscing lobortis, ut veniam nostrud accumsan vero elit dolore ex nulla ullamcorper sit qui. Qui magna velit consequat, lobortis iriure autem augue duis exerci blandit esse laoreet ex eros, adipiscing aliquip, ut, vel eum. Vero consectetuer dolor feugait dolore lobortis delenit nibh eu, te et in, dolore. Nulla ut enim consequat diam adipiscing nulla facilisis zzril te laoreet at.</span></p> </div> </TextFlow>; private var _textFlow:TextFlow; private function init(evt:Event):void { var importer:ITextImporter = TextConverter.getImporter(TextConverter.TEXT_LAYOUT_FORMAT); importer.throwOnError = true; // will throw exception if parsing error occurs on import _textFlow = importer.importToFlow(textInput); _textFlow.flowComposer.addController(new ContainerController(col1, col1.width, col1.height)); _textFlow.flowComposer.addController(new ContainerController(col2,col2.width,col2.height)); col2.x = g1.width*0.55; //adding Select/Edit/Copy/Paste/Undo features _textFlow.interactionManager = new EditManager(new UndoManager()); // initialize with a selection before the first character _textFlow.interactionManager.selectRange(0,0); _textFlow.flowComposer.updateAllControllers(); } ]]> </fx:Script> <fx:Declarations> <!-- Place non-visual elements (e.g., services, value objects) here --> </fx:Declarations> <s:Group x="0" y="0" width="100%" height="100%" id="g1"> <s:SpriteVisualElement x="0" y="0" height="100%" width="45%" id="col1"/> <s:SpriteVisualElement y="0" height="100%" width="45%" id="col2"/> </s:Group> </s:WindowedApplication>There is a bug in the TLF 1.1. He wasn't there in TLF 1.0 and has been fixed in TLF 2.0 (currently pre-release). You have three options:
-You can return to TLF 1.0. If you use Flex 4.1, I think you could do that by putting TLF 1.0 instead of TLF 1.1 in the installation of Flex. Alternately, you could roll back using Flex 4.0.
-You can go ahead to use TLF 2.0. If you are using Flex, this means adopting the pre-commercial version of heroes of Flex.
-You can create your own TLF 1.1 with a fix. I can provide you with the solution, but you will have to recompile TLF 1.1, which means that you cannot use the RSL library version.
I apologize for the inconvenience.
-robin
-
Keyboard.UP touch in s:TextInput brings the cursor caret to the beginning
Example code:
<?xml version="1.0" encoding="utf-8"?> <s:Application xmlns:fx="http://ns.adobe.com/mxml/2009" xmlns:s="library://ns.adobe.com/flex/spark" xmlns:mx="library://ns.adobe.com/flex/mx" minWidth="955" minHeight="600"> <s:layout> <s:VerticalLayout paddingTop="10" paddingLeft="10"/> </s:layout> <s:TextInput id="textInput"> </s:TextInput> <mx:TextInput id="textInput2"> </mx:TextInput> </s:Application>
To reproduce:
(1) place the focus in Spark TextInput and Halo TextInput
(2) to enter text, for example "123456".
(3) press Keyboard.UP
(4) the notice, this caret cursor is moved to the end at the beginning of the text entered
Interactive example: http://jabbypanda.com/sample_case/TextInputCaret/TextInputCaretPosition.html
Is this a bug?
Looks like it's by design. Probably worth filing an enhancement request to
get some control over it.
-
TextInput borderStyle in Flex 4
In Flex 3, it worked but in Flex 4, the border is still displayed. Anyone know if it is a bug (and if so where should I declare it).
<? XML version = "1.0" encoding = "utf-8"? >
" < = xmlns:mx mx:Application ' http://www.Adobe.com/2006/MXML ">
< mx:TextInput borderStyle = "none" / >
< / mx:Application >Thank you
Obviously the wrong... I can now to repro your question.
Initially I was testing with the halo theme, this is the reason why it worked. borderStyle is honoured by the Halo theme, but not the theme of the spark.
for example
-Theme=${FlexLib}/themes/Halo/Halo.swc
So if you see defaults.css for TextInput framework project styles now look like:
TextInput
{
backgroundColor: #FFFFFF;
backgroundDisabledColor: #DDDDDD;
borderSkin: ClassReference ("mx.skins.spark.TextInputBorderSkin");
paddingTop: 2;
paddingLeft: 2;
paddingRight: 2;
}So I think you can do something like:
Kind regards
Corey
-
Think I found a little stupid, oh not a bug.
When you rename my components, so I can easily use everyhting in Flash Builder, I found the following bug...? At least I think.
Rename the items works well, but when I try to rename a repeatedItem in a DataList repeated items will disappear. The structure of my layers and components is ok but there is no visible reason. Really weird.
------------------------------------------------------------------------------------------ ---------
TextInput component reacts exactly the same
------------------------------------------------------------------------------------------ ---------
Cheers, Kevin
Hey Kevin,
I was able to repro cela and filed a bug, but it fixed itself, when I refreshed the artboard (view > refresh the work plan). Who help me?
-Adam
Catalyst engineering
-
TextInput.setFocus () does not work
TextInput.setFocus () doesn't seem to work if the TextInput is in a TabNavigator/ViewStack. Is this a known bug?
I have a TabNavigator in a TitleWindow. There are several VBoxes for each "tab" in the TabNavigator. Each VBox has a form with a TextInput. When the user clicks a tab to display a different VBox in TabNavigator/ViewStack, I want the TextInput that VBox to get the developed and have the cursor placed in it. Using the TabNavigator valueCommit event sets the focus of the TextInput, but does not place the cursor. I tried 'Application.application.systemManager.stage.focus is TextInput', "focusManager.setFocus (TextInput)" and "TextInput.setFocus ()", nothing helps.
No work around or help is greatly appreciated.Sorry, but I put aside the issue of deep links.
Change this line: valueCommit = "changeTabs (event); »
For this: mouseUp = "changeTabs (event); »The problem here is that the valueCommit Flex causes to move focus back to the tab. The mouseUp event works because the valueCommit already was triggered BEFORE the event mouseUp, and now you can move it to the textInput. At least that's what it looks like to me when I draw it.
The focus in your application was just bounce the textInput and back to the new tab. -
OK, it's really absurd, that I use a NumberValidator which, as its name suggests, VALIDATES that a string contains a valid number so if the string IS NOT a valid number he must raise a ValidationResult not VALID.
The thing is that if I set the required of the validator property false (because in my form, this is optional), and then type an invalid number, the validator throws the invalid result. If I set it to true, and then it WORKS.
So, WHAT's THE PROBLEM WITH THAT? It's really absurd that if he ceases to iset the property required to false to validate properly.
Here is the example of the Adobe Flex 2 Language reference itself which if you set the property required to false is not validate correctly. Try it, type something that is not a number ("Hello" for example) and press the button and it won't do anything, it will not throw an invalid result or a valid result either. So HOW DO THIS WORK? having a textInput not required whose power must be a valid number which is validated by a NumberValidator?
< mx:NumberValidator source = property '{age}"="text"integerError ="enter Integer value ".
minValue = maxValue "18" = "50" domain = "int" required = "false".
trigger = "{myButton}" triggerEvent = "click".
valid = "Alert.Show (" Validation Succeeded!'");" / > "
< mx:Panel title = "Example of NumberValidator" width = "75%" height = "75%".
paddingTop = "10" paddingLeft = "10" paddingRight = "10" paddingBottom = "10" >
< mx:Form >
< mx:FormItem label = "enter an age between 18 and 50:" > ""
< mx:TextInput id = "age" width="100%"/ >
< / mx:FormItem >
< mx:FormItem >
< mx:Button id = "myButton" label = "Validate" / >
< / mx:FormItem >
< / mx:Form >
< / mx:Panel >There was a bug in the version of Flex 2. It has been fixed in internal versions and will be available in the next public drop of Flex, which will be soon.
To work around the problem, you can remove the NumberValidator.isRealValue () method and your validator will validate properly. NumberValidator.isRealValue () added a useless isNaN check that caused the bug.
-
I honestly don't understand what is happening, since I've updated for Flex 2.0.1 I found the bug after bug.
This time, to my surprise I found that the errorString property causes a buggy behavior, if I put a string empty this property in order to clean a validation for a TextInput control error then its layout changes, it gets a weird black color on its border.
Try this one
< mx:TextInput id = "buggy" / >
< mx:Button click = "buggy.errorString =" "/ >".
So tell me, why if it WORKED in FLEX 2.0, why because Adobe change? How is it supposed to work now?
Okay, there's one posted by me and posted by michael as 2 workaround for this bug. They are both displayed in this topic please someone who has the same problem, check out this section for workarounds.
Really really hope that Adobe corrects this someday
-
TextInput-people with disabilities-color of much darker background in beta 2
I noticed my disabled TextInputs now have a much darker background with 2 beta with beta 1. the new background I find is much too dark. What was the value before the beta 2? I would go back to this value in my CSS file.
Thank you.Yes, the default background of a disabled person TextInput has been changed because empty disabled TextInput did not look any different from the one that has been activated. The details of this change are in this bug:
https://bugs.Adobe.com/jira/browse/SDK-9642
Joan Lafferty
Maybe you are looking for
-
Cannot type more than 1 letter in the search box of blogs, or google without hanging FF
I'm trying to use the Google search bar, or a search box on a blog, or the subject line in gmail and I have to type a letter because Firefox will in crashes and the mode "not responding" and hangs. This happened the other day when I installed an upda
-
Freeze on startup. New installation takes 3 tries before windows starts:)
I installed a new copy of Vista ultimate on my laptop (Toshiba Qosmio) now every time I have reboot or turn off and then back again I have to press the power on button 3 times. I get a black screen and there I turn it off and do it again same thing a
-
Replacement hard drive (HP Dv6-2155dx)
Hello everyone, my name is Aiko. A week ago, I received a notice of "SMART hard drive detects imminent failure" on my laptop. So devastating! My warranty has expired because this laptop is about 2 years old. I'm trying to understand what hard drive I
-
Connectivity of recorder Panasonic RR-$us450 for Windows 7 64 Bit OS.
I have Windows 7 Home Edition with a 64-bit operating system. I have a model of recorder panasonic RR-$us450 and was able to transfer voice files for my old computer with windows xp. If I understand correctly Panasonic that Windows 7 will only host
-
Update blackBerry Smartphones Marshmallow for unlocked ATT Priv
Hi I was wondering if there is updates when the fix will be available? http://support.BlackBerry.com/kb/articleDetail?articleNumber=000038204&language=English Thank you!