[Qing]

Thanks for reply Derek.
It is really tough to figure out the right time and way to release all the com objects, and the web service interaction makes it even more tough.
So I just want to simplify it to see if there is any way to disable the document change macro when close the xmetal with multiple docs open. Is there any way to achieve this?
And I find a most simple way is the API Application.Quit(1) at the end of On_Application_Close macro and after the necessary release work.But, does this method secure?

Reply

[Qing]

Any one there? There question is so weird or I didn't make it clear?

Reply

[Qing]

Thank you Derek for the detailed reply.
What I am trying to do is not to display an element as an image, I just modify the sample to file to figure that how XMetal treats empty element.

I new an element named br and set the corresponding css file to make it display:block. And in this way, attempt to produce a line break when the br element is inserted into a document.
But, when the element shows like
in tags-on view, the cursor will be put inside the element after the insert behavior, and content will be inserted directly if the cursor is not moved out which cannot be done in normal view. The content inside an element acting as a line break is of no use.

Then, after some transformation, we finally make an empty element
, XMetal shows a blue diamond in both tags-on view and normal view. which is a little weird.

Does XMetal just does not support line break inside a paragraph or empty element? I mean XMetal Authoring Enterprise 7.0.

Reply

[Qing]

Sorry for lacking detailed information.
I have my own schema file, and define an element, name br, and do some transformation to make it appears like
in plain test view instead of
,but I am getting something like this(figure 1), then I go to the sample file: Journalist, when I removing its attributes fileref, then it appears like this(phigure 2).

I am using xmetal authoring enterprise 7.0.

Reply

[Qing]

Thank you Derek.
I may didn't describe my question clearly. My question is not how to disable the buttons, but to enable them.

The DisableMacro disable the buttons in the beginning for they are enable in default, and when I want to enable them, I attempt to use PushInMacro, but the reality is that PushInMacro seems not enable them. So my confusion is how to enable the button when I want to?
The handle macro of a button just do some binding the OnButtonClick, like this: OnButtonClick(controlId).

Thank you very much.

Reply

[Qing]

Thanks you Derek. This explains a lot. I am using XMetal Author Essential.
Actually my confusion comes from some unclear, or may wrong code. A opened document is not disposed when close it. Then when reopen it, only the macro On_Document_Activate is fired and On_Document_Open_Complete never runs, but, after I change the code to dispose the document when close it, the On_Document_Open_Complete runs after On_Document_Activate.  So I am wondering if some conditions exist.

Plus anther question, We customize the Command bar to add some other buttons, and according to the state the document to decide the enable the button or not, but it seems that the effect is not shown until mouse click. It makes sense in some situations, but some others not. Is there any API to refresh the command bar? I scanned the programmer's guide but no such API was found.

Appreciate you time and thank you very much.

Reply

[Author]

Posts