[svn:fx-4.x] 15104: Fix for invalid links for @see of inherited styles

Revision: 15104
Revision: 15104
Author:   [email protected]
Date:     2010-03-29 07:36:44 -0700 (Mon, 29 Mar 2010)
Log Message:
Fix for invalid links for @see of inherited styles
QE notes: None.
Doc notes: None.
Bugs: SDK-26002
Reviewed By: Darrell
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-26002
Modified Paths:
    flex/sdk/branches/4.x/asdoc/templates/asdoc-util.xslt
    flex/sdk/branches/4.x/asdoc/templates/class-files.xslt

Similar Messages

[svn:fx-4.x] 15377: Fix for invalid links for inherited skin part depending on package depth

Revision: 15377
Revision: 15377
Author:   [email protected]
Date:     2010-04-13 12:53:59 -0700 (Tue, 13 Apr 2010)
Log Message:
Fix for invalid links for inherited skin part depending on package depth
QE notes: None
Doc notes: None
Bugs: SDK-26208
Reviewer: Darrell
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-26208
Modified Paths:
    flex/sdk/branches/4.x/asdoc/templates/class-files.xslt

Stope
Mailing me ***
Sent from my I phone

[svn] 2703: Fixes for bad links in seeTag and inheritance link.

Revision: 2703
Author: [email protected]
Date: 2008-08-01 08:45:08 -0700 (Fri, 01 Aug 2008)
Log Message:
Fixes for bad links in seeTag and inheritance link.
@seeTag was causing duplicate entries for package name in the array - which was causing a bad link..
Bugs: SDK-9440, SDK-14265, SDK-12745
QA: Yes
Reviewed by: Paul
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-9440
http://bugs.adobe.com/jira/browse/SDK-14265
http://bugs.adobe.com/jira/browse/SDK-12745
Modified Paths:
flex/sdk/trunk/modules/compiler/asdoc/asDocHelper.as

Revision: 2703
Author: [email protected]
Date: 2008-08-01 08:45:08 -0700 (Fri, 01 Aug 2008)
Log Message:
Fixes for bad links in seeTag and inheritance link.
@seeTag was causing duplicate entries for package name in the array - which was causing a bad link..
Bugs: SDK-9440, SDK-14265, SDK-12745
QA: Yes
Reviewed by: Paul
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-9440
http://bugs.adobe.com/jira/browse/SDK-14265
http://bugs.adobe.com/jira/browse/SDK-12745
Modified Paths:
flex/sdk/trunk/modules/compiler/asdoc/asDocHelper.as

[svn] 4624: Flex SDK Bug Fix - Add snapshot support for 3D transformed GraphicElements

Revision: 4624
Author: [email protected]
Date: 2009-01-22 13:15:17 -0800 (Thu, 22 Jan 2009)
Log Message:
Flex SDK Bug Fix - Add snapshot support for 3D transformed GraphicElements
SDK-17362 - GraphicElement.getBitmapData doesn't handle 3D transforms
Added in support to take a bitmap snapshot of a 3D transformed GraphicElement.
Added a flag to getBitmapData to return a bitmap of the target either in the local or global coordinate space.
Also, fixed a bug in the bitmap snapshot logic for a 2D GraphicElement that was sharing its displayObject.
Note that the 3D snapshot isn't accurate if you have set maintainProjectionCenter on an ancestor. There are also limitations when rotation is applied. In addition, getting a local 3D snapshot isn't too accurate once you start scaling ancestors.
QE Notes: Add mustella tests for getBitmapData
Doc Notes: Document that getBitmapData now supports 3D transforms
Bugs: SDK-17362
Reviewer: Evtim
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17362
http://bugs.adobe.com/jira/browse/SDK-17362
Modified Paths:
flex/sdk/trunk/frameworks/projects/flex4/src/mx/graphics/graphicsClasses/GraphicElement.a s

FYI - This regression has been filed here: http://bugs.adobe.com/jira/browse/SDK-31989

