You complain that my handler deletes the data, so it seems I wasn't
clear enough. Obviously there's a custom property, called "data". This
is what you use to show later parts of, or sorted stuff of, in the
field. That is why I said "less memory efficient", because there's an
additional property containing all the data. Sure, dividing the
presentation from the actual data is much more work then having both
in one, but it also gives you more control.
Again I'm not against having all the data in a field, and I never
claimed my way of doubling everything in a cprop is simpler. But no
matter if runrev agrees that your proposal is a nice thing to have or
not, it isn't available now.
Also: You need to add a "set the itemDelimiter to tab" line for my
example code to actually work.
have FUN (extra caps for extra fun)
Björnke
On 23 Feb 2008, at 23:53, Richard Gaskin wrote:
Never said it was. Not sure what that's about, unless "Ugh" is some
acronym for the European Space Agency. ;)
I just said it was inconvenient, and not the sort of thing I want to
spent time teaching, nor presumably how RunRev would like to see
potential new corporate adoptees spend their time learning.
For example:
on mouseUp
put 1 into doNotWantColumn
put 2 into sortByThisColumn
put the data of field 1 into theData
sort theData by item sortByThisColumn of each
split theData by column
delete variable theData[doNotWantColumn]
combine theData by column
put theData into field 1
end mouseUp
Obviously not as simple as not showing a column in the field, and
less memory efficient too, but on the plus side this is available
now, and most likely faster then a modified field object
(everything that has to do with fields is slow).
But moreover, your handler does something so very different from the
example I gave above that I'm not sure how it's relevant here. While
three of us have explained the value of preserving data and just
hiding it from display, if I read your handler correctly it
completely deletes the column altogether.
For performance and convenience, compare your handler to what I and
the
others here are proposing with zero-width columns:
on mouseUp
sort lines of field 1 by item 2 of each
end mouseUp
--
official ChatRev page:
http://chatrev.bjoernke.com
Chat with other RunRev developers:
go stack URL "http://homepage.mac.com/bvg/chatrev1.3.rev";
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
