[svn:osmf:] 11199: Sample clean up and bug fixing.

Revision: 11199
Author:   [email protected]
Date:     2009-10-27 13:56:22 -0700 (Tue, 27 Oct 2009)
Log Message:
Sample clean up and bug fixing.
Modified Paths:
    osmf/trunk/apps/samples/framework/CuePointSample/src/CuePointSample.mxml

At least in the version I was using it was, quite literally. Horrible.
Invalid, unsemantic, not cross-browser, and subject to quirks mode rendering.
That isn't necessarily a comment on the developers of the system as a whole. Just those who created the HTML and JS. And, who knows, perhaps was improved in later versions.
From my experience with other CMS systems, though, there is sufficient abstraction to fix much of this, if the templates for the HTML and JS can be located.
I'm hoping that SAP is the same, that there are places to look for the HTML that creates major UI components.
This seems useful anyway, since customising is more effective if the templates themselves can be changed at that level.
This also carries over to the IDE - where the sample apps that could be created also generated invalid or unsemantic HTML and JavaScript in my tests. (setting aside my killing my server in my first test of field submission just by pasting a few kilobytes of text in the field )
Anyway, certainly front-end is not a comment on system as a whole, but lightweight and valid HTML makes styling much easier, so if I could figure out how to fix that, it'd be lovely.
P.S. - this forum itself uses "color: windowText" for text areas without setting background-color: window.
Kind of sloppy, easily fixed on my side (where I use a dark UI theme) by overriding the site style.

Similar Messages

Vibe Z2 Pro (K920) stock ROM improvements and bug fixes

Phone info: Lenovo K920, Android 4.4.2, K920_ROW_S133_141010 I've already posted this message, but, probably, to the wrong forum section. Hello to all I hope that if it is the official Lenovo forum, the respectable developers already read it from time to time & some thoughts about Vibe Z2 Pro stock software improvements and bug fixes will be useful for them. Interface1) "Double tap to wake" feature is, probably, the most requested one.2) There is very long response period between the long pressing "Menu" button and the showing of the earlier executed applications list. Even then Settings > Accessebility > [Touch & hold delay] is set to "Shot". I'd better to cut this delay twice.3) "Clear all" function in the the earlier executed applications list sometimes seems doesn't work properly: I press the button, clearance process indicator is rotating, but the list isn't empty.4) The system font is lengthened by vertical axis & it looks worse then the corresponding font on nexus devices. Lockscreen1) Lockscreen crashes when Poweramp with the default settings is playing a song (Poweramp > Settings > Lock Screen > Enable Android Lock Screen = true). Probably, this is a Poweramp bug, not K920 ROM (The Rocket Player with the same functionality works well), but who knows...2) There will be a good idea to realize option "Disable change lockscreen picture by swype" somewhere in Settings, because such an involuntary change take place regularly. Stock Camera app1) As far as I know, Samsung Galaxy S5 has an HDR option for recording a video. It would be cool to implement this feature (moreover, if I'm not mistaken, K920 has the same camera hardware).2) In professional mode I can drag "Photo camera" icon left and this will result in appearance the five curves of settings (like a Solar system) - just as in Nokia Camera for Nokia Lumia phones. Bute there are two shortages in this (generally very good) idea.2a) In Nokia Camera the "Photo camera" icon is moving left just under the finger while being dragged, while in K920 Camera app "Photo camera" icon is moving only after dragging is finished & the finger is moved away from the screen. Such a behaviour looks a little bit unnatural.2b) In Nokia Camera I can show the single curve for the tuning of a single parameter by pressing a corresponding button on the center of the top side of the screen. The K920 Camera app doesn't have such an ability at all (or I failed to find it).This video illustrates the problem.3) It would be very good to add the next options: disable shutter sound, change photo resolution (5M, 8M, 16M) and aspect ratio (16:9, 4:3).4) The Zoom function in video recording mode works like simple pixelization, not zoom. Neither Lumia 1520, nor HTC One X (my other phones) doesn't zoom in video mode like K920. The two videos - about Lumia 1520 zoom & K920 zoom illustrate the problem. This is the more so strange, that in photo mode K920 zoom is apparently better than the Lumia 1520 one. Sound1) It would be great to realize step-by-step volume increasing for incoming calls. Thank you.

