Comments on: SuperTextInput – Building a Custom Component in Flex 4

By: Jimmy Johns

Jimmy Johns — Tue, 10 Jan 2012 18:39:08 +0000

I upgraded to Flash Builder 4.6 and now get the following errors:

“Overriding a function that is not marked for override”

That error is at Line 1 which is:

package dashboard.components {

and line 35, which is:

public function get prompt():String {

Then, I get another error:

“A conflict exists with inherited definition spark.components.supportClasses:SkinnableTextBase.promptDisplay in namespace public.”

This is at line 16, which is:

public var promptDisplay:Label;

davi’s solution above was unsuccessful in fixing this problem. Please help!

By: davi

davi — Tue, 22 Nov 2011 18:51:53 +0000

@Rico, yep, to have this component working with the filterFunction, you must dispatch the TextOperationEvent.CHANGE event!

private function clearClick(e:MouseEvent):void {
    text = "";
    dispatchEvent(new TextOperationEvent(TextOperationEvent.CHANGE));
}

By: Erik

Erik — Fri, 09 Sep 2011 19:07:15 +0000

Seems to have broken with Flex 4.5.1. It throws a bunch of compile errors like:

Description Resource Path Location Type
1024: Overriding a function that is not marked for override. PromptingTextInput.as /Flex/src/com/saturnboy/SuperTextInput/components line 30 Flex Problem

By: rico

rico — Fri, 01 Apr 2011 10:17:52 +0000

excellent tutorial and code samples – thank you very much.

Just a little information for the ones using the input in conjunction with a filterFunction (e.g. ArrayCollection). In the clearClick() function you need to dispatch a TextOperationEvent.CHANGE event manually. (Maybe already clear for everyone)

By: justin

justin — Mon, 27 Dec 2010 22:56:06 +0000

@higgins: All positioning is done in the skin itself (as it should be). You should just create a “ClearRightSkin” and swap the left/right attributes of the text field and the button.

By: higgins

higgins — Mon, 27 Dec 2010 16:57:06 +0000

Can you explain why the Clear Button is always on the right? I’m trying to get it on the left of the field, is this a SkinPart issue or is that position set somewhere and I’m not seeing it?

Thanks.

By: justin

justin — Mon, 29 Nov 2010 20:43:44 +0000

@brianj774: Yes. Sorry I wasn’t clear. You must wire skins to components in your application’s CSS. As a component author, I can’t do this wiring for you.

By: brianj774

brianj774 — Mon, 29 Nov 2010 19:59:01 +0000

@Erik & @Justin... I am having this same issue, but on following the suggestions made by Justin, and still having no luck at all, I did some digging, and found some helpful info from polygeek. He says, "That is a Type selector and so will work but only in the Application root. If you try that from inside another component then you’ll see a warning: CSS type selectors are not supported in components: ‘whateverComponentYouAreIn’. You will have to take the above CSS and place it in or in a CSS file that is declared in the ."

By: Saulo Brust

Saulo Brust — Wed, 04 Aug 2010 13:43:26 +0000

Great component!

I am developing a component similar to other features and possibilities. If you want to contribute in some way, or just give such a component, take a look here: http://github.com/brust/SearchInput

By: justin

justin — Tue, 03 Aug 2010 15:34:12 +0000

@Erik: All of my example code is typically packaged one level deep (aka I don't prefix everything with com.saturnboy). So, components are in components, skins are in skins, etc. So if you re-package the SuperTextInput component you need to change the package name in four places:

In the component itself: the package directive.
In the skin: the HostComponent, and optionally in the skin's code if there are any skinClass attributes.
In your code: the xmlns:components namespace
In the CSS: the @namespace components namespace

For your error, you must have missed one of the above. Good luck.