]]> http://reality-and-a-half.multiversum.com/werkzeuge/open-web-fonts-auf-der-typecon-2010/feed 0 http://reality-and-a-half.multiversum.com/produkte/3d-hd-camcorder-von-panasonic http://reality-and-a-half.multiversum.com/produkte/3d-hd-camcorder-von-panasonic#comments Wed, 28 Jul 2010 12:18:46 +0000 Mike http://reality-and-a-half.multiversum.com/?p=228 Panasonic bringt im September den HDC-SDT750 Camcorder auf den Markt. Wesentliches Highlight ist die 3D Funktion, mit der durch eine Vorsatzlinse jeweils zwei Bilder parallel aus unterschiedlichen Perspektiven aufgezeichnet werden. Mit Standard 3D Fernsehern und Abspielgeräten lassen sich die Filme anschauen. Der Einführungspreis soll bei € 1399 liegen.

Here are my steps:

1. Set up the mouse handlers on the chart compound – the most important is the mouseMove event since it is fired everytime the user moves the mouse upon the chart. the over and out Handlers are only for switching the visibility of the DataTip or other objects. I don’t mention them further

   mouseMove="mouseChartHandler(event)" mouseOver="mouseInHandler(event)" mouseOut="mouseOutHandler(event)"

2. Setup functions to hande the events

   private function mouseChartHandler(event:MouseEvent):void { .... }

   private  function mouseInHandler(event:MouseEvent):void { .... }

    private function mouseOutHandler(event:MouseEvent):void { .... }

3. Inside the mouseMove handler function do the following steps:
   1. Define a vertical strip (e.g. 5 px broad) from the top to the bottom with the actual mouse x coordinate
   2. Use the chart series findDataPoints function to capture the item beneath or above the mouse pointer
   3. Use the resulting HitItem to instantiate a DataTip instance (or whatever you need)

That’s it. Easy if one has digged through the bunch of class and function definitions…

Ok, let’s give some code for practical reasons – so here is the code for the mouseMove handler

		private function mouseChartHandler(event:MouseEvent):void {
			// define a region for the findDataPoint function
			var sensitiveRegion:Rectangle = new Rectangle( event.stageX-5, 0, 10, this.document.height);   

            var hitItems:Array = new Array();

            if (event.currentTarget.name =! "lineChart") return;

            for each ( var chartItem:ChartItem in lineChart.getItemsInRegion( sensitiveRegion ) ) {
            	if ( chartItem.element.name == "seriesMean" ) {
            		var item:LineSeriesItem = chartItem as LineSeriesItem;

            		var xTime:Date = item.xValue as Date;
            		var yVal:Number = item.yValue as Number;

            		var dataPoints:Array = seriesMean.findDataPoints( item.x, item.y, 2 );

            		var hitItem:HitData = dataPoints[0];//new HitData( new Date().getMilliseconds()*Math.random(), 1, item.x, item.y, chartItem);

			if (hitItem) {
                  		hitItems.push( hitItem );

						// Add DataTip to stage if not existing
						if ( !this.stageFlyout ) {
							this.stageFlyout = this.addChild( flyout );
						} 

	            		flyout.x = hitItem.x + 60;
	            		flyout.hitData = hitItem;

					}

            	}
            }

Remark: I use a custom DataTip renderer which I instanciated previous as this.stageFlyout

Now you have a DataTip showing everytime the mouse is moving on the chart. To avoid showing both the custom triggered DataTip and the chart’s provided you can either switch the visibility to false if the chart’s built-in DataTip handler shows his info or you simply turn the showDataTips property of the chart compound of ( in MXML showDataTips=”false” ).

So please tell me if I should explain the solution further. Or perhaps you have another one – I would be pleased to add it here . Simply use the comment function.

The tale of Lucasfilm, Skywalker Ranch, Red Tails, Star Wars and Canon DSLRs on a 40 foot screen! | Philip Bloom.

But fortunately it’s very easy to extend Flex components. For a project I was working I pragmatically turned off the visibility of the input field by making the TextInput field child object accessible to the outer world by adding a getter and a setter method for the ComboBase textField class property. This gives us full control over the input field. Instead of just turning visibility off you can of change other properties as the width or height.

The actionscript extension class (DateChooserPopup.as)

package customComponents

{

import mx.controls.DateField;

import mx.controls.TextInput;

public class DateChooserPopup extends DateField

{

public function DateChooserPopup()

{

super();

}

public function set TextInputField( textInput:TextInput ):void {

this.textInput = textInput;

}

public function get TextInputField():TextInput {

return this.textInput;

}

}

}

Now we use the new component within the MXML main file:

<?xml version=”1.0″ encoding=”utf-8″?>

<mx:Application xmlns:mx=”http://www.adobe.com/2006/mxml” width=”640” height=”445” layout=”absolute” backgroundGradientColors=”[#FFFFFF, #FFFFFF]” xmlns:CUSTComp=”customComponents.*“>