Hi monocats,
Yes, I have expirienced quite the same camera issues as you, but only 5 or 6 times of more than 200 photos, so made little for this issue.
Link to image
Link to image
I'm a newbie in photography, but noticed, that slightest chage in camera position result in disappearing such artefacts as on the photos above. So it can be result of a light sources mutual position and some camera hardware aspects.
Moderator note: Large image/s converted to link/s About Posting Pictures In The Forums

May Release: New partner support, Infrastructure updates, Site templates and bug fixes

Link: http://www.businesscatalyst.com/_blog/BC_Blog/post/May-release-New-partner-support-Infrast ructure-updates-Site-templates-and_bug-fixes/
We are announcing a new Business Catalyst release, scheduled to go live on Thursday, May 3rd. With this release, we are continuing our investments in system performance and stability by increasing our web servers capacity, enabling HTTP acceleration to provide faster site loading times, and improving the site creation speed by using pre-generated sites.
On the product side, we have completely revamped our partner support workflow taking advantage of the Adobe support infrastructure and tools, enhanced the site templates workflow for partners, and included lots of bug fixes and improvements. Read through the following sections to get detailed information about this release:
Partner support
Infrastructure updates
Features and enhancements
Issues fixed by this release
What's next
You can jump to the corresponding section by clicking the above links.
Partner support
Updated Help & Support partner experience
Following Adobe ID support, we have upgraded BC support tools (cases, chat, documentation) with standard Adobe tools. As a partner, you can now benefit from the same support tools as the rest of Adobe Creative Suite, and can track your support cases with Adobe BC, Dreamweaver, Muse or Photoshop in a single place.
Partners with more than 100 paid sites will get 2nd level chat support, which includes a higher priority, by default. If you have more than 100 paid sites, but spread across different Partner Portals, please ask support to enable 2nd level chat for you.
Support experience for your Small Business owner clients can now be owned by partners (see below).
Custom Help & Support URL for your clients
As a partner, you are probably already offering various additional services to your clients besides building & maintaining their BC site. Support, tailored specifically to your client needs, is usually one of these value-added services. We are now enabling you to take your Support service to the next level. In Partner Portal Settings, you have the option to set a custom URL for what will open when your client clicks on Help & Support inside Admin Console:
If you have multiple partner accounts, for different verticals, you can specify a Support URL for each of these.
The default Support experience provided by BC for your clients will be updated in a few releases to be similar to the partner support experience. This includes BC-branded support cases and documentation. If you'd like to keep a white-label experience for your customers, please set your own Help & Support URL in Partner Portal.
For more details please read the Improved support workflow and new forums announcement on our blog.
Infrastructure updates
Between our April release and the following infrastructure updates have been enabled
Limited trial sites for free partners – starting with our May release, the number of trial sites a Free Partner can have will be limited to 100. Once the limit is reached, Free Partners that need to create a new trial site have the options to upgrade to a higher partner plan, upgrade some of the trial sites to paid or delete unused/expired trials.
Automatic trial expiry extension - with this release, trial site expiry date will be automatically extended with 30 days every time an admin user logs in the system through the admin interface or through FTP.
Installed additional hardware - we have installed additional web servers on all our data centers, that translate into an increase of the existing capacity with over 70%.
Updated DNS infrastructure - we have improved the DNS resolution for email delivery so that we can increase the rate at which we're sending the system operational emails
HTTP acceleration – all sites static assets are served from a new cache engine (images, CSS and JavaScript files, together with improved headers that should allow the browser to cache them better for a browsing session). This update has been turned on along with our April release, and has made all the BC sites load faster on first and on subsequent loads.
Accelerated site/partner creation – we've changed the way new sites are created for faster speed, pre-creating them and reusing pre-created sites when needed, and have also improved the creation process for new partners, minimizing the impact of new CCM customers on the existing datacenters.
Adobe ID for partners - in order to support an integrating experience between the various Adobe tools a partner may use (Dreamweaver, Muse, Support forums) we have added Adobe ID support for Business Catalyst partner accounts. Starting April 19, partners are asked to merge their current Business Catalyst account with their Adobe ID accounts. For more details about the transition process and FAQ please read the Introducing Adobe ID blog post.
Updated Terms of Use - Along with several other changes in our processes in the past few months, we also revamped our Terms of Use and the signature process by requesting every admin user to sign a TOU. We have completed the rollout for partners, and we might be pushing an updated partner Terms of Use version within the following weeks. For more details and questions about this change, read the New Terms of Use for Business Catalyst blog post.
Features and enhancements
Site templates
To support the increasing number of partners building, sharing or reusing templates to create new sites, we're extending our site templates support from our partner portal with a new template type and improved management support. The update is going to enable partners to mark sites as templates and choose between making them available in Online Business Builder and keeping them private in their partner portal. A template site will not expire and has the same limits as any other trial site.
Based on your partner level, you can create private or public templates using the Site Details screen or the Tools>My Site Template section from your Partner Portal. Standard partners can only create private templates, while Free Partners can only view site templates that have been transferred to their accounts by other partners.
The number of templates a partner will have will be limited and will vary based on partner level: free partners can store up to 5 templates in their partner portal, standard partners have up to 100 site templates while Premium Partners might have up to 200 templates. Paid sites marked as templates are not counted against these limits.
Business Catalyst Partner fixes
While we are really focused on making the Business Catalyst integration into Creative Cloud a smashing success, we are slowly resuming our efforts to deliver fixes that have been requested by our partners. This release includes the following partner fixes:
Improved product custom fields - we have increased the maximum number of characters for product custom fields to 1024 (previous limit was 256); this gives partners and customers additional space to use when working with products
Improved Secure Zone subscribers list - we have added the customer email address in the Secure Zone Subscribers list to enable partners better filter and manage customers
Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
Social plugins integration updates
Starting with our May release, we are updating the social plugins support to require users to get the plugin code from the third party provider and saving into his Business Catalyst website. The module tags and configuration will remain unchanged, but will render an empty tag until the partner or site owner will update the module template to include the corresponding module code snippet from the third party platform provider.
For more information about how you can enable the Social Plugins on a Business Catalyst websites, read the Social Media: Integrating Facebook and Twitter knowledge base article.
Other changes
Updated weekly emails - Starting with our May release, the information in the site weekly emails has been filtered based on the site's plan. For example, webBasics site reports will no longer include the sales report.
Localization - we improved and increased the coverage of the admin interface translations into German, French and Japanese
Site Settings -> Ignored IP addresses has been relocated under Reports -> Visitors -> More.
BC-Dreamweaver integration performance improvements
Development Dashboard has been removed, as it didn't provide a clear useful, ongoing benefit. The information present in the development dashboard has been integrated into our new Help & Support section.
Payment gateway settings - for more privacy and data protection, we have updated the Payment Gateway configuration screens to obfuscate the sensitive login information. Fields that have been obfuscated are now requiring confirmation.
Report abuse badge on trial sites - for compliance reasons, a "Report Abuse" link has been added to the front-end of all trial sites of free partners that don't have any paid sites. When they click the Report Abuse link, site visitors are redirected to a form submission page on businesscatalyst.com site.
Issues fixed by May release
Issues 3051303, 3168786 - Workflow notifications - Fixed a problem preventing workflow notifications emails from being sent.(see get satisfaction forum discussion)
Issue 3164074 - Fixed a bug causing the lightbox gallery created from Muse to be displayed behind page elements
Issue 3162810 - Fixed a bug in rendering engine to prevent content placed between body and head tags being incorrectly moved inside the body tag
Issue 3166610 - Fixed a broken link to Partner Portal in Internet Explorer
Issue 3175003 - Fixed an issue that caused an incorrect price display for the Year One-Off Setup Fee when upgrading a site from Admin using CB
Issue 2567278 - Fixed a bug causing site replication to ignore product attributes
Issue 2947989 - CRM passwords are now case sensitive
Issue 2723731 - Removed CSS files from the head section of the Layouts files, when downloaded and opened in Dreamweaver, via the BC extension
Business Catalyst new admin interface updates
Added "Save and Add New" button in Web App Item Add & Edit screens (see get satisfaction forum discussion)
Updated Quick Actions menus to add more actions (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to display deleted items (see get satisfaction forum discussion)
Fixed a display issue on File Manager making top buttons unreachable (see get satisfaction forum discussion)
Fixed the scrollbars in Email Marketing>Campaign>Stats>Bounced Emails reports (see get satisfaction forum discussion)
Fixed an issue causing Recent items menu to brake after selecting the current page from the Recent Items menu (see get satisfaction forum discussion)
Replaced the Success notification displayed when selecting Users or Permissions tabs from User Roles with an Warning
Change the action label displayed in User Roles list from View to Edit to match the list pattern from Admin Users
Fixed a missing file JavaScript error occurring when trying to open image manager from product details-> Attributes -> options
Moved System Emails section from Site Setting to Site Manager (see get satisfaction forum discussion)
Updated Domain Management interfaces to close the modal window and refresh the domain list after successfully adding a domain
Fixed an issue preventing the Hyperlink Manager to function properly (see get satisfaction forum discussion)
Updated the confirmation message received after copying a page to match the new workflow and button names
Fixed an issue causing the current screen or section to not be highlighted in the menu
Updated styling on the new dashboard, user management and email accounts interfaces
Updated dashboard reports filters and chart display; made the chart and the filter use the site time zone
Fixed an issue preventing users from inviting new admin users or create new email accounts on Internet Explorer 8
Fixed an issue preventing users from deleting Email Accounts or Admin Users in Internet Explorer 8
Fixed some issues preventing password recovery email from being sent
Removed the alert message displayed when the user or email account limit has been reached
Added localization for the simplified dashboard
Fixed display issues for site limits, domains and user list in the simplified dashboard
Added Custom reports for webBasics plan
Fixed a bug generating a "500:Collection error" on the simplified dashboard when user did not had View users permission
Added TOU checkbox in the email account setup screen
Updated Site Preview link in the dashboard to load the default domain
Fixed an issue in the new File Manager forcing a user to press Undo twice in order to see the change take effect if the code that was previously formatted contained any <"tag" with more than 2 lines
Fixed an issue causing the File Manager editor toolbar to incorrectly render if page URL path is longer than certain value; starting with this release, the site URL is trimmed
Fixed an issue causing the invite users to be displayed as [object Object] in dashboard and admin user list
Fixed a bug in the new admin causing the interface to become unresponsive when using the browser Back button
Fixed an issue in the new File Manager causing "Save Draft" button to publish the default page template instead of creating a draft version
Fixed a broken invite link issue in the Email Account invite email
Updated loading indicators in File Manager and Email Accounts screens
What's next
The first item on the what's next list might not be news for many of you, but it's definitely one of the most important milestones this year. The Creative Cloud launch is just around the corner, and Business Catalyst is playing an important role in that, as the publishing platform for Adobe® Muse and Dreamweaver. This launch will capture all our attention within the next weeks as we want it to be our best ever.
We'll start our next development cycle on May 15th, while the next Business Catalyst release is going to be pushed live in mid June. That being said, the following items are already on our launch plan for the next release and a few more will join the list. Please expect an update on our 2012 plans around mid May.
HTTP throttling – all page load and API calls to BC will be protected against attacks, this might trigger problems for API heavy sites. We are looking into enabling this update along with our June release, and will help make sure that a reasonable number of requests will be accepted from the same computer per minute.
Automatic site deletion - Starting with the June release, we are going to start automatically delete expired trial sites and canceled sites. Customers will be notified twice before we are going to proceed with deleting the sites.
Thank you,
Cristinel Anastasoaie
Adobe Business Catalyst Product Manager

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

How long for updates and bug fixes usually?

I'm new to Logic and even new to Macs. I'm just wondering how long does it usually take for Apple to release bug fixes and updates to Logic?
Also, how long did Apple take to get around to providing worthwhile updates to Logic 7? Were there substantial updates changed work flow, functionality, etc?
Basically I'm wondering how long until Logic 8 will be more stable and complete?

Logic 7 was never updated so as to provide any significant changes in workflow over its initial release. But apparently L7 so intrinsically broken that they abandoned any effort to fix it. Instead, they developed Logic 8.
L8 has some very obvious bugs, yes. They need to be fixed yesterday. But as usual, Apple is dragging its feet in this regard.
To your question, how long.... well, L7 updates occurred about every 4 months. There's no telling if they'll be on a more conscientious schedule for releasing L8 updates. They only offer end-users one choice: wait and see what happens.

[svn:bz-4.0.0_fixes] 20451: backporting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError .

Revision: 20451
Revision: 20451
Author:   [email protected]
Date:     2011-02-24 08:33:31 -0800 (Thu, 24 Feb 2011)
Log Message:
backporting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation. Checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-570
    http://bugs.adobe.com/jira/browse/BLZ-620
Modified Paths:
    blazeds/branches/4.0.0_fixes/modules/common/src/flex/messaging/errors.properties
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/endpoints/AbstractEndpoint.j ava
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/SerializationContext.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf0Input.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/Amf3Input.java
    blazeds/branches/4.0.0_fixes/modules/core/src/flex/messaging/io/amf/AmfIO.java

Dear Pallavi,
Very useful post!
I am looking for similar accelerators for
Software Inventory Accelerator
Hardware Inventory Accelerator
Interfaces Inventory
Customization Assessment Accelerator
Sizing Tool
Which helps us to come up with the relevant Bill of Matetials for every area mentioned above, and the ones which I dont know...
Request help on such accelerators... Any clues?
Any reply, help is highly appreciated.
Regards
Manish Madhav

[svn:bz-3.x] 20443: back porting bug fix BLZ-570/ BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError .

Revision: 20443
Revision: 20443
Author:   [email protected]
Date:     2011-02-23 21:19:22 -0800 (Wed, 23 Feb 2011)
Log Message:
back porting bug fix BLZ-570/BLZ-620 Double linked list with lot of objects result in BlazeDS Error deserializing error : StackOverflowError We put hard limit to the max object nest level to prevent StackOverFlowError. the default max object nest level is 1024 and it can be configured in the endpoint/serialziation section in service-config.xml. This needs documentation. Checkintests pass
Ticket Links:
    http://bugs.adobe.com/jira/browse/BLZ-570
    http://bugs.adobe.com/jira/browse/BLZ-620
Modified Paths:
    blazeds/branches/3.x/modules/common/src/java/flex/messaging/errors.properties
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/endpoints/AbstractEndpoint.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/SerializationContext.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf0Input.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/Amf3Input.java
    blazeds/branches/3.x/modules/core/src/java/flex/messaging/io/amf/AmfIO.java

[svn:fx-3.x] 5687: Flex Framework Bug Fix

Revision: 5687
Author: [email protected]
Date: 2009-03-27 16:27:38 -0700 (Fri, 27 Mar 2009)
Log Message:
Flex Framework Bug Fix
SDK-14684 Un-hardcode the 10 digit limit in PhoneNumberValidator
Added a minDigits property to PhoneNumberValidator. Added new resource string to Validator.properties.
SDK-16679 NumberValidator.domain should use constants instead of strings
Added new class NumberValidatorDomainType. Updated the ASDoc and one of the equality checks in NumberValidator.
QE Notes: add tests for the new minDigits property
Doc Notes: add documentation for the new minDigits property and NumberValidatorDomainType class
Bugs: SDK-14684, SDK-16679
Reviewer: Hans
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-14684
http://bugs.adobe.com/jira/browse/SDK-16679
http://bugs.adobe.com/jira/browse/SDK-14684
http://bugs.adobe.com/jira/browse/SDK-16679
Modified Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/bundles/en_US/src/validators.properti es
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/validators/NumberValidator.as
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/validators/PhoneNumberValidato r.as
Added Paths:
flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/validators/NumberValidatorDoma inType.as

[svn:fx-trunk] 5152: First pass of bug fixes for the Spark skins for Halo components.

Revision: 5152
Author: [email protected]
Date: 2009-03-03 13:18:45 -0800 (Tue, 03 Mar 2009)
Log Message:
First pass of bug fixes for the Spark skins for Halo components.
Bugs:
SDK-19963 - themeColor should not affect rollOverColor or selectionColor in flex 4
SDK-19654 - Spark skin for the Halo ComboBox dropdown needs a drop shadow
SDK-19637 - Halo HScrollBar/VScrollBar controls dont render correctly when specifying includeIn states
SDK-19634 - Halo ProgressBar default size is very different when using Halo vs Gumbo theme
SDK-19626 - Flicker when toggling enabled property on Halo TabBar control with Gumbo skin
SDK-19556 - selected Halo CheckBox and RadioButton icons briefly flicker when you roll over them
SDK-19658 - Halo ComboBox with Gumbo skin has an odd flicker
Doc/QA Notes: The fix for SDK-19963 includes a compatibility-version check. When compatibility-version < 4, setting themeColor implicitly sets rollOverColor and selectionColor, if they have not been set. When compatibility-version >= 4, you must explicitly set rollOverColor and selectionColor, even when using the Halo theme.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19963
http://bugs.adobe.com/jira/browse/SDK-19654
http://bugs.adobe.com/jira/browse/SDK-19637
http://bugs.adobe.com/jira/browse/SDK-19634
http://bugs.adobe.com/jira/browse/SDK-19626
http://bugs.adobe.com/jira/browse/SDK-19556
http://bugs.adobe.com/jira/browse/SDK-19658
http://bugs.adobe.com/jira/browse/SDK-19963
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/components/FxApplication.as
flex/sdk/trunk/frameworks/projects/framework/defaults.css
flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/Button.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/ComboBase.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/core/Application.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/graphics/RectangularDropShadow.as
flex/sdk/trunk/frameworks/projects/sparkskins/src/mx/skins/spark/BorderSkin.mxml
flex/sdk/trunk/frameworks/projects/sparkskins/src/mx/skins/spark/ProgressBarTrackSkin.mxm l

[svn:fx-3.x] 8970: Slider Tick bug fix

Revision: 8970
Author:   [email protected]
Date:     2009-07-31 14:03:33 -0700 (Fri, 31 Jul 2009)
Log Message:
Slider Tick bug fix
http://bugs.adobe.com/jira/browse/SDK-15529 - Ticks arent centered properly in HSlider control
Patch submission from Aaron Whiting:
"Tick marks drawing code included an x-offset value to adjust the tick mark location by half of the tick line thickness. X-offset value was removed from drawing code and ticks are now centered."
The ticks no longer need to be offset since we switched from a Sprite symbol to using the drawing API.
QE notes: Add test case
Doc notes: None
Bugs: SDK-15529
Reviewer: Jason
Tests run: Slider
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-15529
    http://bugs.adobe.com/jira/browse/SDK-15529
Modified Paths:
    flex/sdk/branches/3.x/frameworks/projects/framework/src/mx/controls/sliderClasses/Slider. as

[svn] 3543: Asc front end performance improvements & bug fixes

Revision: 3543
Author: [email protected]
Date: 2008-10-09 11:54:47 -0700 (Thu, 09 Oct 2008)
Log Message:
Asc front end performance improvements & bug fixes
This set of Asc parser/scanner/inputbuffer updates contains changes that simplify the parser?\226?\128?\153s lookahead/match fsm.
A method, ?\226?\128?\152shift()?\226?\128?\153 has been added that replaces match, when the token to be consumed is known.
Also, a simplified version of lookahead has been added that returns the lookahead token, which allows use of switch code when the lookahead set is large.
Simple inputbuffer changes (switching to a String, so that we can use substring instead of valueof) seem to result in about a 2% performance improvement.
Fixes for:
ASC-3519
ASC-2292
ASC-3545
All being overlapping bugs related to regexp recognition in slightly differing contexts.
QA: Yes
Doc:
Tests: checkintests, Performance tests, tamarin, asc-tests, mx-unit
Ticket Links:
http://bugs.adobe.com/jira/browse/ASC-3519
http://bugs.adobe.com/jira/browse/ASC-2292
http://bugs.adobe.com/jira/browse/ASC-3545
Ticket Links:
http://bugs.adobe.com/jira/browse/ASC-3519
http://bugs.adobe.com/jira/browse/ASC-2292
http://bugs.adobe.com/jira/browse/ASC-3545
http://bugs.adobe.com/jira/browse/ASC-3519
http://bugs.adobe.com/jira/browse/ASC-2292
http://bugs.adobe.com/jira/browse/ASC-3545
Modified Paths:
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/InputBuffer.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/Parser.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/Scanner.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/States.java

In reference to this change in the Custom Reports... Better experience when exporting data - to prevent customer confusion when exporting data from Mac computers, we have removed the export to excel option and exporting in CSV format by default.
What is the customer confusion we are trying to stop here? I've got even more confused customers at the moment because all of a sudden they can't find the export to excel option but know it exists if they log in on a PC?
Mark

[svn:fx-trunk] 11274: ModuleLoader enhancement and StyleProtoChain fix

Revision: 11274
Author:   [email protected]
Date:     2009-10-29 12:22:48 -0700 (Thu, 29 Oct 2009)
Log Message:
ModuleLoader enhancement and StyleProtoChain fix
QE notes: None.
Doc notes: None.
Bugs: SDK-23855, SDK-23733
Reviewer: Alex
Tests run: checkintests, Managers/StyleManager
Is noteworthy for integration: No.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23855
    http://bugs.adobe.com/jira/browse/SDK-23733
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/modules/ModuleLoader.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/styles/StyleProtoChain.as

[svn:fx-trunk] 5170: Round 2 of bug fixes for the Spark skins for Halo components.

Revision: 5170
Author: [email protected]
Date: 2009-03-04 17:50:32 -0800 (Wed, 04 Mar 2009)
Log Message:
Round 2 of bug fixes for the Spark skins for Halo components. Thanks to Alex for help with the data grid issues.
Bugs fixed:
SDK-19655 - Setting rowCount property on DataGrid causes extra blank row to be displayed
SDK-19652 - Items in a DataGrid do not line up after scrolling.
SDK-19605 - disabled Halo ColorPicker with Gumbo skin draws too dark
SDK-19596 - When you have a single button on an Alert, the left edge looks flatter than the right
SDK-19585 - Menus compiled with the halo theme in Flex 4 have a different backgroundColor than in Flex 3
SDK-19665 - Halo List with Gumbo skin doesnt draw the alternating item color all the way to the right edge of the control if VScrollBar is present
SDK-19651 - odd header rendering issue on Halo DataGrid with Gumbo skin
QA Notes: The alert layout code was positioning the buttons/text on sub-pixel boundaries if the width or height of the alert was an odd number of pixels. We always snap to pixel boundaries now, but this may cause bitmap compare issues with Alert.
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-19655
http://bugs.adobe.com/jira/browse/SDK-19652
http://bugs.adobe.com/jira/browse/SDK-19605
http://bugs.adobe.com/jira/browse/SDK-19596
http://bugs.adobe.com/jira/browse/SDK-19585
http://bugs.adobe.com/jira/browse/SDK-19665
http://bugs.adobe.com/jira/browse/SDK-19651
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/DataGrid.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/alertClasses/AlertForm.as
flex/sdk/trunk/frameworks/projects/framework/src/mx/core/ScrollControlBase.as
flex/sdk/trunk/frameworks/projects/halo/defaults.css
flex/sdk/trunk/frameworks/projects/sparkskins/src/mx/skins/spark/ColorPickerSkin.mxml

[svn:fx-trunk] 10182: This is a bug fix for DropDownList.

Revision: 10182
Author:   [email protected]
Date:     2009-09-11 16:15:57 -0700 (Fri, 11 Sep 2009)
Log Message:
This is a bug fix for DropDownList. When Label changed from a GraphicElement to a UIC it started blocking the mouse events from the anchorButton inside of a DropDownList. To fix this, I've just disabled the mouse of the labelDisplay in the DropDownListSkin
QE notes: -
Doc notes: -
Bugs: SDK-23054
Reviewer: Jason
Tests run: checkintests, DropDownList
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23054
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/skins/spark/DropDownListSkin.mxml
    flex/sdk/trunk/frameworks/projects/wireframe/src/spark/skins/wireframe/DropDownListSkin.m xml

[svn:fx-trunk] 14199: ToolTip border skin bug fix

Revision: 14199
Revision: 14199
Author:   [email protected]
Date:     2010-02-16 13:59:53 -0800 (Tue, 16 Feb 2010)
Log Message:
ToolTip border skin bug fix
http://bugs.adobe.com/jira/browse/SDK-24282 - SliderDataTip instantiates it?\226?\128?\153s border class before it?\226?\128?\153s style can be set by Slider
Modified a patch submission to follow the pattern in TextInput. When the borderSkin style changes, the border was not recreated with the new border class.
Thanks go to David Spanton for the original submission
QE notes: yes, need tests for this use case
Doc notes: n/a
Bugs: SDK-24282
Reviewer: Kevin
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24282
    http://bugs.adobe.com/jira/browse/SDK-24282
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/controls/ToolTip.as

[svn:fx-trunk] 12816: VideoPlayer full screen bug fix

Revision: 12816
Revision: 12816
Author:   [email protected]
Date:     2009-12-10 16:19:26 -0800 (Thu, 10 Dec 2009)
Log Message:
VideoPlayer full screen bug fix
SDK-24308 - Full-screen VideoPlayer running as AIR application on dual monitor setup has white background
If we are running on the AIR Player, then use the Screen bounds API instead.
QE notes: None
Doc notes: None
Bugs: SDK-24308
Reviewer: Ryan
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24308
    http://bugs.adobe.com/jira/browse/SDK-24308
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/VideoPlayer.as

[svn:osmf:] 11199: Sample clean up and bug fixing.

Similar Messages

Maybe you are looking for