Re: [Flashcoders] AS3 - Button follow cursor within image area

Thanks for the tip Ashim! :-)) On 6/25/08 5:01 AM, Ashim D'Silva [EMAIL PROTECTED] wrote: You can also disable the button and use the image itself as a button. On click on the image, the event will feed you local mouse coords which will tell you which side of the image the mouse is on.

Re: [Flashcoders] as2 - method losing scope when called from timeline.

AS2 is full of mysterious crap, er bugs like this. It's what made Flash such a pain at times. I am s loving AS3... not that it's without it's own quirks... ___ Joseph Balderson, Flash Platform Developer | http://joeflash.ca

Re: [Flashcoders] calling public static methods on Class using getDefinitionByName

On a related note, I noticed this syntax in Flash help this morning: var componentClass:Class = e.target.selectedItem.data as Class; var styles:Object = componentClass[getStyleDefinition].call(this); On Tue, Jun 24, 2008 at 8:27 PM, Patrick Matte | BLITZ [EMAIL PROTECTED] wrote: Ah ok, the

[Flashcoders] FLV ending prematurely in FLVPlayback component

Hi, I am using the FLVPlayback component to serve videos. Users with a slow connection are getting the FLV stopping midway through. I've done some testing and it seems the player thinks the FLV has finished, which it hasn't. This is happening across multiple FLV's. I've tried encoding with no

[Flashcoders] switch statement more efficient than if...else?

Hi guys quick question that came up in a conversation I had the other day - are switch statements more or less efficient than a series of if...else statements in either AS2 or AS3? I'd always thought that the most efficient was the switch al.z

Re: [Flashcoders] switch statement more efficient than if...else?

- Original Message - From: Allandt Bik-Elliott (Receptacle) [EMAIL PROTECTED] To: flashcoders flashcoders@chattyfig.figleaf.com Sent: Wednesday, June 25, 2008 3:12 PM Subject: [Flashcoders] switch statement more efficient than if...else? Hi guys quick question that came up in a

Re: [Flashcoders] FLV ending prematurely in FLVPlayback component

Try using the FLV Metadata Injector into your FLVs http://www.buraks.com/flvmdi/ The problem may be caused by incorrect (ie, rounded down duration value) or corrupted metadata on the FLV. Matt Muller wrote: Hi, I am using the FLVPlayback component to serve videos. Users with a slow

Re: [Flashcoders] switch statement more efficient than if...else?

Switch/case is a bit quicker. On Wed, Jun 25, 2008 at 10:12 AM, Allandt Bik-Elliott (Receptacle) [EMAIL PROTECTED] wrote: Hi guys quick question that came up in a conversation I had the other day - are switch statements more or less efficient than a series of if...else statements in either

Re: [Flashcoders] switch statement more efficient than if...else?

One thing worth noting is switch statement uses strict equality (===) therefore it's not exactly the same as if/else with equality (==). Kenneth Kawamoto http://www.materiaprima.co.uk/ Paul Andrews wrote: Hi guys quick question that came up in a conversation I had the other day - are

Re: [Flashcoders] switch statement more efficient than if...else?

I doubt there's a noticeable difference between a switch and a series of if /else if statements. In AS 3.0 bytecode, though, switches and equivalent conditionals are not necessarily compiled into the same bytecode. In fact, there's a lookupswitch instruction (opcode 0x1b). Of course, any switch

Re: [Flashcoders] switch statement more efficient than if...else?

hey thanks for all of your responses al.z On 25 Jun 2008, at 16:24, Juan Pablo Califano wrote: I doubt there's a noticeable difference between a switch and a series of if /else if statements. In AS 3.0 bytecode, though, switches and equivalent conditionals are not necessarily compiled

Re: [Flashcoders] switch statement more efficient than if...else?

I'd always thought that the most efficient was the switch I know that the haXe compiler uses a jump table, I'm not sure about the AS3 compiler. But as already mentioned there is an extra opcode for switch, and even if the compiler doesn't a jump table, it might use one in the future. So, switch

Re: [Flashcoders] switch statement more efficient than if...else?

Actually, tt is my (perhaps wrong) understanding that this is not the case. In the past, both Macromedia and Adobe sources have stated that switch does not offer a performance boost--just readability and functionality (optional break lines) enhancements over if statements. I have been wrong many

Re: [Flashcoders] switch statement more efficient than if...else?

and switch on Number ? :P I read somewhere that Number was quicker than int though I still can't believe it cedric I'd always thought that the most efficient was the switch I know that the haXe compiler uses a jump table, I'm not sure about the AS3 compiler. But as already mentioned

[Flashcoders] SWF file size differences

Wonder if anyone else has come across this problem. It's definitely weird and to me it looks like a bug. I have a simple fla file. I publish on a Mac and a PC (both with Flash CS3, AS3, Flash Player 9). The resulting SWF is way bigger on the PC (7KB vs 2KB on the Mac) despite the fla being

[Flashcoders] Firefox 3 and flash 8 wmode problem

Has anybody else been experiencing problems with flash player 8 using wmode with Firefox 3? Can't click on any of the flash buttons, using flash player 8 r42. No problem with Firefox 2. ___ Flashcoders mailing list Flashcoders@chattyfig.figleaf.com

Re: [Flashcoders] switch statement more efficient than if...else?

I disagree that switch statements are more readable than if else statements, at least if you put your braces on their own lines. if (true) { // something } else if (true) { // something else } else if (true) { // yet another outcome } I don't think either is more readable than the

RE: [Flashcoders] switch statement more efficient than if...else?

I disagree that switch statements are more readable than if else statements, at least if you put your braces on their own lines. I wouldn't disagree, but I think it's more about personal preference. Maybe it's just aesthetics, but I prefer: switch(b) { case apple: do

RE: [Flashcoders] switch statement more efficient than if...else?

Steven Sacks wrote: I disagree that switch statements are more readable than if else statements, at least if you put your braces on their own lines. I'm a die-hard switch/case guy, but I agree with Steven on this. Neither is inherently easier or harder to read. Of course, I personally prefer

Re: [Flashcoders] switch statement more efficient than if...else?

better way than nested switches that are 3-4 pages long = if/else statements ;) On Wed, Jun 25, 2008 at 11:25 PM, Kerry Thompson [EMAIL PROTECTED] wrote: Steven Sacks wrote: I disagree that switch statements are more readable than if else statements, at least if you put your braces on

Re: [Flashcoders] switch statement more efficient than if...else?

One thing that nobody who writes switch statements seemed to know (me included) is you can (and, apparently, should) write them like this: switch (n) { case 0: { foo(); break; } case 1: { bar(); return; } case 2: { baz();