I could not play the parallel effect which is defined by the following code:
var parallel:Parallel=new Parallel();
var E1:WipeDown=new WipeDown();
var E2:WipeLeft=new WipeLeft();
parallel.addChild(E2);
parallel.addChild(E1);
parallel.duration=2000;
parallel.target=this;
parallel.play();
On playin the effect by calling effect() function only the effect E1 is getting played.
If the code was:
parallel.addChild(E1);
parallel.addChild(E2);
instead of:
parallel.addChild(E2);
parallel.addChild(E1);
then only the effect E2 is getting played..
To summurize only the top most child effect is getting played..
Can any one plese suggest a solution...
<code>
<mx:Parallel target="{this}" id="wipeDownLeft" duration="2000">
<mx:WipeDown target="{this}" duration="2000"/>
<mx:WipeLeft target="{this}" duration="2000"/>
</code>
If above code is not clear one can check with this application(copy the code and run)
code
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="http://www.adobe.com/2006/mxml" layout="absolute" minWidth="1024" minHeight="768" xmlns:ns1="*">
<mx:Canvas id="C" creationComplete="{E.play()}" width="50%" height="50%" backgroundColor="#387C44">
</mx:Canvas>
<mx:Parallel id="E" duration="2000">
<mx:WipeLeft duration="2000" target="{C}"/>
<mx:WipeDown duration="2000" target="{C}"/>
</mx:Parallel>
<mx:Button click="E.play([C])" x="{C.width+10}" y="{C.height+10}">
</mx:Button>
</mx:Application>
Maybe try setting the target property for each of the child effects instead?
Probably wouldnt hurt to do this for duration either...
I have only used effects in mxml, and this it how ive always done it (same with the doc examples?) - in fact have even done the dual wipe you are trying here, but not in AS...
[Edit] - I cannot see your mxml unlessI go into edit mode, but i cannot submit edits - use the code tags on it...
but same again, specify target and duration for the children not the parallel...
I think, the reason that, WipeLeft and WipeDown are mutually exclusive effects. But must performed in parallel. if you replace a to the , then it will be work. Or if you replace WipeLeft (or WipeDown) effect to some other effect, f.ex. , then it will be work too.
Related
I'm using XPROC and the XPROC Processor MorganaXProc-IIIse. I'm actually just trying to create a directory through XPROC. However, all I get is this error message:
No visible declaration for '{http://www.w3.org/ns/xproc-step/filesystem}file-mkdir' found: Check spelling, imports or #use-when values.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<p:declare-step xmlns:p="http://www.w3.org/ns/xproc" xmlns:pf="http://www.w3.org/ns/xproc-step/filesystem" name="pipeline" version="3.0">
<p:variable name="base.dir" select="'.'"/>
<pf:file-mkdir href="${basedir}/lib"/>
</p:declare-step>
Since documentation is very limited, any hint is appreciated.
Thanks
In the context of XProc 3, the file-mkdir step is in the namespace http://www.w3.org/ns/xproc so using the prefix p your pipeline declares for that should work: <p:file-mkdir href="${basedir}/lib"/> instead of <pf:file-mkdir href="${basedir}/lib"/>.
Having some trouble setting a WizardStyle in QTIFW I have read the documentation and cant understand why the following doesn't work.
<'WizardStyle>Mac<'/WizardStyle>
<'Background>logo.png<'Background>
(Obviously excluding ' char)
Qt Documentation:
Background - Filename for an image used as QWizard::BackgroundPixmap
(only used by MacStyle). WizardStyle - Set the wizard style to be used
("Modern", "Mac", "Aero" or "Classic").
I get the following error:
Caught exception: Error in config\config.xml, line 8, column 17: Unexpected element 'WizardStyle'
<?xml version="1.0" encoding="UTF-8"?>
<Installer>
<Name>Dave Installer</Name>
<Version>1.2.3</Version>
<Title>Dave Installer</Title>
<Publisher>Dave</Publisher>
<Icon>qticon</Icon>
<WizardStyle>Mac</WizardStyle>
<Background>logo.png</Background>
<StartMenuDir>Super App</StartMenuDir>
<TargetDir>#RootDir#InstallationDirectory</TargetDir>
<RunProgram>#TargetDir#/qt</RunProgram>
<RunProgramDescription>Qt Installer</RunProgramDescription>
</Installer>
According to comments made in bug 470 and 452, the WizardStyle tag implementation never made it into the v1.5 release (at least the compiled binary). So you'll have to get a later release (the master is at ~v2.0).
I have several hundred placemarks that are all in one folder. I'm trying to make the labels appear only below a certain altitude. (The placemarks were created by exporting a layer from ArcGIS, and I presume that the altitude should be specified in the units used by the coordinate system of the layer, in this case, in feet; correct me if I'm wrong.) However, nothing I do with the <Region> tag seems to work; the labels happily appear at all altitudes. Here is the code that I'm using; can anyone tell what is wrong with it?
<Document id="DocumentName">
<name>NameGoesHere</name>
<Snippet></Snippet>
<Folder id="NameOfTheFolder">
<name>NameGoesHere</name>
<Region id="highAltitude">
<LatLonAltBox>
<north>40</north>
<south>37</south>
<east>-74</east>
<west>-79</west>
<minAltitude>50000</minAltitude>
<maxAltitude>500000</maxAltitude>
</LatLonAltBox>
<LabelStyle id="styleNameHere">
<scale>0</scale>
</LabelStyle>
</Region>
<Snippet></Snippet>
...
<placemark> ... </placemark>
<placemark> ... </placemark>
<placemark> ... </placemark>
...
</Folder>
</Document>
The point of all this code is to suppress labels at altitudes above 50,000 feet, but it does nothing of the sort. Toward the end of the code, after the </Folder> tag but before the </Document> tag, there is some code, generated when the file was exported, that specifies label styles. But whether or not I delete the <scale> part of it, it seems to have no effect. That code is as follows:
<Style id="Stylename">
<IconStyle>
...
</IconStyle>
<LabelStyle>
<color> ... </color>
<scale> ... </scale>
</LabelStyle>
<PolyStyle>
...
</PolyStyle>
</Style>
I suspect that I'm doing something wrong here in terms of syntax, but, because I've had no experience with KML at all until a few days ago, I'm not sure what the issue is. I appreciate any ideas as to why this isn't working.
You need to define the Lod (Level of Detail) in the Region otherwise it will always appear.
<Region id="highAltitude">
<LatLonAltBox>
...
</LatLonAltBox>
<Lod>
<minLodPixels>256</minLodPixels>
</Lod>
<Region>
The minLodPixels defines the size of the region where if it is less than this minimum number of pixels on the screen then the region is not shown.
https://developers.google.com/kml/documentation/kmlreference#lod
Also, the LabelStyle is not valid within the Region. That must appear in a <Style> element. If KML doesn't behave as you'd expect 9 out of 10 times the syntax is wrong -- try to validate it using a KML validator.
I am changing my code to use binds in XForms (which is better practice than using nodesets everywhere!) but I am getting errors.
The error message I receive is: "Error: XForms Error (8): id (data_criterion) does not refer to a bind element..."
From tutorials/guides I have been using, it seems as though this should work, but clearly I am missing something! (btw, I was modeling my binding code after the examples here: http://en.wikibooks.org/wiki/XForms/Bind)
I originally thought the problem was due to the fact I was using xf:select controls as opposed to xf:input like the examples, but even once I dumbed down my code to the most simplistic code, I still receive errors!
This is the model code I am using:
<xf:model id="select_data">
<xf:instance id="criteria_data" xmlns="">
<file>
<criteria>
<criterion></criterion>
</criteria>
</file>
</xf:instance>
<bind id="data_criterion" nodeset="instance('criteria_data')/criteria/criterion"/>
</xf:model>
As for the ui code, this is what I have:
<xf:input bind="data_criterion">
<xf:label>Enter criteria:</xf:label>
</xf:input>
The error message I receive is: "Error: XForms Error (8): id (data_criterion) does not refer to a bind element..."
Anyone have any insight to what the problem is? Also, is there any special usage of bindings and xf:select (with xf:itemset) controls that I should be aware of? (I am ultimately using a lot of xf:select controls on my form..)
Thanks in advance!
EDIT:
I ran the code through this validator, and I got this message (refers to the bind line):
"Warning: Should the following element have the XForms namespace applied?: bind (line 66)"
A couple of things you might want to change:
Not sure of this is the reason for the error, but the nodeset expression should be instance('criteria_data')/criteria/..., without file. Remember: instance() returns the root element, not the document node. (This one you took care by updating the question; good)
You are missing the xf on the bind. It should be: <xf:bind id="data_criterion" nodeset="instance('criteria_data')/criteria/criterion"/>.
See below a full example with your code, which works fine for me under Orbeon Forms:
<xhtml:html xmlns:xhtml="http://www.w3.org/1999/xhtml"
xmlns:xforms="http://www.w3.org/2002/xforms"
xmlns:xf="http://www.w3.org/2002/xforms"
xmlns:xxforms="http://orbeon.org/oxf/xml/xforms"
xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:fr="http://orbeon.org/oxf/xml/form-runner">
<xhtml:head>
<xhtml:title>SO Bind</xhtml:title>
<xf:model id="select_data">
<xf:instance id="criteria_data" xmlns="">
<file>
<criteria>
<criterion>Gaga</criterion>
</criteria>
</file>
</xf:instance>
<xf:bind id="data_criterion" nodeset="instance('criteria_data')/criteria/criterion"/>
</xf:model>
</xhtml:head>
<xhtml:body>
<xf:input bind="data_criterion">
<xf:label>Enter criteria:</xf:label>
</xf:input>
</xhtml:body>
</xhtml:html>
I just bought and installed the Flash Builder 4 after having the Beta for a while. The same code is giving me compile-time errors and suggests using mx1 instead of mx! If I make it mx1 the compile error goes away. Here is the top of my component:
<s:SkinnableContainer xmlns:fx="http://ns.adobe.com/mxml/2009"
xmlns:s="library://ns.adobe.com/flex/spark"
xmlns:mx="library://ns.adobe.com/flex/halo"
I mentioned nothing about mx1.
I used:
xmlns:mx="library://ns.adobe.com/flex/mx"
instead of:
xmlns:mx="library://ns.adobe.com/flex/halo"
and it worked.