Confused by the behavior on importing simple tagged text

I have a tagged text file with the following content beween the dashed lines. (the lines are not part of the file). Both IText and BText are predefined paragraph sytles.
<ASCII-WIN>
Price <ParaStyle:IText>AA<cPosition:Superscript>aa<cPosition:> - <ParaStyle:BText>BB<cPosition:Superscript>bb<cPosition:>
Once imported, the result is not what I expected. Specifically,
1. All text are imported with the BText paragraph style.
2. It shows the "bb" as superscripted, but not the "aa".
Why is that? And how can I have different styles for the AAaa part versus the BBbb part?
This can be reproduced on CS5 and CS5.5. Didn't try any older versions.
Thanks.

When I think of it, the first behavior makes sense, because the text were specified as a continuous line without line break, they are treated as a single paragraph. And for a paragraph, only one paragraph can be used, and the one that is specified later, BText in this example, wiins.
But still, why does the import routine ignores the superscript character style on "aa" before the second paragraph style tag?

Similar Messages

CS3/JS: Code to import x-tagged text into Indesign

Hi All,
Normally we import text as X-Tag using Em Software plugin manually. We developed a script for auto-pagination in Indesign. But we couldn't find any JS code to import X-tagged text anywhere. So we used word file to import but facing lot of issues while importing word file into Indesign.
Is there any javascript code to import text with X-tag plugin? If so, kindly provide. It will be be helpful for us very much.
Thanks in advance.
regards
Masthan

An external plugin can only (*) be used in Javascript if the original programmers added support for it. Best is to check its documentation, and if it's not mentioned in there, contact the authors.
(*) Perhaps you can locate its menu entries and use those instead. I wouldn't know at all if that works with external plugins.

Importing Adobe Tagged Text

Hello,
So here's what's happening…
I've installed a Wordpress plugin that exports posts as Adobe Tagged Text.
When I import, the text still shows up marked up with tags, just as it looks in the .txt file:
<ANSI-MAC>
<DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle><cColor:Registration ><cSize:10><cLeading:11><pFirstLineIndent:12><cFont:Times New Roman>>
<ParaStyle:NormalParagraphStyle>This <cTypeface:Italic>is<cTypeface:> a <cTypeface:Bold>test<cTypeface:>
<ParaStyle:NormalParagraphStyle>Test paragraph
<ParaStyle:NormalParagraphStyle>Testing this out
Does it have something to do with the first line of code, <ANSI-MAC>?
Regards,
Eric

You're using a very old InDesign workflow which I've never used. But it's referenced in Olav Kvern's and David Blatner's excellent "Real World InDesign" (I'm looking at the CS4 edition).
On page 235, it reads, "The first characters in a tagged text file must state the character encoding (ASCII, ANSI, UNICODE, BIG5, or SJIS), followed by the platform (MAC or WIN). So the typical Windows tagged text begins with <ASCII-WIN> , and the Macintosh version begins with <ASCII-MAC> ."
It looks to me like it should work. Have you tried exporting some tagged text from InDesign to see how it looks? File > Export > Adobe InDesign Tagged Text.

Import ID tagged text file results in paragraph style overrides

I have been working on a project that requires the import of a large amount of information from a database. I have defined all the paragraph styles in InDesign and have a program to apply the paragraph style to the database information creating the InDesign Tagged Text file. When I place it into my document the paragraph styles are recognized but there is an override. If I clear the override, the text looks fine. I have an example document that I have exported and imported some text to rule out the program, but even in this case, an override occurs. Text is there, the paragraph format is there, but font size (for example) is wrong. Where should I be looking to correct this issue?
Harold

I don't recognize any of those being wrong, per se. I have the file on another computer, so I mocked up yet another one. Sorry
Again in this one I did ASCII export, no fancy characters. And this one demonstrates the problem, too. I have two kinds of paragraphs. A big one and a small one. I create those paragraph styles. I select the only two lines in the file. Export and then bring them in underneath themselves to compare.
The paragraph styles for the newly Placed paragraphs are gone. The font color is the same. But the font size and font have not changed.
I manually edited the IDTT and removed the <Japanese feature> tag. Placed it again. Font color is the same, but the size and font are wrong.
In other words, my problem is that ID does not seem to apply the paragraph style to the text when it is imported. Aren't the font size and font defined in the Paragraph Style?
My end goal is to define some paragraph styles and create the IDTT automatically from a database. My hope was that the paragraphs would be formated properly based on the predefined styles when the IDTT comes in. I cannot get it to do this even for a pared down example. Aren't other users doing this?
Here is the IDTT on pastebin (with the <Japanese...> tag removed)
http://pastebin.com/Vdc6NVDV
And what it looks like after the intial Place with <Japanese...> tag in, edited line from Small to "Deleted Japanese feature...", removed tag from IDTT and then did another Place.

