ts4242 wrote:versalzen wrote:how/where can i set your neat program to run tc with the correct wincmd.ini ?
If you run the program from inside TC, it should always find the correct wincmd.ini because it get it from %Commander_INI% variable
probably you didn't find changes you have already made after restarting TC because the menu you are editing isn't the menu used by TC
i start the menu editor from inside tc.
wincmd.ini
Code: Select all
menu178=Main Menu Editor
cmd178=Main Menu Editor.exe
path178=%COMMANDER_PATH%\exe\ultra tc editors\
changes are applied and correct, after i start tc with the correct wincmd.ini from my .lnk file, or
if i use
TC Plugins Manager to restart tc, after i made changes with your menu editor.
TC Plugins Manager restarts tc correctly. your program did'nt. so there must be any other kind of problem where i can assist you to solve? what do you need to know from my system? what could be the problem now?
ts4242 wrote:
versalzen wrote:
now, i'm looking for a way to reload the file (the data inside usercmd.ini, actually) inside your neat program
for speed issue Totalcmd.inc, usercmd.ini and wcmd_xxx.ini are loaded only at startup so the program must be restarted to reload them
aha, but speed issue should only be important at startup. not, while the user wants to update a file inside menu editor.
if the options is: restart program, or wait a short amount of time, then the option should be: wait a short amount of time, but not restart the program. also, if restarting the main editor, this takes more time and clicks than just reload an .ini.
this is, my opinion, of course.
what do others think of that?
Was nützt der Löffel für die Weisheit, wenn man zu weit vom Suppentopf entfernt sitzt?
Mario