Warning: include() [function.include]: Unable to access /var/www/html/rogue-development/blog2/wp-content/advanced-cache.php in /var/www/html/rogue-development/blog2/wp-settings.php on line 62

Warning: include(/var/www/html/rogue-development/blog2/wp-content/advanced-cache.php) [function.include]: failed to open stream: No such file or directory in /var/www/html/rogue-development/blog2/wp-settings.php on line 62

Warning: include() [function.include]: Failed opening '/var/www/html/rogue-development/blog2/wp-content/advanced-cache.php' for inclusion (include_path='.:/usr/share/pear:/usr/share/php') in /var/www/html/rogue-development/blog2/wp-settings.php on line 62

Notice: add_option was called with an argument that is deprecated since version 2.3 with no alternative available. in /var/www/html/rogue-development/blog2/wp-includes/functions.php on line 3468

Notice: register_sidebar_widget is deprecated since version 2.8! Use wp_register_sidebar_widget() instead. in /var/www/html/rogue-development/blog2/wp-includes/functions.php on line 3382

Notice: register_widget_control is deprecated since version 2.8! Use wp_register_widget_control() instead. in /var/www/html/rogue-development/blog2/wp-includes/functions.php on line 3382
Comments on: Profiling experience http://www.rogue-development.com/blog2/2009/07/profiling-experience/ Comments and thoughts on technology from Marc Hughes Sun, 30 Jan 2011 18:36:22 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Maxim Porges http://www.rogue-development.com/blog2/2009/07/profiling-experience/comment-page-1/#comment-1016 Maxim Porges Wed, 29 Jul 2009 03:22:45 +0000 http://www.rogue-development.com/blog2/?p=513#comment-1016 I had an almost identical experience with a spinner-style progress component I found online. The assumption was that Flash would stop trying to render an item no longer on screen; that assumption ended up being very wrong. - max I had an almost identical experience with a spinner-style progress component I found online. The assumption was that Flash would stop trying to render an item no longer on screen; that assumption ended up being very wrong.

- max

]]> By: Mark Doberenz http://www.rogue-development.com/blog2/2009/07/profiling-experience/comment-page-1/#comment-963 Mark Doberenz Tue, 14 Jul 2009 20:00:15 +0000 http://www.rogue-development.com/blog2/?p=513#comment-963 I came upon the indeterminate progress bar issue a different way one time. I happened to be running an app and just to play around, turned on "Show Redraw Regions" and in the middle of the app there's this moving red rectangle. I realized it was my progress bar still redrawing itself. This was back in the Flex 2 days without the Profiler. :) I came upon the indeterminate progress bar issue a different way one time. I happened to be running an app and just to play around, turned on “Show Redraw Regions” and in the middle of the app there’s this moving red rectangle. I realized it was my progress bar still redrawing itself. This was back in the Flex 2 days without the Profiler. :)

]]> By: Marc http://www.rogue-development.com/blog2/2009/07/profiling-experience/comment-page-1/#comment-959 Marc Mon, 13 Jul 2009 18:00:28 +0000 http://www.rogue-development.com/blog2/?p=513#comment-959 Afraid so. Now it wasn't just the fact that 2 timers were going, it was the fact that the two progress bars were constantly animating. I'm assuming it's because of a deeply nested display list and either the flex layout code was constantly running, or the Flash rendering code was going crazy. After manually setting the visibility on those two progress bars everything was fine (and that being the only change). But once solving the problem I didn't investigate the why any further why it was happening. Afraid so.

Now it wasn’t just the fact that 2 timers were going, it was the fact that the two progress bars were constantly animating. I’m assuming it’s because of a deeply nested display list and either the flex layout code was constantly running, or the Flash rendering code was going crazy. After manually setting the visibility on those two progress bars everything was fine (and that being the only change). But once solving the problem I didn’t investigate the why any further why it was happening.

]]> By: felix http://www.rogue-development.com/blog2/2009/07/profiling-experience/comment-page-1/#comment-958 felix Mon, 13 Jul 2009 17:50:46 +0000 http://www.rogue-development.com/blog2/?p=513#comment-958 So 2 spinning timers knocked the cpu from 4% to 216%? surely not? So 2 spinning timers knocked the cpu from 4% to 216%? surely not?

]]>