some change I would like to have in the new GUI

[ntkntk]

If it is feasible and not require too much work, I would like to see the features:

1/ the send command line should accept multi lines

2/ send command line should link to a buffer so you can recall commands you have tested there recently

3/ would be convenient when you are in a small experiment, the command buffer could be quietly reloaded with each restart of the GUI. I know, the other way to do is write a la lua script but many user can not program lua, yet they do experiment on commandline-interface

4/ instead of displaying text when loading setting.xml it should only display a progressing bar indicator, possibly start up time is shorter, (currently it loads and displays text, I don't know what for, it is too fast to read and too slow for the operator who wants to quickly access commands, not reading text he would not understand or does not see any benefit

5/ multi-pages on e for HF one for LF one for extra tools

6/ the list of commands going already longer and loner ... a sorting order or a way to index would be great

[0xFFFF]

1/ For what purpose? Sending multiple commands? Please elaborate.
2/ Please create a separate issue for this.
3/ ?
4/ ? Possibly a non-existent issue.
5/ ?
6/ The commands are organised in a tree view just like the original Gaucho GUI. The order of appearance is determined by pm3Commands.xml

[iceman1001]

5. maybe a search function, which searches the treeview and highlight the cmd.

First step is to get the old code working in C#. I never use this GUI, and if I ask myself what would make me want to start using a gui I come up with to following. Maybe if there is a nice way of bin-diff between dumps in the gui. Since I'm fast in running commands in the client, I also think if the GUI is to be interesting it needs to be fast in usage. ie, I don't want to expand and seach in the treeview to find commands. the textbox for running customcommands must be "enchanced" somehow. Maybe a history like @ntkntk suggest. Not sure.

[ntkntk]

to 1/
I can not exactly explain yet why I would like to see in PM3 GUI. I think developer should design ergonomic, to user's convenience in mind. Every terminal xterminal, python, perl, DOS terminal allows multi line commands ... unless there is a clear reason i would not limit this ability by default

often we do thing in multi line mode without thinking. When do lf sea, it should read, decode when possible, and display plot too. When recompile, we do "make clean all flash-os" or even flash-all... not one task then next task.

[iceman1001]

but we don't run "make clean && make all" from inside the GUI nor do we flash the device.

The flash process is possible but compiling demands a full dev-environment.

[ntkntk]

only an unfortunated chosen example iceman. I am not using multi lines feature for compiling or flashing . I mean a lot of things we don't do in only one step one consequence out mind is far ahead when we do something, think we expecting, thing we look out for etc..

for example yo do reading, you think already of plot of decoding AM but perhaps fsk mode, when it works why not print out hex data, and save in a file name xyz1.pm, When I repat the experiment with an other tag, this time I would do similar step but I know I don't need to try several mode: I need rawdemode fsk , and save under xyz2.pm3. it is a lot easier with multi line is nit not?

a single line feature would stop the flow of thinking...

and the plain nature of terminal allowing buffering, accepting multi line, pipeing without any difficulty, when implement it in a GUI why don't think that way, but provide a limited,

[ntkntk]

Only for a certain work work you wish GUI provides special feature, such of those while you clone why you read EM tag or read the password out of a plot you would laugh what the hell should I provide that feature. But, like in the last few days while checking and updating the pm3commands file (or settings.xml file), there is no fun when I implement a new part, to check it I have to switch off GUI then open it again, the part of the commands tree now disappears, you again chose tree view, scroll down, click and click and click to go down to that sub-level to check for the part you are working on ... there is no fun.

At time I wish there is a button you press and it would try to read the settings file, refresh the window pan of command tree view etc or at least when I have to shut GUI and restart please GUI re-opens and automatically bring me to the part where i am doing work lastly. kind of a "service/maintenance mode"

I wish we have a switch in the SW for allow that special feature while I am updating, checking. modify the setting.xml