[svn:bz-trunk] 8796: Forgot to check this in with my earlier check-in.

Revision: 8796
Author:   [email protected]
Date:     2009-07-24 06:21:48 -0700 (Fri, 24 Jul 2009)
Log Message:
Forgot to check this in with my earlier check-in.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/client/exceptions/ClientStatusExcept ion.java

Open a clip in the affected sequence in the viewer, go to the motion tab, and under distort, try changing the number by adding or subracting 33.33. If it works, copy the clip, and paste attributes to all your other affected clips.

Similar Messages

Edit postDelete postReport this postReply with quote ATP check but the comm

hi , all guys :
when I create the pp-pi order , first i use the batch determination to allocate the component
batch , then i do the ATP check , but the committed quantity always is zero ,the ATP alway does
not support confirm quantity (co09 the confirm quantity always is zero),so when i create the other pp-pi order the stock quantity always cover the reqirements quantity of components
in the mater data , i use the ATP group is 02 (the customizing is standard) i think the ATP scope is irrelative to this issue .
in the order type control parameters , i use the ATP check
for example :
the componet 100-200 have three batchs :
batch: 20100501 quantity 30 kg
batch: 20100502 quantity 40 kg
batch: 20100601 quantity 40 kg
now , the requirment of component 100-200 is 100 kg
the batch determination conditions is self expiration .
so i throght the batch determination and batch split to allocate the bacth and quantity is
batch: 20100501 quantity 30 kg
batch: 20100502 quantity 40 kg
batch: 20100601 quantity 30 kg
after allocating , i run the ATP check ,BUT the COMMITED QUANTITY ALWAYS IS ZERO .
I don't know why !!! ,where can configure the ATP confirm quantities (committed quantities) the in the customizing
can you give help me!!!
thanks!!!
best regards

Davis:
Check in MRP Group settings, Availability Check session, flag activate full confirmation logic. Test activate full confirmation logic.
Regards,
Ricardo

When placing icons on the menu bar, I can not increase size to large icons. I can make icons larger when putting icons on other bars below menu bar. Never had this problem with any earlier version of FF

This happens with all icon themes including default. I like having the large icons on the menu bar so hopefully this can be fixed.

NO way.
Mylenium

[svn:fx-trunk] 7687: Forgot to have WindowedSystemManager use instance instead of static for mixins .

Revision: 7687
Author:   [email protected]
Date:     2009-06-09 13:41:18 -0700 (Tue, 09 Jun 2009)
Log Message:
Forgot to have WindowedSystemManager use instance instead of static for mixins. (regular SystemManager was changed to use instance instead of static before checkin)
Also fix porting error in MarshallPlan.as
QE Notes: None
Doc Notes: None
Bugs: SDK-21461
Reviewer: darrell
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21461
Modified Paths:
    flex/sdk/trunk/frameworks/projects/airframework/src/mx/managers/WindowedSystemManager.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/managers/systemClasses/MarshallPlan.a s

Hi Chris,
I tried removing and adding back the dialpeer 101 and adding .T to 501 but still the same result. Please help.
Please see the following:
SEC-HO-VGATEWAY01#show dial-peer voice summ
dial-peer hunt 1
             AD                                    PRE PASS                OUT
TAG    TYPE MIN OPER PREFIX    DEST-PATTERN      FER THRU SESS-TARGET    STAT PORT    KEEPALIVE
501    voip up   up                                0 syst
1001   voip up   up             5...               1 syst ipv4:10.13.14.21
1002   voip up   up             1...$              1 syst ipv4:10.13.14.21
103    voip up   up             911$               1 syst dns:toronto2.voip.ms
102    voip up   up             1[2-9]..[2-9]...- 1 syst dns:toronto2.voip.ms
                                 ...$
101    voip up   up             [2-9]..[2-9]....- 1 syst dns:toronto2.voip.ms
                                 ..$
SEC-HO-VGATEWAY01#show run | sec dial-peer voice 501
dial-peer voice 501 voip
incoming called-number .T
voice-class sip bind control source-interface Loopback0
voice-class sip bind media source-interface Loopback0
dtmf-relay rtp-nte
codec g711ulaw
no vad

Report this postReply with quote Credit check for unconfirmed item

Hello,
I have configured automatic credit control for sales orders.
When a confirmed order quantity is entered, I get a warning message plus the credit block, just as I need. If I have no confirmed quantity of the items, I get no message, just a saved order.
Our item confirmation is done only on what is in stock, not on RLT, so it is common that an item has 0 confirmation. I need a credit block if the value would otherwise exceed the open credit limit? How can I do this? I've tried both the static and dynamic checks, but they only work with confirmed quantities.
Thanks

