Jump to content
  • Announcements

    • Rahul Ponginan

      Please click here for a short but important announcement   03/26/17

      Dear Users Our Commercial and Academic users around the world can use these same forums here as before i.e. the Altair Support Forum , Commercial users from India with solver queries can go to the Solver Forum for India Commercial Users , Academic Users from India and AOC India Participants are requested to go to the Forum for India Academic Users and AOC India Participants , We will be tending to all queries in all the forums promptly as before, thank you for your understanding. 

Recommended Posts

I don't think command recorder is anymore needed. For Altair Hypermesh 14 and above command.tcl saved in working directory (mostly in Documents) does the needed job. 

Share this post


Link to post
Share on other sites
14 hours ago, Q.Nguyen-Dai said:

Which version of Hypermesh do you use?

"command.cmf" is OLD release.

HI

I use version 2017

Share this post


Link to post
Share on other sites
7 hours ago, Livil Lyle said:

I don't think command recorder is anymore needed. For Altair Hypermesh 14 and above command.tcl saved in working directory (mostly in Documents) does the needed job. 

Hello

Could u please tell me more about that! Does it means every command in HM saved after we save that file?

Share this post


Link to post
Share on other sites
1 minute ago, pohan said:

Hello

Could u please tell me more about that! Does it means every command in HM saved after we save that file?

 

Hi, 
It keeps a track of all the operations you're doing in HM. It saves automatically in background. 

pohan likes this

Share this post


Link to post
Share on other sites

Thank you Livil Lyle

In my opinion, sometimes if we want to focus on some specific commands may be command recorder is better.

Share this post


Link to post
Share on other sites

It is not a problem with me. I usually delete command.cmf before I focus on a certain command.

the recorder is actually unnecessary

if i want to track it, I will set a tracer

pohan likes this

Share this post


Link to post
Share on other sites

Hello

I create my first tcl/tk script file with the syntax like that

*startnotehistorystate {Deleted Components}
*createmark components 1 " RW_left" " RW_right" "Compresseur"
*clearmark components 1
*createmark components 1 " RW_left" " RW_right" "Compresseur"
*deletemark components 1
*endnotehistorystate {Deleted Components}

in order to delete component " RW_left" " RW_right" "Compresseur" in my model.

But when I run the tcl/tk script file it did not work.

Could you please give me some suggestions?

Thanks

Share this post


Link to post
Share on other sites

Hi

try removing space in front of comp names

you have excessive createmark and clearmark commands at line 2 & 3, they are unnecessary.

pohan likes this

Share this post


Link to post
Share on other sites
1 hour ago, tinh said:

Hi

try removing space in front of comp names

you have excessive createmark and clearmark commands at line 2 & 3, they are unnecessary.

Hi

I tried but It said that

invalid command name "*startnotehistorystate"
invalid command name "*startnotehistorystate"
    while executing
"*startnotehistorystate {Deleted Components}"
    (file "D:/Dropbox/Lille/Altair/TCL/Hoan/command03_15_delcomp.tcl" line 1)
    invoked from within
"source {D:/Dropbox/Lille/Altair/TCL/Hoan/command03_15_delcomp.tcl}"
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 "source {$file}""
    (procedure "::HM_Framework::p_FileLoad" line 68)
    invoked from within
"::HM_Framework::p_FileLoad 24"
    (menu invoke)

Share this post


Link to post
Share on other sites

Hi Pohan, 

You don't need startnotehistorystate and end endnotehistorystate. All you have to do is:
 

*createmark components 1 "RW_left" "RW_right" "Compresseur"
*deletemark components 1
pohan likes this

Share this post


Link to post
Share on other sites

Hi Tinh and Livil

Thank you very much. It worked with two rows.

I think  startnotehistorystate and end endnotehistorystate are for undo.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×