Here is an even more concise version:
list: ["a" "b" "c"]
probe collect [
view [
text-list data list on-down [
keep take at face/data face/selected
if empty? face/data [unview]
]
]
]
Submitting code for improvement by the community is a good way to learn. Though, it should not replace reading in depth the existing docs. Also, asking the community questions about some language concepts or constructs is also very useful. Back in the early days in the Rebol community, we only had the mailing-list for that, and it was very helpful for everyone to ask questions and submit code. Nowadays, we have sophisticated realtime chats and online collaborative tools, so don't be shy. ;-)
One more question. How do i get the selected item? Looks simple but
not to me.
not to me.
list: ["a" "b" "c"]
print collect [
view [
text-list data list on-down [
; I need the selected item to
; store it into another text-list
keep take at face/data face/selected
if empty? face/data [unview]
]
]
]
@Rebol2Red Right, I should have used
event/picked rather than face/selected. Though, the mouse events seem to not fill event/picked, so that we need to change the event type and add some extra code to ensure that the text-list's selection does not interfere:list: ["a" "b" "c"]
probe collect [
view [
text-list data list
on-change [face/selected: none]
on-select [
keep take at face/data probe event/picked
if empty? face/data [unview]
]
]
]
I've opened a ticket for the mouse events on text-list, to see if we can improve it.
Then you can sort as each item is selected.
Taking advantage of my holidays I acquired this new T-Shirt at the corner's shop, I'm so proud of wear it this summer :smile:
Looks like a bug. Code
@henrikmk :point_up: August 8, 2017 11:40 AM There is no need to store the old selection, both old and new values are available during
select event.
@GiuseppeChillemi @pekr some improvements:
http://i.imgur.com/LZm7Vas.png
- columns can be reordered
- long text is automatically truncated
- text can be aligned to left or right
- active cell or row can be highlighted
- header
- and probably some others I forgot.
Next is keyboard navigation and editing (probably using fieldstyle, I will see).
As for editing - it is just me, so feel just easy, but I don't like in-place Excel like editing. In real-life DB apps, what I like is INS, DEL, ENTER keyboard, and entering the form to change/input new data .... just my opinion though, but if I can influence the design, please allow forbidding the in-place editing as an option ....
btw - is there going to be a vartical scroller too, if there is more than visible amount of columns? Well, beware - that might result in another request to have some columns frozen (not scrolling) at the left :-)
My final word - great work, looks good and will allow ppl to start to produce DB apps, so thanks for that!
- Vertical scroller - I'd like to avoid that as long as I can ;)
- In-place editing - actually having separate editor would be easier to do than in-place one, so I may start with separate one and add in-place later. I need to do some testing to see what is easier.
And thanks, I'm glad you like it!
as for an "editor" - it is upon the programmer, to design the form. It would be enough to allow double click, or using the keyboard navigation, plus enter event, to enter the form. I worked with many db apps in an enerprise. Grids rarely allowed to hilite the particular cell, the row was mostly enough. Also some allowed to tick the box, to select multiple rows, and then you could do some batch operations via some button, etc.
I really did not like in-place editing, as sometimes you need to do a validation against some other table, or the field triggers some other operations, etc.