dockimbel on interp-events
FEAT: preliminary work on instr… (compare)
greggirwin on master
FIX: removed dead code FIX: \\\uXXXX sequences are now… FEAT: 4x speedup by using parse… and 4 more (compare)
test2function, I have set
m: 1,why the print is
122after second recursion
m: "1" binds the word in the local context of the function to a string value whose initial content is "1". Assume that the "address" of the string is str-1234. 'm: 1' binds 'm' to str-1234.
m: append m "2" binds
m to the value returned by
append which is the value 'm' is bound to (i.e. str-1234) with "2" appended to it.
Next time, the function is called; 'm: "1"' still binds 'm' to str-1234 which now contains "12".
Compilation Error: unknown directive macro
event/pickedis described in
event!section. Though, in a User Manual, we should put all those information together for easier reading.
@dockimbel That still doesn't provide the necessary information where it's needed, in the ON-CHANGE actor. So either ON-CHANGE is worthless or it can only be used in specific circumstances, which the application author must be aware of.
If I were you, I'd get rid of the ON-CHANGE actor, because it doesn't easily describe what change has happened to the widget and who did it. Go with ON-SELECT which is specific enough, along with providing OLD-SELECTION and SELECTION words for the application author to work with.
The GUI needs to be luxurious about what it provides to application authors, because this is where the nitty gritty of debugging happens, and it might as well be provided and debugged by the GUI once, so each application author doesn't have to write and debug their own code for it.