harmonia & build

[Hasan Aljudy]

Andrew Fedoniouk wrote:
> "Hasan Aljudy" <hasan.aljudy at gmail.com> wrote in message 
> news:dv0luu$2to5$1 at digitaldaemon.com...
> 
>>Hasan Aljudy wrote:
>>
>>>I noticed a comment in the make file ..
>>>#native\win32.d - do not compile it as it is just a 'header'
>>>
>>>so I looked in the build documentation, and found that inserting
>>>version(build) { pragma(nolink); }
>>>will tell build to not link this file, so I added it to
>>>harmonia/native/win32.d
>>>
>>>and it compiled fine .. BUT
>>>When I run it, I get an "access voilation" messege and then the program 
>>>exits.
>>>
>>
>>When I turn on the -debug switch, the messege becomes:
>>
>>
>>>ERROR: Access Voilation
>>>while processing win message #0x0
>>
>>Here's the stack frame from windbg
>>
>>00 
>>image00400000!D8harmonia2ui6window6Window10childStyleFE8harmonia2ui11definitions11ControlTypeZC8harmonia6themes5theme5Style+0x17 
>>[C:\dmd\src\other\harmonia\ui\window.d @ 303]
> 
> 
> It is here:
>   return Theme.defaultTheme.themeStyle(id);
> 
> Seems like module harmonia.themes.pathfinder;
> was not included by build.exe.
> 
> It has:
> static this()
>   {
>     // install this as a default theme
>     defaultTheme = new PathfinderTheme();
>   }
> 
> module harmonia.themes.pathfinder; is theme implementation
> and has no direct external references.
> 
> You need to tell to build.exe somehow that it must include it.
> 

Ah! Thanks!
I added an import for harmonia.themes.pathfinder and now it works for 
half a second (shows a window) but still produces an access voilation!!
while processing win mesage #0x200

Any other modules you know which are needed but not referenced?!

/me goes to check the call stack ..

ok, I think this one is harmonia.ui.tooltip
let me try ..

(after 20 seconds ...)

yup! seems to work fine now!! :D