Invalid link for Oracle9i JHeadstart Developer's Guide

The link to the Developer's Guide at http://otn.oracle.com/consulting/9iServices/JHeadstart2.html
is invalid.

You are right. We are in the process of uploading this file. I will annonce the new page on this forum when the developer's
guide is uploaded.
By the way the zip file that includes all the viewlets is not uploaded either. We will fix that as well.
Regards,
Ton van Kooten
JHeadstart Team

Invalid Link for 9.2.0.1 EE/SE/S/P/Client 32-bit Windows Server 2003

Hello,
The OTN download for Oracle 9i Release 2 (9.2.0.1) 32-bit for Windows Server 2003 is incorrect. This link brings you to the 9.2.0.3 PATCHSET download, and NOT the base release software.
Here is the contents of the link when followed.
"Oracle9i Database Release 2 Enterprise/Standard/Personal/Client Edition for Windows Server 2003 (32-bit)
     Download the Complete Files
          OUI220180.zip (47,405,300 bytes)
          9203WIN2K3.zip (181,643,734 bytes)
     Documentation
          Oracle9i Database Release 2 for Windows Server 2003 (32-bit) Release Notes (PDF/HTML)
     Directions
          1. Before downloading, please review the product certification information for this product.
          2. Consult the release notes for download and installation instructions."
I need to download the 9.2.0.1 32-bit Client. The eDelivery site only has the 9.2.0.1 64-bit release.
OTN Admins - please help!
Regards,
Steve

Are there any moderators checking this forum?
I called Oracle support and requested a shipment for Oracle9i for Windows Server 2003. I made sure that whatever media pack they were sending me what explicitly for 2003. It was for both 2000 & 2003 however the client/database CDs for 2003 are only for 64-bit.
If 9i 32-bit is the only certified version for AMD processors why isn't it in included the media pack? There's a nice sticker on the back that notifies you that the 32-bit software requires an additional upgrade that is available from OTN.
So, If OTN's link is bad and no one is from OTN is moderating this site then how on Earth is anyone able to aquire this software version? Oracle's Metalink offers no solution outside of posting to this forum.
-Steve

Invalid rights for existing type: workitem

Hi,
Yesterday I installed the SP1 for idm 6.0.
Since then i'm getting a WavesetException printout for "invalid rights for existing type: workitem" when I call: Server.getServer().
Has anyone expierenced the same problem or perhaps know how to avoid the exception?
regards
Kevin

I'm getting the exception everywhere now.
Did I do something wrong in the installation perhaps?
When I start the BPE I get the exception, also for the lh console.

Link for IS-OIL in 7.2 version of SAP

Hi experts,
I am searching for the link for IS-OIL in 7.2 version of SAP ? Can anybody tell me to find the link ?
Regards,
Shakti

Hello Clinker,
Still SAPGUI 64 bit version not available. You can use SAPGUI 32 bit version in 64bit OS. It will work.
Best Regards, Ashwini

[svn] 2218: Fix for invalid seek.

Revision: 2218
Author: [email protected]
Date: 2008-06-24 13:49:11 -0700 (Tue, 24 Jun 2008)
Log Message:
Fix for invalid seek. Player would become non-responsive indefinitely when an
invalid seek occured.
Bugs: SDK-14784
QA: Yes
Reviewer: Deepa
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-14784
Modified Paths:
flex/sdk/branches/3.0.x/frameworks/projects/framework/src/mx/controls/videoClasses/VideoP layer.as

Please, help me! I don't want this post to be forgotten.

Script to fix invalid characters for SharePoint synced share

