OK, I'll try them.
However, the "\n" I used didn't work.
outTE.AppendText("Hello World !\n")
outTE.AppendText("Nice to meet you !")
The output on the text edit shows "Hello World ! Nice to meet you !"
But when I use "\r\n", it works!
Yes, the word should be "button", not "bottom".
Thanks for your
Hello everyone:
I've finished studying https://github.com/lxn/walk/tree/master/examples.
However, there is still a problem that I'm encountering:
Is there any examples about tree diagram with buttons for references?
Ex: When we install software, there are multiple choices for users to
choose,
Hello everyone:
I've finished studying https://github.com/lxn/walk/tree/master/examples.
However, there are some problems that I'm encountering:
1. I want to print the message after clicking the "Confirm" button, but I
have no idea how to implement it. Here is the incompleted code:
salam. Hi gophers can any one take a look at at this snippet of code
https://play.golang.org/p/qv0N0EN81tX
and answer me why should this panic at runtime, and why the compiler
does not catch this kind of mistakes.
--
You received this message because you are subscribed to the Google Groups
I'm working through the most excellent book "Concurrency in Go", doing the
example on page 162-166. My code is here:
https://play.golang.org/p/7kokkAIdhov
The program is not triggering the timeout section of the code (lines
103-103 in the playground code).
All of the other examples have
Your not checking done in your for loop.
On 14/10/2019 13:39, Jeff Kayser wrote:
I'm working through the most excellent book "Concurrency in Go", doing
the example on page 162-166. My code is here:
https://play.golang.org/p/7kokkAIdhov
The program is not triggering the timeout section of
On Monday, October 14, 2019 at 5:53:23 AM UTC-7, Jeff Kayser wrote:
>
> I'm working through the most excellent book "Concurrency in Go", doing the
> example on page 162-166. My code is here:
>
> https://play.golang.org/p/7kokkAIdhov
>
> The program is not triggering the timeout section of the
On Mon, Oct 14, 2019 at 5:53 AM wrote:
>
> salam. Hi gophers can any one take a look at at this snippet of code
> https://play.golang.org/p/qv0N0EN81tX
> and answer me why should this panic at runtime, and why the compiler
> does not catch this kind of mistakes.
I assume that you are asking why
