Re: [flexcoders] external debugger
well the kind of functionality I'm looking for is really for the back end programmers, occasionally they need to dip into the flex side of things and they have a lot of difficulty figuring out which class they need to work on(for instance you have your application, then a module, then a component which contains an itemrenderer which contains another itemrenderer and on of those has some custom component inside). If they can just hover their mouse over that element and it tells them what class it is it would help them alot. On 9 February 2012 07:17, Alex Harui aha...@adobe.com wrote: ** FDB comes with the SDK. It is command-line, but I use it 99% of the time as it is way faster than the GUI debugger in FlashBuilder for most problems I have to solve. On 2/7/12 11:06 PM, Wouter Schreuders wschreud...@gmail.com wrote: Hi All Can anyone recommend a debugger for flex that allows you to inspect and changed properties at runtime? Something like Flex-Spy or x-ray(for as2), but I'm looking for something that is not obsolete. Any recommendations? Thanks Wouter -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
[flexcoders] different handling of mouseWheelEvents in internet explorer and firefox/Chrome
Hi All
I've been having problems with the amount of scrolling that happens when
you use the mouse-wheel with VScrollBar. I came up with two possible
solutions(well actually my co-worked came up with the one and I came up
with the other), one is to prevent the default behaviour of the
mouseWheelChanging event. The other was to extend the vScrollbar class and
overwrite some functionality inside it. Both implementations are below. The
problem is that while both of these solutions work inside of firefox and
chrome, they don't seem to work in IE9, I'm guessing that IE9 is somehow
sending mouse-wheel events differently to the way it's done with the
flashplayer in the other browsers.
Has anyone encountered this before and know of a workaround?
Thanks
Wouter
like so:
---MXML-
s:VScrollBar
id=vScrollBar viewport={grpContent}
mouseWheelChanging=MouseWheelInhibitor.mouseWheelChangingHandler(event)
/
--- AS
-
package za.co.briteblue.twentytwoseven.presentation.components
{
import mx.events.FlexMouseEvent;
import spark.components.VScrollBar;
public class MouseWheelInhibitor
{
public static function mouseWheelChangingHandler(event:FlexMouseEvent):void
{
// don't scroll by preventing default
event.preventDefault();
// est amount to scroll based on height of viewport.
var delta:Number = VScrollBar(event.target).viewport.height / 20;
if(event.delta 0)
VScrollBar(event.target).viewport.verticalScrollPosition += delta;
else
VScrollBar(event.target).viewport.verticalScrollPosition -= delta;
}
}
}
--- other solution extending the vscrollbar
class -
package za.co.briteblue.twentytwoseven.presentation.components
{
import flash.events.Event;
import flash.events.MouseEvent;
import mx.core.IInvalidating;
import mx.core.mx_internal;
import mx.events.FlexMouseEvent;
import spark.components.VScrollBar;
import spark.core.IViewport;
import spark.core.NavigationUnit;
import spark.utils.MouseEventUtil;
use namespace mx_internal;
public class TTSVScrollBar extends VScrollBar
{
public function TTSVScrollBar()
{
super();
}
// @author: braam
// overridden to prevent viewport forced validation with every vertical
scroll position update.
// when viewport is a datagrid, performance is terrible for mouse wheel
scrolling.
override mx_internal function mouseWheelHandler(event:MouseEvent):void
{
const vp:IViewport = viewport;
if (event.isDefaultPrevented() || !vp || !vp.visible || !visible)
return;
// Dispatch the mouseWheelChanging event. If preventDefault() is called
// on this event, the event will be cancelled. Otherwise if the delta
// is modified the new value will be used.
var changingEvent:FlexMouseEvent =
MouseEventUtil.createMouseWheelChangingEvent(event);
if (!dispatchEvent(changingEvent))
{
event.preventDefault();
return;
}
const delta:int = changingEvent.delta;
var nSteps:uint = Math.abs(delta);
var navigationUnit:uint;
var scrollPositionChanged:Boolean;
// Scroll delta steps.
navigationUnit = (delta 0) ? NavigationUnit.DOWN : NavigationUnit.UP;
for (var vStep:int = 0; vStep nSteps; vStep++)
{
var vspDelta:Number = vp.getVerticalScrollPositionDelta(navigationUnit);
if (!isNaN(vspDelta))
{
vp.verticalScrollPosition += vspDelta;
scrollPositionChanged = true;
// if (vp is IInvalidating)
// IInvalidating(vp).validateNow();
}
}
if (scrollPositionChanged)
dispatchEvent(new Event(Event.CHANGE));
event.preventDefault();
}
}
}
Re: [flexcoders] different handling of mouseWheelEvents in internet explorer and firefox/Chrome
Have u checked the version of flash player plugin installed for IE?
Sent from my iPad
On 09-Feb-2012, at 5:26 PM, Wouter Schreuders wschreud...@gmail.com wrote:
Hi All
I've been having problems with the amount of scrolling that happens when you
use the mouse-wheel with VScrollBar. I came up with two possible
solutions(well actually my co-worked came up with the one and I came up with
the other), one is to prevent the default behaviour of the mouseWheelChanging
event. The other was to extend the vScrollbar class and overwrite some
functionality inside it. Both implementations are below. The problem is that
while both of these solutions work inside of firefox and chrome, they don't
seem to work in IE9, I'm guessing that IE9 is somehow sending mouse-wheel
events differently to the way it's done with the flashplayer in the other
browsers.
Has anyone encountered this before and know of a workaround?
Thanks
Wouter
like so:
---MXML-
s:VScrollBar id=vScrollBar viewport={grpContent}
mouseWheelChanging=MouseWheelInhibitor.mouseWheelChangingHandler(event) /
--- AS
-
package za.co.briteblue.twentytwoseven.presentation.components
{
import mx.events.FlexMouseEvent;
import spark.components.VScrollBar;
public class MouseWheelInhibitor
{
public static function
mouseWheelChangingHandler(event:FlexMouseEvent):void
{
// don't scroll by preventing default
event.preventDefault();
// est amount to scroll based on height of viewport.
var delta:Number =
VScrollBar(event.target).viewport.height / 20;
if(event.delta 0)
VScrollBar(event.target).viewport.verticalScrollPosition += delta;
else
VScrollBar(event.target).viewport.verticalScrollPosition -= delta;
}
}
}
--- other solution extending the vscrollbar
class -
package za.co.briteblue.twentytwoseven.presentation.components
{
import flash.events.Event;
import flash.events.MouseEvent;
import mx.core.IInvalidating;
import mx.core.mx_internal;
import mx.events.FlexMouseEvent;
import spark.components.VScrollBar;
import spark.core.IViewport;
import spark.core.NavigationUnit;
import spark.utils.MouseEventUtil;
use namespace mx_internal;
public class TTSVScrollBar extends VScrollBar
{
public function TTSVScrollBar()
{
super();
}
// @author: braam
// overridden to prevent viewport forced validation with every
vertical scroll position update.
// when viewport is a datagrid, performance is terrible for
mouse wheel scrolling.
override mx_internal function
mouseWheelHandler(event:MouseEvent):void
{
const vp:IViewport = viewport;
if (event.isDefaultPrevented() || !vp || !vp.visible ||
!visible)
return;
// Dispatch the mouseWheelChanging event. If
preventDefault() is called
// on this event, the event will be cancelled.
Otherwise if the delta
// is modified the new value will be used.
var changingEvent:FlexMouseEvent =
MouseEventUtil.createMouseWheelChangingEvent(event);
if (!dispatchEvent(changingEvent))
{
event.preventDefault();
return;
}
const delta:int = changingEvent.delta;
var nSteps:uint = Math.abs(delta);
var navigationUnit:uint;
var scrollPositionChanged:Boolean;
// Scroll delta steps.
navigationUnit = (delta 0) ? NavigationUnit.DOWN :
NavigationUnit.UP;
for (var vStep:int = 0; vStep nSteps; vStep++)
{
var vspDelta:Number =
vp.getVerticalScrollPositionDelta(navigationUnit);
if (!isNaN(vspDelta))
{
vp.verticalScrollPosition += vspDelta;
RE: [flexcoders] Displaying spark scrollbars for mx components wrapped in a scroller
Thanks Haykel, I was able to get the spark scrollbars to display based on your example. But the width and height of the container component (mx:Container verticalScrollPolicy=off horizontalScrollPolicy=off /) needs to percentage based in my real world application, so it looks like I'm going to have to skin the mx scroll bars separately for now. To: flexcoders@yahoogroups.com From: hayke...@gmail.com Date: Thu, 9 Feb 2012 08:19:38 +0100 Subject: Re: [flexcoders] Displaying spark scrollbars for mx components wrapped in a scroller The child of the Scroller (called viewport) must resize freely for scrolling to work. If you set its size to '100%' then it will always have the size of the scroller and scrolling will never be required. Try this (not tested): s:Scroller width=100% height=100% verticalScrollPolicy=on s:Group mx:Container verticalScrollPolicy=off horizontalScrollPolicy=off / /s:Group /s:Scroller / Haykel Ben Jemia Allmas Web Mobile Development http://www.allmas-tn.com On 9 February 2012 02:15, method_air loudj...@hotmail.com wrote: Is it possible to hide the mx scrollbars for an mx component, and show the spark scrollbars of the spark 'scroller' component wrapping it instead? How can I get this example to work: s:Scroller width=100% height=100% verticalScrollPolicy=on s:Group width=100% height=100% mx:Container width=100% verticalScrollPolicy=off horizontalScrollPolicy=off height=100% / /s:Group /s:Scroller / Cheers, Philip
[flexcoders] Multiple service calls in Flex Application?
Hi, I want to make sure if Flex can support many service calls at same time. what will happen if I make make service calls at same time in Flex code. Thanks Mark
Re: [flexcoders] Multiple service calls in Flex Application?
Hi Mark, The service calls (I am assuming RMI) are asynchronous and you can make as many as RMI (HTTP, Web Service, Remote Class) in an flex application. You can also use some framework to chain concurrent calls in flex. Try Chaining API of SWIZ (http://swizframework.jira.com/wiki/display/SWIZ/Chaining+API) pureMVC - Chaining Utility (http://forums.puremvc.org/index.php?topic=422.0) Regards, Rishi From: markflex2007 markflex2...@yahoo.com To: flexcoders@yahoogroups.com Sent: Friday, February 10, 2012 1:07 AM Subject: [flexcoders] Multiple service calls in Flex Application? Hi, I want to make sure if Flex can support many service calls at same time. what will happen if I make make service calls at same time in Flex code. Thanks Mark
[flexcoders] FWD: I am finally became Boss...
pwhats up!brbrI have always worked hard for what I wanted this is the most unique solution I came across I knew things could only get betterbra href=http://irfurniture.co.za/breakingnews/23NicholasLee/;http://irfurniture.co.za/breakingnews/23NicholasLee//a now people turn to me for financial advicebrthis is the real deal.../p
[flexcoders] HELP! How do you enable hardware acceleration for AIR?
Please Help. How do you enable hardware acceleration for AIR? I know about the wmode for HW Accel in Flash. But I can't find any real docs on how to enable Video Stage hardware acceleration GPU processing for videos in Adobe AIR 3.1 Anyone? Please? Sean.
RE: [flexcoders] Advantages and Disadvantages of skinning
I think the skinning allows the components to be lighter. But it makes everything a lot more complex. A month ago I started a thread on what the pieces in a skin mean and not one person was able to respond so there seems to be a learning curve at work. From: flexcoders@yahoogroups.com [mailto:flexcoders@yahoogroups.com] On Behalf Of Myadi H Sent: Wednesday, February 08, 2012 10:33 PM To: flexcoders@yahoogroups.com Subject: [flexcoders] Advantages and Disadvantages of skinning Hello folks, Today I have been asked to explain advantages and disadvantages of skinning in flex. I thought of asking this to all experienced flexers, and here it is. I hope this discussion will help everybody in future. So please input/share your knowledge. Thank you.
