… so in principle not something you couldn’t recover from using eval().

About compiled app:
After compilation, there’s the *.exe
-> myfun.exe
I’ve associate my extension file with the executable (Step 1).
When I open the file, myfun.exe is launched with one input arg: the path and file. It’s the same as %1 in dde.

So, with a little adaptation, it’s easy to launch the file:

function  myfun(args)
   if nargin==1 && exist(args{1},'file')==2
      launch_file(args{1})
      return;
   end
end

This code is ok for guis.

I also wanted to explore multiselect open, but it seem a little bit more tricky: a multiselect on files then open just launch n-times the single file opening instruction.

Thx,

Since last time i’ve made a script that manage all my DDE file association (initializatiojn by writing in the registry (even file icon) and open , plot of file)

I’m certain i’ve read somewhere that compiled scripts and gui cannot have input argument.
So i’m not quite sure how to use DDE.
I’ll try and post after.

I’ll also try mulitselection.

@Pooh – I do not know how DDE behaves in a compiled application. I suspect that since MCR uses the same Matlab engine as the interactive application, DDE will also work with MCR, but I do not know. The easiest way to find out is to simply try it out (don’t worry – it will not explode in your face…)

Thanks a lot for this feature, It works well and will save me a lot of time (changing working directory, specify the file to open).

I’ve a question about compiled matlab application : is it possible to call DDE with a matlab compiled app (MCR) ?

I’ve a gui that read and process files and i deploy this gui in a compiled version. The non-compiled version can now open files directly from windows explorer (thx to this post). How can i do it with the compiled version if this is possible ?

Thx a lot