I'm hoping for some help implementing a script that will rename files with characters that are invalid for SharePoint, in a synced file share that is accessed by everyone at an office.
Some background: I'm working for a small nonprofit that has a SBS 2012 server and a local domain with about 30 users. I'm the sole volunteer IT person here. We have a network file share on the server that everyone stores their documents on. Recently,
we signed up with Office 365 Online and I set up a SharePoint library and synced it with the document share on our server. A few files aren't being uploaded, though, because of invalid characters (For instance, a file like "Outline/Team plan #3.doc"
Expecting everyone to remember not to use any of the invalid characters isn't really a solution, particularly since I'm not here full-time if things go wrong. I'm looking for a script to run on the server every few minutes that will rename any incompatible
files so that they can be uploaded to SharePoint. Personally, I think it's just plain criminal that Microsoft hasn't provided this functionality itself (it's the least they could do) but that's another rant for another time. Unfortunately, while
I do have a couple of years of experience with basic server administration and group policy, I'm not experienced at all when it comes to PowerShell scripting. I can string together some command line commands in a batch file, and that's about it.
I did find this promising post here:
http://community.spiceworks.com/scripts/show/2097-fix-file-names-for-skydrive-pro-syncing
I was hoping for opinions - is this the sort of thing I'm looking for, and what would be the best way to implement it (eg, every few minutes as a scheduled event)? Also, is this a straight-up powershell script, or are there additional languages/resources
involved? (Like I said, I'm sort of a script newbie).
Additional background: I posted a similar question asking if it could be done with GPOs, and they directed me here, suggesting it could be done with scripts.
Thanks!!

That script that Mike linked to is a good one, i've used it myself a fair few times. Just to weigh in with a bit of information on why those characters are forbidden:
The reason that some characters aren't allowed is that those characters are used as special characters in URLs. If you were to allow them to go into the file names (without 'escaping' them) then all the traffic to and from SharePoint would start to
go horribly wrong.
Now it is theoretically possible to build a tool that recognises the characters, escapes them, then uploads them. As well as updating the SharePoint interface to 'unescape' the characters when it renders them. However it's not a trivial bit of engineering,
you'd have to gut SharePoint and re-do some of the core behaviour. You've then got to re-test it and make sure it doesn't break any previous SharePoint behaviour.
The way MS want you to work is to save the files directly to SharePoint, which would pick up that you have protected characters and prompt the user to correct them. That does break down a bit with OneDrive as you can use the characters locally, it's only
the next step that fails...

[svn] 4261: Fix Eclipse project files for BlazeDS/trunk.

Revision: 4261
Author: [email protected]
Date: 2008-12-09 05:51:20 -0800 (Tue, 09 Dec 2008)
Log Message:
Fix Eclipse project files for BlazeDS/trunk. There were a number of problems. The classpath for the Java projects still included references to the backport jars which we don't have in the tree any more because we no longer support JDK 1.4. The actionsript projects hadn't been updated to reference the new location of things in the Flex 4 SDK so paths to things like playerglobal.swc, resource bundles and Assets.swf were wrong. All projects are building for me now but please let me know if you have any problems.
Modified Paths:
blazeds/trunk/development/eclipse/projects/flex/3.0/framework/.actionScriptProperties
blazeds/trunk/development/eclipse/projects/flex/3.0/framework/.flexLibProperties
blazeds/trunk/development/eclipse/projects/flex/3.0/framework/.project
blazeds/trunk/development/eclipse/projects/flex/3.0/rpc/.actionScriptProperties
blazeds/trunk/development/eclipse/projects/flex/3.0/rpc/.project
blazeds/trunk/development/eclipse/projects/java/blazeds-core/.classpath
blazeds/trunk/development/eclipse/projects/java/blazeds-opt/.classpath

If you have issues with Eclipse please ask question in Eclipse forums or just check documentation.

[svn:fx-4.x] 15123: Fix for ASDoc bugs:

Revision: 15123
Revision: 15123
Author:   [email protected]
Date:     2010-03-29 17:46:28 -0700 (Mon, 29 Mar 2010)
Log Message:
Fix for ASDoc bugs:
@see links are not working in the ASDoc of a style property
@see links in a skinPart ASDoc are not visible
Asdoc tool generates bad links for Vector. type, property detail section
QE notes: None.
Doc notes: None.
Bugs: SDK-26034, SDK-26035, SDK-26036
Reviewed By: Darrell
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-26034
    http://bugs.adobe.com/jira/browse/SDK-26035
    http://bugs.adobe.com/jira/browse/SDK-26036
Modified Paths:
    flex/sdk/branches/4.x/asdoc/templates/all-index.xslt
    flex/sdk/branches/4.x/asdoc/templates/class-files.xslt
    flex/sdk/branches/4.x/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGener ator.java

Stope
Mailing me ***
Sent from my I phone

[svn] 3233: Fix for bug related to see tag, [Exclude] metadata, and extra lines in mxml examples block.

Revision: 3233
Author: [email protected]
Date: 2008-09-16 12:57:29 -0700 (Tue, 16 Sep 2008)
Log Message:
Fix for bug related to see tag, [Exclude] metadata, and extra lines in mxml examples block.
Bugs: SDK-16886
QA: Yes
Doc:
Reviewed By: Pete F
Tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-16886
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

Remember that Arch Arm is a different distribution, but we try to bend the rules and provide limited support for them. This may or may not be unique to Arch Arm, so you might try asking on their forums as well.

[svn] 4241: A collection of minor fixes for FXG transcoding to SWF: matrix attribute name correction; allowing for 0x prefix for hexadecimal colors; allowing for an id attribute on FXG nodes; fixing blur filter quality encoding; fixing the order in which

Revision: 4241
Author: [email protected]
Date: 2008-12-05 11:00:45 -0800 (Fri, 05 Dec 2008)
Log Message:
A collection of minor fixes for FXG transcoding to SWF: matrix attribute name correction; allowing for 0x prefix for hexadecimal colors; allowing for an id attribute on FXG nodes; fixing blur filter quality encoding; fixing the order in which bevel filter colors are encoding - the SWF specification appears to have the wrong order specified; updating SwfxPrinter to display a linestyle's fillstyle (if present).
Temporarily removing generated id attribute emitted in FXG to SWF optimization as this attribute is not present in the AS impl.
Also updating compiler error base types to allow a rootcause to be specified for additional detail to a compiler message exception.
QE: No
Doc: No
Checkintests: Pass
Reviewer: Discussed compiler base error change with Paul.
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/CompilerException.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/EmbedEvaluator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/util/CompilerMessage.java
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/FXGConstants.java
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/dom/AbstractFXGNode.java
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/dom/TextGraphicNode.java
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/swf/AbstractFXGGraphics.java
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/TagDecoder.java
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/TagEncoder.java
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/tools/SwfxPrinter.java

[svn:fx-trunk] 11193: fix packaged build file for textlayout to accommodate the recent changes made to that project

Revision: 11193
Author:   [email protected]
Date:     2009-10-27 13:08:28 -0700 (Tue, 27 Oct 2009)
Log Message:
fix packaged build file for textlayout to accommodate the recent changes made to that project
QE notes: no
Doc notes:
Bugs: sdk-23302
Reviewer:
Tests run: checkintests
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23302
Modified Paths:
    flex/sdk/trunk/frameworks/build_framework.xml

There are two main annoying problems with Flash Builder and swc's:
1. Flash Builder doesn't reflect changes made to swc files
Solution : First of all - keep your swc files inside your project folder, you can also disable global swc cache: change as3api.cpp code,refresh swc in flashBuilder bug!
2. Flash Builder breakes content inside swc files (and also popular problem "TypeError: Error #1034: Type Coercion failed: cannot convert flash.display::MovieClip@1f21adc1 to...")
Solution : locate the project .actionScriptProperties file and set useFlashSDK=”false” : Flash Builder 4.7 – useFlashSDK | In Flagrante Delicto!
In this case you can also download latest Apache Flex SDK to target new Flash player versions: http://flex.apache.org/
Hope this helps!
P.

[svn:fx-4.x] 15104: Fix for invalid links for @see of inherited styles

Similar Messages

Maybe you are looking for