pricing:
   step Des                      From     print     subtotal
   120   Total                                   X        1
   130   Credit value           120         X        A
and also in automatic credit control select open orders
but system calculate the credit value=confirmed quantity*price.

[svn:fx-trunk] 10503: Prepping to update textLayout sources with a more recent build.

Revision: 10503
Author:   [email protected]
Date:     2009-09-22 09:18:51 -0700 (Tue, 22 Sep 2009)
Log Message:
Prepping to update textLayout sources with a more recent build. TLFTextField is no longer in textLayout since we now own it. It is being moved to spark.swc and will live with UITLFTextField in mx.core.
QE notes:
Doc notes:
Bugs:
Reviewer: Gordon asked me to do this
Tests run: checkintests and a few of my own that use TLFTextField
Is noteworthy for integration: perhaps
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/TextFieldFactory.as
    flex/sdk/trunk/frameworks/projects/spark/src/SparkClasses.as
    flex/sdk/trunk/frameworks/projects/spark/src/mx/core/UITLFTextField.as
    flex/sdk/trunk/frameworks/projects/textLayout/build.xml
Added Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/mx/core/TLFTextField.as
Removed Paths:
    flex/sdk/trunk/frameworks/projects/textLayout/textLayout_textField/

Good show...pleased to see the speed and performance of a ram based PKGBUILD.
My system has no HDD, is based on Compact Flash devices in Faunos. I may give this procedure a tryout on a "Live" system.
EDIT:
Faunos already uses tmpfs so I guess the PKGBUILDS already perform in ram along with the system via aufs for downloads.
Last edited by lilsirecho (2008-09-14 22:47:31)

[svn:fx-trunk] 10943: Fix to dragging from List with multiple-selection

Revision: 10943
Author:   [email protected]
Date:     2009-10-08 15:46:27 -0700 (Thu, 08 Oct 2009)
Log Message:
Fix to dragging from List with multiple-selection
- The fix is to postpone the selection commit until we make sure the user has not started a drag gesture.
- Exclude the dragEnabled, dropEnabled, dragMoveEnabled properties for DropDownList
QE notes: None
Doc notes: None
Bugs: None
Reviewer: Deepa
Tests run: checkintests, mustella List, DropDownList
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/DropDownList.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/List.as

Checking PDF Resolution with Preflight Single Checks

While checking resolution with Acrobat 10.1.1, I am baffled and need comments from you all on how to interpret the following preflight reports:
Checking whether the ppi of my PDF is less than 150 results in a big red X and then states that the document is 96ppi?
And - why do the results state No Problems Found when a check is run on the same document asking whether the resolution is between 100 - 120 ppi if the document is indeed 96ppi ?

If the method seems complicated, I think it may be that, like many people, you don't realise that the question is complicated too.
It is best not to say "resolution of a PDF" because it sounds as if a PDF has just one resolution. If it were that simple there would be a box to popup with that resolution.
Rather, each image in a PDF has a resolution, potentially different. So you need to use preflight, to check every image against the rules you want.
So you can't say "the resolution of my document is 96 ppi". Rather, "my document contains at least one image at 96 ppi". The others might be the same, or this might be the only one, with all the others at (say) 300 ppi.

[svn:bz-trunk] 10020: Had previously updated user-agent string for Opera 10 in resources/config/ services-config.xml on DataServices/trunk.

Revision: 10020
Author:   [email protected]
Date:     2009-09-04 07:35:51 -0700 (Fri, 04 Sep 2009)
Log Message:
Had previously updated user-agent string for Opera 10 in resources/config/services-config.xml on DataServices/trunk. Forgot to do this for the file on BlazeDS/trunk.
Modified Paths:
    blazeds/trunk/resources/config/services-config.xml

Revision: 10020
Author:   [email protected]
Date:     2009-09-04 07:35:51 -0700 (Fri, 04 Sep 2009)
Log Message:
Had previously updated user-agent string for Opera 10 in resources/config/services-config.xml on DataServices/trunk. Forgot to do this for the file on BlazeDS/trunk.
Modified Paths:
    blazeds/trunk/resources/config/services-config.xml

Check string validity with pattern

