Or a warning if you have selected a large number of files. Remember that sequential would lock up the lister until you have checked all files, which might be a bit .. annoying.
personnaly I'm not for sequential : if I multi-select files and then click on view then I want them to be viewed simultaneously. I would rather prefer your solution : a warning. Anyway it can very well be 'sequential' and done by a sub-process to not block the lister
yeah, but creating processes internally, as apposed to systemtags(), is not very fun when using newlib and I don't want to explode the file size by skipping newlib.
Unless of course I create 'yet-another-binary' that just launches the sequential list, but I don't want to add a lot of helper apps either.
You don't use systemtags to create new processes internally. You use CreateNewProcTags().
Which afaik requires that you use NP_Child when using newlib. or else the newlib base is deallocated when the parent process quits (it is shared) which can lead to that the child processes takes a hard dive into grimgrimland. Also you must be very careful to not share any data between the processes, ie. need to reload all libraries and interfaces that you might need, or else you might deallocate something that the child processes are using.
But I don't want to use NP_Child since that means that the parent process doesn't quit until all sub processes have quit.
I guess you could open a new newlib but then you're venturing into something that doesn't seem like it's really worth the hassle.
All in all it seems easier to simply just add a warning.
I think I misunderstood you. I have my own problems to get CreateNewProcTags() to work in my app. (Called function itself works but system becomes highly unstable afterwards. I dont' know where the problem is. Maybe it's not intended to work that way I'm doing it.)
If you want to launch apps from user buttons like they were started from WB you can use OpenWorkbenchObject() on AOS4.1. (AFAIK that function didn't work properly in 4.0. I'm using SystemTags("WBRun <appname>",...) if it's running on 4.0.)
Rock lobster bit me - so I'm here forever X1000 + AmigaOS 4.1 FE "Anyone can build a fast CPU. The trick is to build a fast system." - Seymour Cray
This project is very nice! Great to see it reach beta-stage! :) Congratulations!
btw - would it be possible to add an option to let the user change the text "set destination" and "set source" - Myself I prefer to simply have "Source" on the lister that is the source, and "destination" on the lister that is the destination.
btw - would it be possible to add an option to let the user change the text "set destination" and "set source" - Myself I prefer to simply have "Source" on the lister that is the source, and "destination" on the lister that is the destination.
I did find that slightly confusing to look at myself at first. Now I have source and destinations set with differeing colour schemes, so it's obvious at a quick glance with is which.
Tested right now 53.21 version, want to say its looks like good professional programm at moment! Tiny, stable, fast. After running i just tryed add filetypes for videos (avi, wmv, mpeg). And its much easest and logical if for example compare with old dopus4. Just curios, it is possible to redirect filler output to NUL ? i just tryed somethink like: run <>NIL: mplayer "{f}", but i have this annoing mplayer shell output still.