On Tuesday, 12 March 2019 at 14:44:59 UTC, Ron Tarrant wrote:
> another post on the gtkDcoding blog.

0013 says
> ... with *setTooltipText()*.
Maybe a formatting error?

Thanks again for the Blog.
FYI: I also had dropped a note in some of the previous gtkdcoding forum threads

On Thursday, 21 March 2019 at 20:49:07 UTC, number wrote:
> On Tuesday, 12 March 2019 at 14:44:59 UTC, Ron Tarrant wrote:
>> another post on the gtkDcoding blog.
>
> 0010 says
>> Here’s the code file.
>> Here’s a second code file for you.
>
> but no links. I guess it's
> https://github.com/rontarrant/gtkDcoding/blob/master/003_box/box_003_03_checkbutton.d
> and
> https://github.com/rontarrant/gtkDcoding/blob/master/003_box/box_003_04_togglebutton.d

Hmm... I'm not sure why the links didn't show up for you. I just double-checked and they're in the .md file and version of the file has been in place for at least 10 days.

Still, no harm in having them on this forum as well.

Thanks for taking an interest.

On Friday, 22 March 2019 at 10:02:24 UTC, number wrote:
> On Tuesday, 12 March 2019 at 14:44:59 UTC, Ron Tarrant wrote:
>> another post on the gtkDcoding blog.
>
> 0013 says
>> ... with *setTooltipText()*.
> Maybe a formatting error?

Yup, it was. I'm still trying to break the habit of putting optional stuff in angle brackets, '<' and '>,' which markdown doesn't like. Thanks for catching that.

> Thanks again for the Blog.

I'm delighted anybody's reading it. :)

> FYI: I also had dropped a note in some of the previous gtkdcoding forum threads

I'll have a look. Sorry I missed your remarks.

On Thursday, 21 March 2019 at 21:34:26 UTC, Michelle Long wrote:

> I'd suggest adding pictures! It's very easy to take a screen shot and not much harder to link them and they offer far more interest.

You're the second person to suggest this, so I'll explain my reasoning. I assure you, it's not because I'm lazy or don't know where the Print Screen button is. :)

My original plan was to include screenshots. Then I thought back over my own experiences with reading tutorial sites. I have a tendency to look at the screenshot, skim the article, copy-n-paste the code, and go off to do other things. I've also noticed this in others. It's often quite obvious someone hasn't read something carefully just by the questions they ask (present company excluded).

And I think images deter people from paying close attention while reading. I can't back this up with statistics or research other than my own, but I have noticed a decline in reading comprehension over the last 30 years as the Internet went from text-only to images and ads filling our screens.

So the bottom line is, by leaving out images, I feel I'm doing my bit for literacy. If there's nothing else besides text, it's all the reader has to engage with and I'm hoping this will engender a complete understanding of the subjects I cover... as much as is possible.

It's also why I keep the frills down to an absolute minimum. I've tossed thousands of words because they veered too far off topic or were written just to get a laugh or whatever.

And there you have it, the philosophy behind gtkDcoding.

Thanks for reading, Michelle. And keep the comments coming, please.

On Thursday, 21 March 2019 at 21:34:26 UTC, Michelle Long wrote:

> I'd suggest adding pictures!

Oops! Forgot to say...

I get why you want images. You were asking about animation the other day, so obviously you're a visual artist. So am I and I know how drawn I am to imagery and I imagine most artists are.

Again, thanks for your feedback, Michelle.

Also forgot...

It's Friday again and time for another gtkDcoding blog post. In today's episode, we slap an image onto a Timmy the Button's face, then do a switch up to keep poor Timmy off balance. You can tune in here:

http://gtkdcoding.com/2019/03/22/0020-image-buttons.html

On Friday, 22 March 2019 at 11:19:56 UTC, Ron Tarrant wrote:
> Hmm... I'm not sure why the links didn't show up for you. I just double-checked and they're in the .md file and version of the file has been in place for at least 10 days.
>
> Still, no harm in having them on this forum as well.
>
> Thanks for taking an interest.

Not sure about .md or file version, but there are no links in the actual blog post:
http://gtkdcoding.com/2019/02/15/0010-checkbutton.html
and apparently also not in in this .md file:
https://raw.githubusercontent.com/rontarrant/gtkDcoding/master/docs/_posts/2019-02-15-0010-checkbutton.md

On Tuesday, 12 March 2019 at 14:44:59 UTC, Ron Tarrant wrote:
> 

As a side note, in 0004 you say:
> We can still call the constructor, even though strictly speaking it’s private, because by using ‘new MyButton()’ the constructor isn’t being called directly, but as part of a lower-level process for instantiating the object.

I'm still new to D too, but I think it works in this scenario because private in D works on the module/file level. main/TestRigWindow/MyButton are defined in the same file (module) and thus can access each others private members. If you put the button class in its own file/module and import it then you would have to make its constructor public to access it.

> button_002_04_oop_arg.d(22): Error: class `button_002_04_oop_arg_2.MyButton` member this is not accessible

On Tuesday, 19 March 2019 at 12:33:08 UTC, Ron Tarrant wrote:
> Tuesday again. This blog post is about invisible Entry widgets and the FontButton. Really stimulating stuff and you'll find it at: http://gtkdcoding.com/2019/03/19/0019-disappearing-text-entry.html

A little copy/paste glitch..
code (on blog and on github) says 'text entry box' where a FontButton is used:

> writeln("The text entry box holds: ", fontButton.getFontName());

On Friday, 22 March 2019 at 13:17:23 UTC, number wrote:

> Not sure about .md or file version, but there are no links in the actual blog post:
> http://gtkdcoding.com/2019/02/15/0010-checkbutton.html

It's fixed now.

> and apparently also not in in this .md file:
> https://raw.githubusercontent.com/rontarrant/gtkDcoding/master/docs/_posts/2019-02-15-0010-checkbutton.md

This is actually the .md source file for the above html file, so it's fixed, too.

Thanks for catching yet another broken link.