On Sunday, 10 February 2019 at 21:26:56 UTC, Adam D. Ruppe wrote:
> On Sunday, 10 February 2019 at 18:42:59 UTC, Murilo wrote:
>> Adam, is there a place where we can chat? I don't like chatting via this forum. I would like to talk to you about your modules and about the D lang.
>
> get on the freenode irc, i am in #d like all the time (and will see messages when i am back on my computer) or you can dm me adam_d_ruppe there if i am online

okay, I will try that, but do you have a facebook account? I usually chat with people on facebook.

On Sunday, 10 February 2019 at 21:26:56 UTC, Adam D. Ruppe wrote:
> On Sunday, 10 February 2019 at 18:42:59 UTC, Murilo wrote:
>> Adam, is there a place where we can chat? I don't like chatting via this forum. I would like to talk to you about your modules and about the D lang.
>
> get on the freenode irc, i am in #d like all the time (and will see messages when i am back on my computer) or you can dm me adam_d_ruppe there if i am online

Hi Adam. I have been using your arsd library and I have noticed that compiling with -m64 causes this error:
Error: cannot mix core.std.stdlib.alloca() and exception handling in _D4arsd4jpeg27detect_jpeg_image_from_fileFAxaJiJiJiZb()
May I know why that happens? How can I bypass it?

On Tuesday, 12 February 2019 at 01:16:21 UTC, Murilo wrote:
> Hi Adam. I have been using your arsd library and I have noticed that compiling with -m64 causes this error:

huh, only on 64 bit windows.

well, pushed a fix up, try the new version

On Tuesday, 12 February 2019 at 01:31:48 UTC, Adam D. Ruppe wrote:
> On Tuesday, 12 February 2019 at 01:16:21 UTC, Murilo wrote:
>> Hi Adam. I have been using your arsd library and I have noticed that compiling with -m64 causes this error:
>
> huh, only on 64 bit windows.
>
> well, pushed a fix up, try the new version

Hi, unfortunately the problem persists. I have sent you an e-mail on your destructionator@gmail.com account. I would prefer to talk there rather than here. I would just like to understand what is causing the problem so I can figure out a bypass.

On Tuesday, 12 February 2019 at 01:31:48 UTC, Adam D. Ruppe wrote:
> On Tuesday, 12 February 2019 at 01:16:21 UTC, Murilo wrote:
>> Hi Adam. I have been using your arsd library and I have noticed that compiling with -m64 causes this error:
>
> huh, only on 64 bit windows.
>
> well, pushed a fix up, try the new version

Forget about it, I just fixed it myself. :) I am so happy, I did not think I would be able to do it on my own, I guess all those years of studying were worth the effort, I read the error message and figured it was something wrong in the module jpeg.d so I opened it, read the code(in a very fast manner) and discovered that the calls to core.stdc.stdlib.alloca() were causing the problem apart from being unnecessary so I just commented all of them out(just like you did with the very first instance) and then there was a problem with the buffer variable which was only defined by you in the first instance so I just defined it in the other instances following the same method you used and it all worked in the end. I will submit a pull request on your GitHub page. Cheers.

On Tuesday, 12 February 2019 at 01:31:48 UTC, Adam D. Ruppe wrote:
> On Tuesday, 12 February 2019 at 01:16:21 UTC, Murilo wrote:
>> Hi Adam. I have been using your arsd library and I have noticed that compiling with -m64 causes this error:
>
> huh, only on 64 bit windows.
>
> well, pushed a fix up, try the new version

Hi Adam. I am using your library. There is the ScreenPainter struct and it has a method called .eventLoop(), how do I make it stop after a certain amount of loops? I would like to be able to call it several times in the program.

On Monday, 25 February 2019 at 22:34:54 UTC, Murilo wrote:
> Hi Adam. I am using your library. There is the ScreenPainter struct and it has a method called .eventLoop(), how do I make it stop after a certain amount of loops? I would like to be able to call it several times in the program.

I fear your program is poorly designed, that kind of thing shouldn't be necessary.

But it is possible by using the EventLoop struct directly.

http://dpldocs.info/experimental-docs/arsd.simpledisplay.EventLoop.html


EventLoop.get.exit() will exit the loop, though it may not want to start up again (I have never tried).

You can also do something like, after setting it all up,

    bool done;
    EventLoop el = EventLoop.get;
    el.run(() { return !done; });


And that delegate you pass to `run` tells it when to return.

Hi Adam, how do I set the color of the SimpleWindow background?

On Tuesday, 12 March 2019 at 02:21:51 UTC, Murilo wrote:
> Hi Adam, how do I set the color of the SimpleWindow background?

You have to draw a rectangle on the window to make your own background. Set both outlineColor and fillColor to the same thing, then do painter.drawRectangle(Point(0, 0), Size(window.width, window.height));