Priority Queue (input needed)

[Lunake]

well it would be handy that there would be an option to upload the biggest file first after the sfv (i don't mean sorting by size )

[melter]

why would u wanna do that lunake?

if a priority queue is implemented successfully in 2.0 final, i will definately buy it.

[Shark]

Originally posted by melter


if a priority queue is implemented successfully in 2.0 final, i will definately buy it.

Well melter, as said many times throughout the forums... we are not working on new features for 2.0, as we are in a feature lock to finalise 2.0. I.e. get rid of all the bugs, etc.

So, maybe 2. something

[jslifer]

A feature along these lines would be useful for me as well and save me a lot of the time spent manually reordering the queue, which I do quite regularly.

I would be perfectly happy if SFVs were given ultimate priority and then any files or folders matching masks specified in a priority list were queued after the SFV in any order.

I think the skip list tab would be a good model for the frontend, or if you did decide to allow the user to specify the order within the priority list, you could use the highlight tab model.

JS

[StarBuG]

Now after the release of FlashFXP 2.0 Final are u planing to implement that feature in a newer build of FlashFXP 2.0?

Cause I don´t see it on ur to-do list!?

I think many many users would love to have this feature!

Greetings

StarBuG

[MidKnight]

oh yeah baby! Bring it on

[Shark]

Originally posted by 3-legged-goat
i was hoping for an added feature in the right click menu in the queue window to simply move (highlighted files) to top, or to bottom with keyboard shortcuts too, when there is 1000s of files the current click hold and drag re arrangement is not very effecient

Already an option.. ?

[dawnmaker]

Present way of file-listing sounds like carriages being hooked up to a train, sfv becomes the head when present.
Given that you want to take flashfxps limitations into account, can a changable 'list', separate for upload and download, with sfv on top, be added to X?
If not, can the present file-listing optionally prompt a second way without a major rewrite needed?
This is what I made of it after reading things above...

--------
-will the snow this year
fall again to hide white tracks
and enter wolf dreams-

[Bald0z]

bigstar, I might understand you don't want to change MUCH of code... but doing what is asked is, in a easy language like Delphi, not so time consuming also if you have to rethink about the procedure that adds .sfv files before everything else.

I did it in few hours (in Delphi), but as it is an external program it's not very nice having to reload the queue everytime (since my little proggie works on the queue file).

Your program is very nice, don't tell me a procedure like that is hard to make, please

[bigstar]

It's not hard code. It's hard for me to understand the logic of how everyone wants it to function. Also people have to understand that items are added to the list on a first come basis, it's not like specific file types are added first. that does tend to make it a bit more difficult, but not impossible.

[MidKnight]

Bigstar couldn't you make something like the skip list so we can add what ever file/extension that should be uploaded/downloaded first, second, etc

[Cre]

Originally posted by bigstar
It's not hard code. It's hard for me to understand the logic of how everyone wants it to function. Also people have to understand that items are added to the list on a first come basis, it's not like specific file types are added first. that does tend to make it a bit more difficult, but not impossible.

What i'm looking for, and i think many others too, is something like this:

A small window:

[An Add button]
[A Delete button]
[An Edit button]

Now:
Click Add - A box comes up asking for a filepattern
You add the filepattern *.nfo (clicks 'ok')
Repeat - add the filepattern *sample* (clicks 'ok')

Now.. When you queue (or transfer a huge list of files) *sample* and *.nfo gets moved to the top of the list (just like .sfv does at the moment) and transfered first.

Easy as that... Nothing more complicated is needed..

[MidKnight]

You forgot one button, and "move up" and "Move down". this why you can have what ever order of those files you want upped/downed first, second, etc

[Bald0z]

bigstar... I think your software work this way....

1. Retrieve raw list from server
2. Parse list, line by line (files are ordered by the server, so basically "random" order).
3. Put the files in the visual control, and sort by name or so.
4. Each entry in the visual control is added to the queue, one by one. If extension = ".sfv" then it goes to the top of the queue.
5. Start the transfer.

You could do a cycle, after number 4, on the queue to put things up/down, as said in the "priority list".
Probably, making it putting ".nfo" before ".txt" (for example) wouldn't be easy, but I think that it would just be enaugh that *.nfo and *.txt and *Sample* are upped before anything else, that's all, doesn't matter if *.txt is upped before *.nfo or the opposite.

Think you get it , this way... the interface how it should work it's another job, but I don't think it will be hard

[bigstar]

Originally posted by Bald0z
bigstar... I think your software work this way....

1. Retrieve raw list from server
2. Parse list, line by line (files are ordered by the server, so basically "random" order).
3. Put the files in the visual control, and sort by name or so.
4. Each entry in the visual control is added to the queue, one by one. If extension = ".sfv" then it goes to the top of the queue.
5. Start the transfer.

You could do a cycle, after number 4, on the queue to put things up/down, as said in the "priority list".
Probably, making it putting ".nfo" before ".txt" (for example) wouldn't be easy, but I think that it would just be enaugh that *.nfo and *.txt and *Sample* are upped before anything else, that's all, doesn't matter if *.txt is upped before *.nfo or the opposite.

Think you get it , this way... the interface how it should work it's another job, but I don't think it will be hard

Yup, that's exactly how it works. This would be the easiest solution. However not everyone is sold on this behavior.