Hello guys,

I'm new at the forum, I'm using DekoCast version 4.1 Build 28

and I'm communicating with it usind Java and TCP/IP Socket and controlling the scene using XML Commands

and I have done so many projects and live games, but sometimes DekoCast application hangs, and gives a windows error "DekoCast has caused an error and it has to close, Report this problem to Microsoft", I think all of you know this error message.

so I want to be able to save the scene using XML commands,

the RocketEngineBCI.pdf contains all the xml commands including the following:

<scene><set>
          This command sets properties of the selected scene(s).
Valid subtags:
<name>            Property The full path name under which the selected scene(s) should be saved.

I tried the following:

<cmd>
  <scene>
    <set>
      <name>C:\DekoCast\samples\XML\XML Sender\Elements\SimpleDeko.dkc</name>
    </set>
  </scene>
</cmd>

and gave the following error

<reply>
  <error>Unrecognized tag: name</error>
</reply>

can anybody help me with this? I want to save the scene using XML Commands,

Best Regards

Ther is no <Set> tag for a scene.

Valid sub tags at the scene level are listed on page 15 of the document

<object>

<action>

<name>

<add>

<remove>

<show>

<showex>

<hide>

-Lou Garvin

Thank you very much for your reply,

But I didn't invint this <set> tag was demonstrated in the Dekocast manuals,

anyway, I need a way to save the scene automatically using xml tag commands,

anyone can help?

I'm not sure if this will actually save the scene, but the error message you are getting is most likely because the scene name must have an extension of .dkx. Prior to the 4.0 release the .dkc extension was used. After 4.0 the .dkc can be read, but only .dkx files can be written to. Try changing your scene name to .dkx.

I tried to save it as dkx and it didn't work, thanx

u know the problem is that it's in the Dekocast manual, how can they write anything in the manual and it doesn't work?!

Ok, I was able to give this a try. I tried:

<cmd>
  <scene>
    <set>
      <name>D:\Crawls\test.dkx</name>
    </set>
  </scene>
</cmd>

And I got a </reply>. But I did not have any scenes open on the DekoCast and essentially nothing happened. If I first entered an <add><name>D:\Crawls\crawl.dkx</name></add> and the scene opened ok, if I then entered the above sequence, I got the "Unrecognized ..." error.

But I'm not sure what I think should have happened. Are you trying to create and save a scene or are you trying open one scene and then save it as another?

Let me know exactly what you are expecting to happen and I will enter a bug report. It does appear to be a bug of some kind, but I need a little bit more info.

Thanx man for your kind response,

Actually I design interactive TV games, but sometimes DekoCast crashes, and gives a system error, so I have to stop it and run it again, so the last status of the game will be lost, and the player will have to play from begining, because the scene will be opened as it was initially,

But I thought if I saved the opened scene each time I send a command, the status of the game will be saved, and the player will only have to wait a few seconds until we re-run DekoCast.

so the Answer to your question is that I'm trying to open the scene and saving it as another or in the same name, there's no differece, either ways works fine with me.

Regards,

I've discussed this with the engineering team and the <set> command does not actually save the scene (as we've already figured out). But they do suggest that you could do something like sending:

<cmd><query><scene><id/><name/><coordinates/><instance/><sceneparams/><userparams/><object><id/><name/><fullname/><type/><param><name/><id/><value/><fullname/></param></object></scene></query></cmd>

Which will generate a reply of the entire scene at that point. You could then use the MS XML Parser to Save the reply in an .xml file.

Also, since DekoCast is aborting on you, that in itself is a bug. Please call our helpline at (800)NEWS-DNG or (800)639-7364 and then use Options 1, then 5 and then 1 to log a call. If you have a method for reproducing the failure, it will help us isolate the bug.

Dave