@nedzadarek if you'd read original error message more carefully, you'd noticed that
get-word! evaluates correctly, but Rebol fails to interpret lit-word! as a valid selector. Red in this case correctly coerces all any-word! values. So, no, problem is not with get-word!, problem is with lit-word! (or any other possible any-word! value) to which it evaluates. Same holds for paren! expressions - they are not selectors, but the result of their evaluation is.
@9214
** Script Error: Invalid path value: a
** Near: probe arr/:indYes, it seems that get-word! evaluates correctly but it seems that we cannot use word! as path's value. "invalid path value: a" - I assume that a is a word! here... but it can be lit-word! as well. In my opinion that error message is not as clean as you said.
Putting that aside, this answer fully explain differences. Thank you for this.
I'm sure you had to overcome that?
Brilliant! The Red console is running. Just ran my first line of code in it
on binary of course
because Red does the conversion automatically based on your platform
replace/all read/binary file crlf lf
How do you deal with time-consuming computation in the gui?
make-random-image: has [img ] [
img: make image! 200x200
forall img [img/1: random 255.255.255]
wait 2 img
]
view [i: image [i/image: make-random-image]]Let's suppose that make-random-image just takes at least 2 seconds to compute. In those 2 seconds I'm left with unresponsive window. Is there anything I can do to make user experience better such in cases?
ps. I know about memoization and I'm not sure if I can translate this part of code to Red/System.
@nedzadarek using
call.- start another process using
call "red my-heavy-script.red"that will write result to some file - start timer and in
on-timecheck periodically if second process finished (result file exists, or something like that) - if it does, stop timer, read the result and present it to the user
?
@rebolek
While Red is single threaded, blocking needs creative handling. For a wait of a couple seconds, I might just put up a window, like we did in the old days. I mean, how much work can the user do in 2 seconds, and how much effort or other issues might come up by letting them mess around during that time. This will hold true even once Red has concurrency.
@toomasv I want to convert treeview to a 2-D view something like this:
https://i.imgur.com/37TOgyX.png
Is there something like collapsible panel instead of static group-box/panel ?
https://i.imgur.com/37TOgyX.png
Is there something like collapsible panel instead of static group-box/panel ?
window: [
title "Layout"
size 800x800
group-box "01-file-header" 780x50 [
panel
]
return
group-box "02-bookmarks" 780x600 [
panel [
group-box "01.init-variables" 740x70 [
panel [
text {.url-0: >url}
]
]
return
group-box "02.reload-favorites" 740x70 [
panel [
text {.reload-favorites}
]
]
return
group-box "04.add-bookmark.sub-function" 740x70 [
panel [
text {.add-readable favorites 'bookmarks reduce [>url]}
]
]
return
group-box "05.either-block-url" 740x400 [
panel [
group-box "true" 350x400 [
panel
]
group-box "false" 350x400[
panel
]
]
]
]
]
]
view window
Is there some limit in VID nested levels ? I get stackoverflow if I add an area inside the last nested groups:
https://i.imgur.com/fbFnbzk.png
https://i.imgur.com/fbFnbzk.png
Red [
Title: ""
]
file-header: [
]
init-variables: [
]
bookmarks: [
groupbox [
panel init-variables
]
]
window: [
title "Layout"
size 1200x800
group-box "01-file-header" 1000x50 [
panel
]
return
group-box "02-bookmarks" 1150x600 [
panel [
group-box "01.init-variables" 740x80 [
panel [
area 500x40 {.url-0: >url}
]
]
return
group-box "02.reload-favorites" 740x80 [
panel [
area 500x40 {.reload-favorites}
]
]
return
group-box "04.add-bookmark.sub-function" 740x80 [
panel [
area 500x40 {.add-readable favorites 'bookmarks reduce [>url]}
]
]
return
group-box "05.either-block-url" 1100x400 [
panel [
group-box "01.is-block.url.true" 800x400 [
panel [
group-box "01.is-category.first-word.true" 330x400 [
panel [
area "stackoverflow !!!!!!"
]
]
group-box "01.is-category.first-word.false" 330x400 [
panel
]
]
]
group-box "01.is-block.url.false" 500x400 [
panel [
area {.add-readable favorites 'bookmarks (>url)} wrap
]
]
]
]
]
]
]
view window
@greggirwin ok thanks, maybe it's because vscode points to this version of red, will have to change I guess:
console-2017-8-3-49893.exe Internal Error: stack overflow Where: srs Stack: view layout layout layout layout layout layout layout layout layout eval-set-path empty?
console-2017-8-3-49893.exe Internal Error: stack overflow Where: srs Stack: view layout layout layout layout layout layout layout layout layout eval-set-path empty?
@nedzadarek ok I didn't know tab-panel, I'll try thanks.
@greggirwin under October build, I can go further but it still crashes in the end :)
@greggirwin under October build, I can go further but it still crashes in the end :)
Red [
Title: ""
]
window: [
title "Layout"
size 1200x800
group-box "01-file-header" 1000x50 [
panel
]
return
group-box "02-bookmarks" 1150x600 [
panel [
group-box "01.init-variables" 740x80 [
panel [
area 500x40 {.url-0: >url}
]
]
return
group-box "02.reload-favorites" 740x80 [
panel [
area 500x40 {.reload-favorites}
]
]
return
group-box "04.add-bookmark.sub-function" 740x80 [
panel [
area 500x40 {.add-readable favorites 'bookmarks reduce [>url]}
]
]
return
group-box "05.either-block-url" 1100x400 [
panel [
group-box "01.is-block.url.true" 800x400 [
panel [
group-box "01.is-category.first-word.true" 430x400 [
panel [
area wrap {favorite-bookmarks: favorites/bookmarks
existing-category: select (favorite-bookmarks) (category)}
group-box "01" [
panel [
area {crash under october build}
]
]
group-box "02" [
]
]
]
group-box "02.is-category.first-word.false" 230x400 [
panel [
area wrap {.add-readable favorites 'bookmarks reduce [>url]}
]
]
]
]
group-box "02.is-block.url.false" 500x400 [
panel [
area wrap {.add-readable favorites 'bookmarks (>url)} wrap
]
]
]
]
]
]
]
view window