Re: DlangUI print too small on retina screens

2019-04-13 Thread Joel via Digitalmars-d-learn
On Sunday, 14 April 2019 at 02:12:28 UTC, evilrat wrote: On Saturday, 13 April 2019 at 12:00:30 UTC, Joel wrote: [...] option 1 - using override DPI function: --- [...] Thanks, option 1 pretty much worked - though overrideScreenDPI didn't compile with float type (int type

Re: Do @property attributes not allow postincrement operators

2019-04-13 Thread Jamie via Digitalmars-d-learn
On Sunday, 14 April 2019 at 02:11:52 UTC, Mike Franklin wrote: On Sunday, 14 April 2019 at 01:54:39 UTC, Jamie wrote: Do @property attributes not allow postincrement operators? ... It's a long standing issue (going on 7 years old) ... I plan on getting to it, but there are other pressing

Re: Do @property attributes not allow postincrement operators

2019-04-13 Thread Mike Franklin via Digitalmars-d-learn
On Sunday, 14 April 2019 at 01:54:39 UTC, Jamie wrote: Do @property attributes not allow postincrement operators? import std.stdio; struct Foo { @property bar() { return 10; } @property bar(int x) { writeln(x); } } void main() { Foo foo; writeln(foo.bar); // actually calls

Re: DlangUI print too small on retina screens

2019-04-13 Thread evilrat via Digitalmars-d-learn
On Saturday, 13 April 2019 at 12:00:30 UTC, Joel wrote: Thanks for the reply, but I looked it up, and couldn't work out what I can do. I want to try using the overrideScreenDPI trick. option 1 - using override DPI function: --- // your average hello world UIAppMain()

Do @property attributes not allow postincrement operators

2019-04-13 Thread Jamie via Digitalmars-d-learn
Do @property attributes not allow postincrement operators? import std.stdio; struct Foo { @property bar() { return 10; } @property bar(int x) { writeln(x); } } void main() { Foo foo; writeln(foo.bar); // actually calls foo.bar(); foo.bar = 10; // calls foo.bar(10); //

Re: getOverloads trait doesn't work on functions

2019-04-13 Thread Adam D. Ruppe via Digitalmars-d-learn
On Saturday, 13 April 2019 at 19:02:42 UTC, faissaloo wrote: I'm trying to use: ``` __traits(getOverloads, fn) ``` But I get the error expected 2 arguments for getOverloads but had 1 It expects the parent and the name rather than an instance of the function. Try __traits(getOverloads,

getOverloads trait doesn't work on functions

2019-04-13 Thread faissaloo via Digitalmars-d-learn
I'm trying to use: ``` __traits(getOverloads, fn) ``` But I get the error expected 2 arguments for getOverloads but had 1 Is there an alternative I can use?

Re: gtkDcoding Blog Post # 26 - Menu Basics

2019-04-13 Thread Ron Tarrant via Digitalmars-d-learn
On Saturday, 13 April 2019 at 09:49:47 UTC, number wrote: On Saturday, 13 April 2019 at 00:25:21 UTC, Ron Tarrant wrote: I'm asking because ... the messagebox sized itself to the shorter text in the content area. They said it's an OS limitation (meaning gtk standard dialogs). Because the

Re: DlangUI print too small on retina screens

2019-04-13 Thread Joel via Digitalmars-d-learn
On Saturday, 13 April 2019 at 02:35:59 UTC, evilrat wrote: On Friday, 12 April 2019 at 08:39:52 UTC, Joel wrote: [...] It should detect DPI for you, and internally do the scaling. Though I don't know if it works at all. In case it is not yet implemented try this

Re: gtkDcoding Blog Post # 26 - Menu Basics

2019-04-13 Thread number via Digitalmars-d-learn
On Saturday, 13 April 2019 at 00:25:21 UTC, Ron Tarrant wrote: On Friday, 12 April 2019 at 13:56:51 UTC, number wrote: Are you planning to cover messagebox-like stuff (i.e. gtkdialog.. i guess?) Yes. Right after this series on menus, I start on Dialogs. The first couple of those are already