Right, time for a new announcement from me.
First off the library I have been talking about called DWC has been
renamed. It is now Under the banner of Devisualization, window[0] project.
Devisualization.window otherwise known as de_window is a window and
context creation for Windows, Linux
Nice work, it's basically the SDL replacement I wished for! I
like that its scope is well defined.
I don't get why it depends on DerelictGL. AFAIK SDL, GLFW and
friends do not depend on GL function loaders.
On Friday, 7 November 2014 at 10:48:46 UTC, Rikki Cattermole
wrote:
- Native GUI controls (such as the menu for OSX)
D native or OS native?
On 8/11/2014 12:46 a.m., ponce wrote:
Nice work, it's basically the SDL replacement I wished for! I like that
its scope is well defined.
I don't get why it depends on DerelictGL. AFAIK SDL, GLFW and friends do
not depend on GL function loaders.
It depends because of OpenGL context creation.
On 8/11/2014 12:48 a.m., Kagamin wrote:
On Friday, 7 November 2014 at 10:48:46 UTC, Rikki Cattermole wrote:
- Native GUI controls (such as the menu for OSX)
D native or OS native?
Short answer:
Basically it should use the native implementation if possible otherwise
it should use the non
Also when I tried to declare / use extern strings like from
NSApplication.h:
APPKIT_EXTERN NSString *NSApplicationDidHideNotification;
I found no way to get this working. Is this a limitation of
the current
64 bit port?
I think that should work. How did you declare it? It should be
On 2014-11-07 13:12, Christian Schneider wrote:
Jacob, thank you very much for your reply and explanations!
I get EXC_BAD_ACCESS (SIGSEGV) for both NSString and void * if I use the
declaration you suggested.
What exactly are you doing with the string when you get the
EXC_BAD_ACCESS? Also,
I get EXC_BAD_ACCESS (SIGSEGV) for both NSString and void * if
I use the
declaration you suggested.
What exactly are you doing with the string when you get the
EXC_BAD_ACCESS? Also, can you reproduce the issue in an program
just printing this variable with NSLog?
I get the SIGSEGV when i
On 2014-11-07 15:23, Christian Schneider wrote:
I get the SIGSEGV when i try to NSLog this string constant. I was not
looking any further, because if it fails to NSLog, i can't do anything
with it ;)
Now I know what the problem is. In D, module variables are by default in
TLS (thread local
Now I know what the problem is. In D, module variables are by
default in TLS (thread local storage). To make it refer to a
global C variable, use __gshared:
extern (C) extern __gshared NSString
NSApplicationDidHideNotification;
Sorry, I completely forgot about that.
Ha, awesome! It
On 2014-11-07 17:05, Christian Schneider wrote:
Ha, awesome! It works! I'll add this to a wiki page in the DiveFramework
github repos.
Thanks again!
No problem :). This isn't mention in the DIP since this has nothing to
do with Objective-C, it's rather plain C. This is documented here [1].
I've recently decided to open source FoundationDB D API from our
internal project. It's released under MIT license since that's
the simplest option I could think of.
https://github.com/GeorgeSapkin/fdb-d
It has been ripped out of a working project so it's missing unit
testing and sample
12 matches
Mail list logo