hello,
I want to check the validity of strings given by the user. The only characters authorized are : 'a' to 'z', 'A' to 'Z', '0' to '9', '.', '-', '_', '*', '@' and ' ' (space)
i want to check this string with a pattern but it does not work.
Somebody can help me for the pattern because the API javadoc is poor and i have a limited web access in my agency.
Thanks
   String regex = "[a-zA-Z0-9.*-_@]";
   System.out.println(regex);
   boolean bol = Pattern.matches(regex, field);
   System.out.println(bol);
   ->> result always false for string field="Indy jones";

try this:
import java.sql.*;
import java.io.*;
import java.util.regex.*;
import java.util.*;
public class RegExTest2 {
public static void main (String args[]) {
Pattern pat = null;
Matcher m = null;
String patternToMatch = "^[a-zA-Z0-9\\.\\*\\-\\_@\\s]+$";
String line1 = "IndianaJones";
String line2 = "Indiana Jones";
String line3 = "Indiana - Jones";
String line4 = "Indiana&Jones";
String line5 = "Indiana & Jones";
String line6 = " Indiana Jones ";
String line7 = "Indiana Jones =";
pat = Pattern.compile(patternToMatch);
System.out.println("Pattern to match = " + patternToMatch);
boolean bol = Pattern.matches(patternToMatch, line1);
System.out.println("line1 : expected true and got " + bol);
bol = Pattern.matches(patternToMatch, line2);
System.out.println("line2 : expected true and got " + bol);
bol = Pattern.matches(patternToMatch, line3);
System.out.println("line3 : expected true and got " + bol);
bol = Pattern.matches(patternToMatch, line4);
System.out.println("line4 : expected false and got " + bol);
bol = Pattern.matches(patternToMatch, line5);
System.out.println("line5 : expected false and got " + bol);
bol = Pattern.matches(patternToMatch, line6);
System.out.println("line6 : expected true and got " + bol);
bol = Pattern.matches(patternToMatch, line7);
System.out.println("line7 : expected false and got " + bol);
} // end main
} //End Class RegExTest2

[svn:fx-trunk] 7787: this should not have been checked in.

Revision: 7787
Author:   [email protected]
Date:     2009-06-12 09:24:18 -0700 (Fri, 12 Jun 2009)
Log Message:
this should not have been checked in. This will fix the build.xml
bugs: no
qa: no
checkintests: pass
Modified Paths:
    flex/sdk/trunk/frameworks/build.xml

[svn:fx-trunk] 12912: With TLF 571 checked in we can now revert the MXML 2009 changes for how the id language attribute is processed .

Revision: 12912
Revision: 12912
Author:   [email protected]
Date:     2009-12-14 12:08:35 -0800 (Mon, 14 Dec 2009)
Log Message:
With TLF 571 checked in we can now revert the MXML 2009 changes for how the id language attribute is processed.
An unqualified id property will no longer be seen as a setter for a normal public, writable, non-static "id" property - which matches Flex 3 behavior.
As in earlier versions of Flex, the mechanism to retain MXML id attribute information at runtime is to implement mx.core.IMXMLObject. The compiler will generate a call to the intialized() method and pass in the id information.
Note: One exception to this rule seems to be UIComponent which instead get id attribute information via mx.core.IDeferredInstantiationUIComponent (although there seems to be a TODO in the codebase to remove this mechanism and thus should not be relied on by third parties).
QE notes: Please add tests for the TLF id property on flow elements (div, span, p, etc).
Doc notes: Please check that we have not documented
Bugs: N/A
Reviewer: Paul
Tests run: Checkintests, local test cases.
Is noteworthy for integration: Yes
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/FrameworkClasses.as
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/UIComponent.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/core/SpriteVisualElement.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/primitives/supportClasses/GraphicEleme nt.as
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ComponentBuilder.jav a
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/lang/StandardDefs.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/Type.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/TypeTable.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/init/ValueInitializer.ja va
Removed Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/core/IID.as

This is a duplicate post. This should be locked to avoid further confusion.
My CSS wont change
Nancy O.

[svn] 3793: Alpha checkin - checking this in on behalf of Paul a fix for SDK-17698.

Revision: 3793
Author: [email protected]
Date: 2008-10-21 13:25:39 -0700 (Tue, 21 Oct 2008)
Log Message:
Alpha checkin - checking this in on behalf of Paul a fix for SDK-17698. Paul's change now means advanced CSS functionality is available by default and -keep no longer needs to be specified.
QE: Yes
Doc: No
Checkintests: Pass
Styles Mustella Tests: Pass
Reviewer: Pete
Bugs:
SDK-17698 - [Advanced CSS] You need to compile with -keep to get Advanced CSS to work (because of direct AST generation)
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-17698
http://bugs.adobe.com/jira/browse/SDK-17698
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/ImplementationGenerator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/MxmlDocument.java
flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