Linked Adobe Tagged Text files importing without styles

I have several data-heavy weekly publications where suddenly, the link to all Adobe Tagged Text format files have the proper paragraph styles and character styles stripped on being placed. I'm aware of the default settings issue, where you deselect all and make sure the character styles is none, and that does not seem to be the issue. Specifics are
Working in CS 5 (Version 7.0.4)
The Adobe Tagged Text format files are exported from Excel spreadsheets
The InDesign documents have links to the Adobe Tagged Text format files, and Update Link is used inside InDesign to update the text when the file is exported from the spreadsheet.
When the publications are opened on my workstation, ALL files linked to Adobe Tagged Text files are not imported correctly, they revert to the Basic Paragraph style.
These are not new documents I'm designing or new Adobe Tagged Text files, this is part of a production process that has worked without issue for years.
When the same documents are opened on another workstation, and Update Links used, they come in perfectly, so it doesn't seem to be a document or file corruption problem, but a problem with my environment or ID settings.
It's not one specific document or file, it is every single document that has a link to an Adobe Tagged Text file (and we have lots, I tried several!)
I've opened the text files in the text editor to check them, but as I mentioned: same document, same files, I'm the only one who can't update without stripping out the styles.
Thanks! Nancy

Hi, Peter! Thanks for the response. Yes, it's really Tagged Text. See below. After exporting from the spreadsheet and database, opening the document in InDesign, and selecting update link, we do no editing in InDesign after the fact because everything is already setup exactly as we want it with the Tagged Text format.
I have literally hundreds of these among several different documents, updated weekly, mainly dealing with prices and numbers. Every one of the links to Tagged Text format files in every publication now strips out the Tagged Text paragraph style and character style formatting on Update Link on my workstation only. On my other two workstations, the links update without issue, and everything is correct in the final document.
So I'm beginning to think I need to look at rebuilding something, maybe as Joel said, replacing preferences. I keep looking for a workstation or ID option that might effect this.
<ANSI-WIN>
<vsn:6><fset:InDesign-Roman><ctable:=<Black:COLOR:CMYK:Process:0,0,0,1>>
<dps:Pnl Comp\:Pnl Comp \$Numbers=<Nextstyle:Pnl Comp\:Pnl Comp \$Numbers>>
<dps:Pnl Comp\:Pnl Comp Bold \$Numbers=<BasedOn:Pnl Comp\:Pnl Comp \$Numbers><Nextstyle:Pnl Comp\:Pnl Comp Bold \$Numbers>>
<dps:Pnl Comp\:Pnl Group \$Numbers=<BasedOn:Pnl Comp\:Pnl Comp \$Numbers><Nextstyle:Pnl Comp\:Pnl Group \$Numbers>>
<pstyle:Pnl Comp\:Pnl Comp Bold \$Numbers> $302 $302 $278
<pstyle:Pnl Comp\:Pnl Group \$Numbers> 203 202 211
<pstyle:Pnl Comp\:Pnl Group \$Numbers> 456 458 393

[IDCS3 WIN] Assert while importing tagged text

