If i understand correctly, here are 3 ways of doing it.
way 1 and 2 are very similar. way 3 has the least objects but its as clumsy as it gets.
output is exactly the same. i used defer low for the button for triggering lookups so it triggers the lookup only after the new value is stored in zl.lookup. You could do with with proper message ordering (putting button most left and bottom if i recall) but I'm a lazy man and I never remember how to properly order messages.
basically, zl.lookup does the "nth element of the list".
You can use zl.iter after zl.lookup to output 4 successive lists instead of 4 parallel lists for inputting to i.e. database object. (coll, pattr)
yes thanks. i think im going to use the packunpack method. that must be the least heavy way to handle this.
this is just a small piece of a thing im working on. Ive got a HUGE list and a very big patch and used the slice method first a couple of months ago but now I need to rewrite the patch cause the slice method was to heavy combined with a lot of other things. so need to slim things down.
thanks for all inputs!!!
Ill make a new thread with the nth and mth question
yeah right i am wrong, my solution would require a buddy or zl nth or something like that after the iter ... and then it is too many objects already ... at least not less than using unpack and pack (which would have been my aim)