I removed the src/ directory and ran makepkg and it succeeded. Pacman -U kernel.pkg.tar.gz also worked. Now all that's left is rebooting and trying.
Thanks everyone.
OK, I guess it's not over yet. I rebooted in the new kernel, but it says it can't find /dev/sda3 (which is my / partition).
This is my grub entry:
title Arch Linux Gigamo
root (hd0,2)
kernel /boot/vmlinuz26 root=/dev/sda3 ro
initrd /boot/kernel26-gigamo.img
Okay well, I didnt realise there was a vmlinux26-gigamo as well. Will see if that fixes it.
Last edited by Gigamo (2008-03-12 16:53:22)

[svn:fx-trunk] 10214: This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList - damageHandler - invalidateDisplaylist - back to updateDisplayList.

Revision: 10214
Author:   [email protected]
Date:     2009-09-13 07:33:58 -0700 (Sun, 13 Sep 2009)
Log Message:
This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList -> damageHandler -> invalidateDisplaylist -> back to updateDisplayList. The bug file was for TextArea which is RET but the same bug was in RichText as well.
This example with a renderer exposed it because the typicalItem that is composed to figure out sizes and the actual first item in the list share the same textFlow. It actually has nothing to do with useVirtualDisplay other than it was sharing a textFlow.
It turns out that the TextFlowFactory dispatches damage events every time the textFlow is composed. Unlike when the flowComposer is used, it always considers the flow damaged. It was exacerbated by each of the two components having a damage handler for the same textFlow.
The solution is to use the textFlow generation number. In the damageHandler if the generation is the last known generation number, assume no changes, and return immediately from the damage handler.
QE notes: There are 1 TextArea, 6 TextInput and 2 NumericStepper failuers, with or without my changes. The common link seems to be DispatchKeyEvent. Most were testing maxChar, displayAsPassword and restrict. I tested these and they seem to be working correctly.
Doc notes:
Bugs: SDK-23002
Reviewer: Gordon
Tests run: checkintests, TextArea, TextInput and NumericStepper
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23002
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichEditableText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/RichEditable TextContainerManager.as

Revision: 10214
Author:   [email protected]
Date:     2009-09-13 07:33:58 -0700 (Sun, 13 Sep 2009)
Log Message:
This fixes the problem that if two text components share the same textFlow there is an infinite loop involving updateDisplayList -> damageHandler -> invalidateDisplaylist -> back to updateDisplayList. The bug file was for TextArea which is RET but the same bug was in RichText as well.
This example with a renderer exposed it because the typicalItem that is composed to figure out sizes and the actual first item in the list share the same textFlow. It actually has nothing to do with useVirtualDisplay other than it was sharing a textFlow.
It turns out that the TextFlowFactory dispatches damage events every time the textFlow is composed. Unlike when the flowComposer is used, it always considers the flow damaged. It was exacerbated by each of the two components having a damage handler for the same textFlow.
The solution is to use the textFlow generation number. In the damageHandler if the generation is the last known generation number, assume no changes, and return immediately from the damage handler.
QE notes: There are 1 TextArea, 6 TextInput and 2 NumericStepper failuers, with or without my changes. The common link seems to be DispatchKeyEvent. Most were testing maxChar, displayAsPassword and restrict. I tested these and they seem to be working correctly.
Doc notes:
Bugs: SDK-23002
Reviewer: Gordon
Tests run: checkintests, TextArea, TextInput and NumericStepper
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-23002
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichEditableText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/RichText.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/RichEditable TextContainerManager.as

[svn:bz-trunk] 24053: Protect debug log messages with a isDebug() check.

Revision: 24053
Revision: 24053
Author:   [email protected]
Date:     2013-04-26 00:58:17 -0700 (Fri, 26 Apr 2013)
Log Message:
Protect debug log messages with a isDebug() check. The stringification of (large) parameters takes a heavy toll on performance otherwise.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Output.java

Revision: 24053
Revision: 24053
Author:   [email protected]
Date:     2013-04-26 00:58:17 -0700 (Fri, 26 Apr 2013)
Log Message:
Protect debug log messages with a isDebug() check. The stringification of (large) parameters takes a heavy toll on performance otherwise.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/io/amf/Amf3Output.java

[svn:bz-trunk] 8796: Forgot to check this in with my earlier check-in.

Similar Messages

Maybe you are looking for