Hi, I use the following code to import a tagged text from a buffer into a text frame: IDataBase* database = frameUIDRef.GetDataBase(); InterfacePtr<IHierarchy> frameHierarhy(frameUIDRef, UseDefaultIID()); int32 count = frameHierarhy->GetChildCount(); InterfacePtr<IMultiColumnTextFrame> textFrame(frameHierarhy->QueryChild(0), UseDefaultIID()); if( !textFrame ) return UIDRef::gNull; UID storyUID = textFrame->GetTextModelUID(); InterfacePtr<ITextModel> textModel(database, storyUID, UseDefaultIID()); if( !textModel ) return UIDRef::gNull; UIDRef result = UIDRef::gNull; InterfacePtr<IK2ServiceRegistry> services(gSession, UseDefaultIID()); InterfacePtr<IK2ServiceProvider> service(services->QueryServiceProviderByClassID(kImportProviderService, kTaggedTextImportFilterBoss)); InterfacePtr<IImportProvider> prov(service, IID_IIMPORTPROVIDER); InterfacePtr<IPMStream> stream(StreamUtil::CreatePointerStreamRead(taggedtext, strlen(taggedtext))); if (prov->CanImportThisStream(stream) == IImportProvider::kFullImport) { database->BeginTransaction(); prov->ImportThis(database, stream, K2::kSuppressUI, &result); //This line generates the Assert if (result != nil ) { Utils<ITextUtils> textUtils; InterfacePtr<ICommand> moveAllStoryCommand(textUtils->QueryMoveStoryFromAllToAllCommand(result, ::GetUIDRef(textModel))); CmdUtils::ProcessCommand(moveAllStoryCommand); } database->EndTransaction(); } It works fine, but when "ImportThis" is called i get this: ASSERT 'fCmdProcessorState == kDoing || fCmdProcessorState != kNotProcessing || cmdMgrRef.GetDataBase()->GetUndoSupport() == IDataBase::kNoUndoSupport' in ..\..\..\source\components\appframework\commandmgmt\CommandProcessor.cpp at line 2889 failed. Any help would be appreciated. Thanks in advance, David

I would say the problem here is in using database->BeginTransaction()/EndTransaction(). Basically you should never call these methods - you need to find/create a command to do the processing instead, then perhaps wrap the two commands in a command sequence.
I know there was a post saying ' don't use those methods' a long time ago by Ken Sadahiro (then of Adobe) - you might find it with a search, though will have been archived by now.
Ian

Soft Returns in Tagged Text

Our Pindar AgilityCMS content managment system flows text to an InDesign page using a special PlugIn.
Some characters are stored natively (store an "a", get an "a" on the page), while other special characters are stored using Tagged Text or Unicode. A return can be either <0x000D> or \u000D. This is especially useful because we can output through one of four "channels".... InDesign, Quark, HTML or as entered in the content manager. The return can now be \p in Quark or in HTML. A non-breaking space, for example, can be \u00A0 in the InDesign channel,   in HTML or <\!s> in Quark. When we insert the "special character" in the Data Editor of our content system, it might be displayed as [sp], but it will resolve correctly regardless of which channel we publish to.
The problem is that unlike Quark, Adobe does not provide for a "soft return" or forced line break. Sure, you can type one from the keyboard with shift+return, and purists will argue that you'd never want to store a soft (discretionary) return in any type of tagged text or a content management system. However, all our text is set flush left, ragged right, and we frequently want to force line breaks for readability, and do so consistently.
Instead of:
On Sale Now Buy One, Get
One Free
we always want
On Sale Now
Buy One, Get One Free
Again, this is a problem whether you store your data in simple tagged text files, or if you bring it in via a complex PlugIn, as we do.
There are many, many threads on this site and elsewhere that discuss this shortcoming. Does Adobe plan to support Soft Returns in Tagged Text with some kind of special tag?

Your question is predicated on some false assumptions, and I'm afraid Peter, Peter, and Stix didn't quite pick that up in their replies. (This gives me pause since normally they're all very detail-oriented).
As I told you when you posted in the thread from 2009, "InDesign Tagged Text supports forced line breaks just fine."
You write:
Does Adobe plan to support Soft Returns in Tagged Text with some kind of special tag?
Adobe's import mechanism does indeed support soft returns. There's no need to speculate on Adobe's plans, which is the direction the other replies went to.
With that in mind, let's move to your actual question:
Our Pindar AgilityCMS content managment system flows text to an InDesign page using a special PlugIn.
Some characters are stored natively (store an "a", get an "a" on the page), while other special characters are stored using Tagged Text or Unicode. A return can be either <0x000D> or \u000D. This is especially useful because we can output through one of four "channels".... InDesign, Quark, HTML or as entered in the content manager. The return can now be \p in Quark or in HTML. A non-breaking space, for example, can be \u00A0 in the InDesign channel,   in HTML or <\!s> in Quark. When we insert the "special character" in the Data Editor of our content system, it might be displayed as [sp], but it will resolve correctly regardless of which channel we publish to.
I think you need to address this question to your support channel for Pindar AgilityCMS. Indeed, in IDTT <000A> represents a shift-return. Here's a screenshot of a test textframe:
and when exported to InDesign Tagged Text, it produces:
<ASCII-MAC>
<Version:7><FeatureSet:InDesign-Roman><ColorTable:=<Black:COLOR:CMYK:Process:0,0,0,1>>
<DefineParaStyle:NormalParagraphStyle=<Nextstyle:NormalParagraphStyle>>
<ParaStyle:NormalParagraphStyle>Paragraph one
<ParaStyle:NormalParagraphStyle>Paragraph two<0x000A>P2/Line two
I presume you have tried <0x000A> as discussed in the prior thread.
I suppose it's remotely possible this is a Mac/PC issue, because the two operating systems do you different line break characters.
Anyhow, once again, your criticism of InDesign and Adobe is false and unfair. And if you have a problem with a 3rd party plugin, those are really the people you need to talk to.
Still, it might be wise to get it working with plain File > Place. Try testing my above IDTT file. Or exporting your own from a sample textframe like the one I used.

Need help with creating text anchors with tagged text.

Can anyone tell me how to determine the correct value for a "Hyperlink Dest Index" value?
I have a script which creates a tagged text file that specifies about about 280 pages of tables (thank heavens for autoflow) , and would like to add live links between different parts. I can create a text anchor and a hyperlink to it in InDesign. The tagged text definition for the link source is simple and in-line and exports and imports nicely as tagged text. However, I see that all the link destinations, aka text anchors, are all exported at the very end of the tagged text files as global definitions, and thier location iin the document is specified by the property HyperlinkDestIndex. However, I can't figure out how to set this value progammatically. I've spent over an hour exporting links, and it sure isn't anything as obvious as character index in the story.
Any advice appreciated,
Read Roberts

Read, I'm not sure the following is going to help you. It works for external hyperlinks, but you want internal links, right? Anyway, it might give you some clues.
A funny thing: I was reviewing some script where I got links to work, and I spotted a tiny coding error. Links seemed to be defined by two separate identifiers: a "link name", which is what appears in Edit Hyperlink dialog, and a "Dest Key", which seems to be a simple increasing number. However, due to aformentioned coding error, the dest keys between the actual link and its definition were off by '1', so there was no way that ought to have matched. But it still worked! So "Dest Key" is a red herring ...
As far as I understand, it works like this (for hyperlinks): in your text, you have
HplName -- this is actually the 'title' that appears in the Hyperlink palette
HplDest -- this is the 'internal name'
DestKey. Hm. Perhaps you could omit this, per above obsvn.
CharStyleRef, the name of the auto-applied style
Hid -- seems to be always '0'
HplOff: the "offset" from this entire command to the start of the hyperlink, in InDesign characters.
HplLen: the "length" from the hyperlinked text, in InDesign characters.
and in the list of 'proper' definitions, those that appear at the very end of your file:
HplDestDfn -- the internal name again
DestKey -- see above
HplDestUrl -- finally! A real URL! (But you must escape lots of characters, such as the forward slash and colon.)
Hid -- again, always seems to be '0'.
Some of these items are perhaps optional, but experimenting with what may be left out only lead to frustration The Tagged Text guide is far from complete, as I'm sure you already knew.
As noted, some (or all) of the named items need a backslash escape for a few characters, but I can't find a definitive way to determine in advance what is 'good' and what is 'not good'.
The following script creates a Tagged Text file with a couple of working hyperlinks in it -- I don't know if this is of any help for your internal links.
var hyperlinkDest = [];
var text = "This is some text with a link [http://www.jongware.com/idjshelp.html] and another one [http://forums.adobe.com/thread/1014617?tstart=0] in it.";
var tagtext = text.replace (/\[(.+?)\]/g, function (full, match)
 return makelink (match, 'title:'+match, match, match);
// When done processing plain text, add the destinations at the end:
tagtext += hyperlinkDest.join('');
tagFile = File(Folder.myDocuments+'/__tmp.txt');
if (tagFile.open('w') == false)
 alert ("Unable to create temporary file!");
 exit();
if (File.fs == "Windows")
 tagFile.write ("<ASCII-WIN>\n");
else
 tagFile.write ("<ASCII-MAC>\n");
tagFile.write ("<dcs:HYPERLINK=<cu:1>>\n");
 tagFile.write (tagtext);
tagFile.close();
// 'text' is the actual text that will be clickable
// 'title' is what will appear in the Hyperlinks palette
// 'name' is the internal name in the Edit Hyperlink dialog
// 'url' is the actual URL that will be linked to
function makelink (text, title, name, url)
 var destkey = hyperlinkDest.length;
 // In URL you must escape forward slashes and colons
 // .. and some other characters as well, by the way. There seems to be no list
 url = url.replace(/\//g, '\\/').replace(/:/g, '\\:');
 hyperlinkDest.push ('<HplDestDfn:=<HplDestName:'+name+'><DestKey:'+String(destkey)+'><HplDestUrl:'+url+'><Hid:0>>');
 return '<Hpl:=<HplName:'+title+'><HplDest:'+name+'><DestKey:'+String(destkey)+'><CharStyleRef:HYPERLINK><Hid:0><Brdrv:0><HplOff:0><HplLen:'+String(text.length)+'>>'+text;

Accented characters in tagged text

I normally write copy in a text editor (TextPad), paste into InDesign, and format in the Story Editor. Now I want to format in TextPad and import tagged text. But I am finding that accented characters from the numeric keypad as well as other more frequently used characters - €, £ - are being misinterpreted. For instance R$8·25 million (about €3 million) comes in as R$8Â·25 million (about â‚¬3 million) and Fundação de Amparo à Pesquisa do Estado de São Paulo is rendered as FundaÃ§Ã£o de Amparo Ã Pesquisa do Estado de SÃ£o Paulo.
I have the options to format the text file as ANSI or DOS, and I have used the headers <ASCII-WIN> and <ANSI-WIN>, but there seems to be no combination that brings the text in cleanly.
Substituting Unicode values for these characters gives me what I want and I can build a library of them to add in TextPad, but this is counter to my aim of more productivity.
Can anyone give me a the formatting options to enable me to use the numeric keypad to generate the extended character set in a form that will import as tagged text?
k

Yes, sorry, it had to be somewhere from InDesign to InDesign. What I actually meant was that your tagged text started life in InDesign. My tagged text is starting life in TextPad.
TextPad can save text in DOS (I guess that means ASCII), ANSI and UTF-8. It's possible that the text in the file I was importing wasn't actually in ANSI. I've restructured it now and it is importing accented characters correctly except, bizarrely, for the Euro symbol (yes, there is a € in the font - Myriad Pro). If I use Alt0128 to create the symbol - or the keyboard AltGr4 - import stops at the last complete line before the € would be encountered, and nothing more is imported. If I use <0x20AC> the symbol imports properly and the whole file is placed.
I also worked with two identical (except for the substitution of some Unicode characters) versions of the same file. Both were ANSI, and both were headed with <ANSI-WIN> and no other definition information. One file picked up the definitions from the InDesign decument and rendered correctly, the other ignored all the paragraph styles and simply imported text at the default paragraph style.
So please accept some points for your collection Ken for leading me to re-check the actual code set in the document.
If you have any ideas about the € problem or why one version of the file would not pick up style definitions I would be intrigued to hear.
k
As an afterthought, I've attached a chunk of each file to show one that picks up definitions and one that doesn't. My initial thought was that the one that does pick up definitions would bleat about them being missing, while the other wouldn't. But if I place them in a blank file, both complain that the definitions are missing. However, If I make an appropriately named definition to match one in the file, the version that picks up definitions will match it and only bleat about the other missing definitions. The file that isn't picking up definitions will fail to honour the paragraph style, and will complain that the remainder are missing.

InDesign Tagged Text for Cross-reference Entries

I'm transforming XML to InDesign Tagged Text. The XML has index codes. For regular page entry type entries I'm having no problem outputting to the appropriate InDesign Tagged Text markup. However, I cannot figure out how to code cross-reference type entries. The document "Using Adobe InDesign Tagged Text CS5 Tagged Text" is extremely limited in its usefulness as it does not list all possible values for tag type tags, etc. I've tried dozens of tag combos and guesses at values. None have worked. Also, for some reason, even though I can create a "See x" type reference in the InDesign document, when I export to InDesign Tagged Text to look at the code, those tags are not included in the export.
Does anyone have a more definitive list of possible IDTT index tag values?

I have been exporting various things to IDTT to see what the result would be, with nothing really helpful as a result. I'll try hyperlinks, but reading of the Adobe guide to InDesign Tagged Text and also just looking at the InDesign scripting object model leads me to believe that there must be specific tags to create index-specific cross-reference tags.

Tagging Text in a document

Hey all,
I haven't used swing in a while. Here is my problem:
A user can view a document at a time. The document is tagged with <begin><end> tags. I would like to process the document and show text between <begin><end> highlighted. The user can remove any tagged text by right clicking and clear. Also the user can add new tags by simply highlighting.
e.g.
The quick <begin>brown fox<end> jumped over the <begin>lazy dog<end>.
brown fox and lazy dog would be pre-highlighted when the doc is loaded.
Has anyone done something like this before in swing? Any help would be great to get started. Thanks.

1. <begin><end> is not proper XML and is thus a bad idea. Use <highlighted></highlighted>
2. Better yet, just use the html tags for setting the background color (check out )
user12374594 wrote:
Hey all,
I haven't used swing in a while. Here is my problem:
A user can view a document at a time. The document is tagged with <begin><end> tags. I would like to process the document and show text between <begin><end> highlighted. The user can remove any tagged text by right clicking and clear. Also the user can add new tags by simply highlighting.
e.g.
The quick <begin>brown fox<end> jumped over the <begin>lazy dog<end>.
brown fox and lazy dog would be pre-highlighted when the doc is loaded.
Has anyone done something like this before in swing? Any help would be great to get started. Thanks.Edited by: tjacobs01 on Jul 18, 2011 11:08 AM

HT201302 I am trying to import photos taken on my iPod Touch to my computer. I read the support article and when I connect my iPod the auto play dialogue box does not appear so I followed the steps to enable the behavior but my iPod is not listed. What ca

Am trying to import photos taken with my iPod touch to my windows 7 computer. When I plug in my iPod the Auto play dialogue box doesn't come up. I read the related article and tried to enable the behavior but when I go to the autoplay section and to devices the iPod does not appear in the devices menue . What can I do next? Thanks

So you tried here:
iOS: Importing personal photos and videos from iOS devices to your computer
Have you looked here:
iOS: Unable to import photos or device not recognized as a camera

Elements Organiser 10 in Windows 8 Lost the 'Imported Keyword Tag'

Using Classroom in a book (Elements 10) with Windows 8, I seem to have lost the 'Imported Keyword Tags' in the Keyword Tags Panel whilst struggling in Lesson 2, whilst trying to make sense of the Organiser,

From: jsRedpath
Sent: 01 March 2013 02:11
To: Gerryh7
Subject: - Re: Elements Organiser 10 in Windows 8 Lost the 'Imported Keyword Tag'
Adobe Community
Re: Elements Organiser 10 in Windows 8 Lost the 'Imported Keyword Tag'
created by jsRedpath in Photoshop Elements - View the full discussion
I have a similar situation. In upgrading from Elements 7 to 11 all my keyword tags are lost; both in the keyword panel and the tags on each of my imported pictures. I didn't install the Elements 11 I had a tech do it when I took my computer in for other issues, so I'm not sure of any of the specific steps taken when this was done. Any way to get these back short of "tagging" each picture again?
Reply to this message by replying to this email -or- go to the message on Adobe Community
Start a new discussion in Photoshop Elements by email or at Adobe Community

Question about the Before/After/Test metadata tags

i think that i have read all of the appropriate sections on the wiki but i am a little unclear on how/when i need to add extra info to the Before/After/Test metadata tags.
thus far, i have not done any unit tests that require a component to be added to the display list. i was reading the section on how to do that and i see that all of the above mentioned tags have extra info:
[Before( async, ui )], [After( async, ui )] and [Test( async, ui )]
what do those do and when/why do i need to use them?
thanks
additionally, i am trying to run this simple example derived from what's on the wiki and it always times out.
package HM.FO.User {
import mx.controls.Button;
import mx.events.FlexEvent;
import org.flexunit.Assert;
import org.flexunit.async.Async;
import org.fluint.uiImpersonation.UIImpersonator;
public class UserWindowPresenterTest {
//protected var window:UserWindow;
protected var button:Button;
[Before( async, ui )] public function setUp():void {
//this.window = new UserWindow();
this.button = new Button();
//Async.proceedOnEvent( this, this.window, FlexEvent.CREATION_COMPLETE, 20000 );
Async.proceedOnEvent( this, this.button, FlexEvent.CREATION_COMPLETE, 20000 );
//UIImpersonator.addChild( this.window );
UIImpersonator.addChild( this.button );
[Before( async, ui )] public function tearDown():void {
//UIImpersonator.removeChild( this.window );
//this.window = null;
UIImpersonator.removeChild( this.button );
this.button = null;
[Test( async, ui )] public function on_user_saved_clears_password_fields():void {
// this.window.pass_txt.text = "foo";
// this.window.pass_confirm_text.text = "bar";
// var presenter:UserWindowPresenter = this.window.presenter as UserWindowPresenter;
// presenter.on_user_saved( null );
// Assert.assertNull( this.window.pass_txt.text );
// Assert.assertNull( this.window.pass_confirm_text.text );
Assert.assertTrue( true );

Okay, so the async modified is used to indicate that the asynchronous statement will be used.
There is a bit of overhead adding async to tests, so, we don't actually instantiate the code that handles Async unless the async attribute is in the Before, After or Test. If you don't place the async in these tags [Test(async)] and attempt to use the async code. Async.whatever... you will get an error.
Regarding the ui, attribute, the same concept was intended to apply for ui elements... in other words we wouldn't build the necessary infrastructure.. that is an optimization and right now is not in play. so you will not see different behavior with or without the ui.
If I copy your code directly from below and paste it in my environment it passes.
Mike

Lion: Is it possible to fix the behavior of New Event in Month View?

I desperately want to be able to choose the default length of new events added while in month view.
I view iCal in Month View and I'm often adding events for next week rather than the current week. When adding a new event while in Month View, iCal assumes the event is all day long and there's no preference to change this behavior. To change the event to the length of a typical meeting, you have to:
Double click the event.
Then click EDIT.
Then click to deselect the "ALL DAY" checkbox.
Click to enter a new time for the event to start.
Then click a new time for the event to end because iCal assumes the event is 8 hours long.
If the event you're adding starts after 4PM, you're going to have to change the end DATE too, because iCal assumed the event lasted into the next day.
MY GOD! All of that, just to add a 1 hour meeting at 4:30 next Tuesday.
Sure, I could use the new + button to add an event at a specific time, but for that 4:30 meeting, iCal still assumes the meeting lasts until 12:30 the next morning, which means a ton of click click clicking to edit the event iCal got wrong in the first place.
I realize I can type out the specifics in that silly bouncy New Event "+" box... but it's annoying to have to type all of that when, previously, all I had to do was double click next Tuesday and type "Meeting with john" and set the time to 4:30.
The new iCal is infuriating. I'm especially shocked that clicking "New Event" in the menubar doesn't open a new event to edit. Instead, it opens the silly bouncy "+" box. If I wanted that, I'd have clicked in the stupid + box! I'm downright shocked by the poor UI decisions in the new iCal. I assumed this stuff would be fixed in 10.7.1. Obviously not.

Sadly, I didn't. iCal is click intensive these days unless you type everything out and get it exactly right, including some things (like which calendar) that you don't get the opportunity to set the first time.
The solution is really simple. Double Clicking on a day while in month view shouldn't create a new day-long event. It should open the gray edit event pop up box so I can create a new event with the correct info the first time (which calendar, notes, etc). The current way is to create a new event and then double click THAT to fix it.
For example: Want to create a new event using your Work calendar? Unless your Work Calendar is your default or the last calendar you used, you can't. You can only create a new event using whichever calendar pops up, and then you have to double click the event you created so you can fix it.
Using the + sign popup box for inputing using native language works when what you need to do is simple. The moment you want to create a new event that isn't dead simple, you're lost in a sea of extra useless clicks to acomplish what should be a simple task because there is no way to get it right the first time,
I'm not convinced anyone at Apple uses iCal on a Mac these days. They probably use iPads, which is why they don't realize how much of a step backward the new iCal for Mac is.

Confused by the behavior on importing simple tagged text

Similar Messages

Maybe you are looking for