Feature request: FILE | SAVE ALL and FILE | SESSIONS...

[irmlab]

A long time I thought to request it, but as it was so evident, I simply waited. :)

OK, if nobody noticed this, please, please add:

FILE menu -> SAVE ALL tabs -- (fixed bug on v. 231023_v6615185166 : unsaved tab lost after exit confirmations)

FILE menu -> SESSIONS....-> Open session | Save as session -- -- Where a [filename].session file is simply a list of .CTS pathnames to populate tabs.

---

BTW, it would be nice to add these and similar options to the TreeSheet,ini file.

SaveAllOnExit=1 -- save ALL modified Tabs on Exit WITHOUT confirmation !

SaveAskConfirmation= 0 -- do NOT ask for confirmation on exiting or closing a tab

And similar options related to Save functionnality (and to fix the save logic).

DefaultSession=c:\somefolder[filename].session
-- If empty, reopen last opened tabs. -- If defined as a *.session file, populate the tabs with .CTS paths -- If defined as a folder, open File dialog selector with *.session filter

Also please solve a probable missing option (I am unable to find how to set this) DefaultLanguage= en -- allow people to CHOOSE the GUI language

---

There are plenty of other options I would add. Also some bugs(?) to understand and fix. But I would like to (have time to) understand the code, and if able, modify it myself !:) Well, hope is human (4 years i discovered Treesheets, never found a pause :))

And I would tell to aardapel : Thanks for this precious software. It is a true jewel. Simple, functionnal and without assumptions. Thanks again ! :D)

[aardappel]

Some good suggestions, would agree "Save All" would be a nice addition, as well as an option to do that automatically on exit.

Not sure about "sessions", I can see it being useful but not sure if its worth the complexity / UI space.

[georgeraraujo]

FILE menu -> SESSIONS....-> Open session | Save as session -- -- Where a [filename].session file is simply a list of .CTS pathnames to populate tabs.

DefaultSession=c:\somefolder[filename].session -- If empty, reopen last opened tabs. -- If defined as a *.session file, populate the tabs with .CTS paths -- If defined as a folder, open File dialog selector with *.session filter

Have you tried Options > Auto reload documents to see if it does what you need?

[irmlab]

Hi aardapel, and georgearraujo, thanks for you answers

Thanks in advance for Save-All wiht ini.file options. I use TS to manage multiple files and I use a lot of "structured texts" mainly in flat text. So I have often more than 5 tabs and there was no way to save all of them.

---

About sessions, I explain the need, (but really I thought it was already evident). First, I found the (undocumented) INI file with the last opened files, I tried to generate the TreeSheet.ini on the fly with a batch file. Then by searching, I read an Aardapel's post about the -p option. After some tries, I can now simulate sessions by launching TS (located in the PATH) not from the install directory, but from the folder where the .INI file is located.

Alas, the logic of the .INI is unclear, it does not work well. I still need to rename the TreeSheet.ini and manage versions of multiple .INI files. So the answer to georgearaujo's question, is : No. the current UI does not help for what I need. With sessions, TS will quickly gain users like me: People working with structured text from multiple sources, that need to be edited on multiple tabs.

---

About UI complexity for adding Sessions, I agree to do not overload the heavy UI interface, (clearly it's the aardapel's taste. but see my next paragraph).

The solution I suggest is to add this feature as an option: With the "DefaultSession=" option in the inifile, the user will simply close and reopen TS to change the session context. Voilà !

With 3 implicit semantics: DefaultSession= -- if empty, you reopen last opened tabs, this is the current TS solution. DefaultSession=c:[somefolder]\defaultfile.session -- list of CTS pathname in some file. DefaultSession=c:[somefolder]\ -- at startup, select a session with OpenFile

In the 2nd case (userdefined session), it becomes easy to generate on the fly the session file before launching TS from a windows batch or linux shell script.

In the later case (userdefined folder), I think the logic is the same than for OpenFile function, but with with a *.session filter. All is done.

The same logic above would apply to menu OPTIONS | tmp, bak and html exports Same logic again for GUI menus for colors, shorcuts right-click items with... .INI options to hide/show the GUI items.

---

About the UI interface, it is true the current GUI is... (well)... overloaded, heavy and often illogical. Not an issue, however, if you know what to do with TS, I read Aardapel's best answer: he likes and uses the SW as-is. From the creator of Treesheets, this answer is absolutly consistent. Please, do no change you criterion ! :D)

For people with other uses, I believe the solution is simply to allow options in the .INI for most of features. This is the reason I want to compile and modify the SW. The idea is to read options before tuning the SW (if I can understand it). Of course, you need to document the options, but again the INI file itself is the solution. And by structuring the ini file with space indents, you can import/export it to TS, modify the option and... reopen TS like you do for a new session. Done !

This is also the idea of the excellent F1-Help page. :D)

Thanks again for this exchange ! TreeSheets is the "mind tool" where the mind is from User-only, and the tool is a flexible structure of flat text. No need for more. And I use it. Happy to read you.

P.S.: How do I change the UI interface language ? (Well, "DefaultLanguage=xx" option ?)

[georgeraraujo]

P.S.: How do I change the UI interface language ? (Well, "DefaultLanguage=xx" option ?)

TreeSheets does not currently allow you to change the UI language. It looks in %LOCALAPPDATA%\Programs\TreeSheets\translations for a folder that matches your system's language. If such a folder exists, TreeSheets will use the translation file therein; if it does not exist, it will display the UI in English.

[irmlab]

It looks in %LOCALAPPDATA%\Programs\TreeSheets\translations for a folder that matches your system's language. If such a folder exists, TreeSheets will use the translation file therein; if it does not exist, it will display the UI in English.

Worked ! In the no-install version, the .\translations folder is located in the "installation" (unzipped) directory. Thanks a lot, George.