[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [MiNT] XaAES 1.55 + NetSurf
- To: mint@lists.fishpool.fi
- Subject: Re: [MiNT] XaAES 1.55 + NetSurf
- From: "Helmut Karlowski" <helmut.karlowski@ish.de>
- Date: Wed, 27 Mar 2013 08:20:35 +0100
- In-reply-to: <eaab616427395c36fe43345756276068-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBeX15ZVF0WWlpoBVc6XFxZRUYGX11QQQ==-webmailer2@server01.webmailer.hosteurope.de>
- List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
- List-id: <mint.lists.fishpool.fi>
- List-owner: <mailto:tjhukkan@fishpool.fi>
- List-post: <mailto:mint@lists.fishpool.fi>
- List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
- List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
- References: <1a2bc1b0313889dc18489decbddd2c3b-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBeX15ZVF0WXl9/H1RUWTBeQkMGXlxRQl9V-webmailer2@server02.webmailer.hosteurope.de> <52f3d2826a772c5b4b06dfa093d62a7f-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBYWEJGUFEWXFloA1VTMl5cR0EAX19eQFg=-webmailer2@server06.webmailer.hosteurope.de> <op.wuhyjes3ofd6j1@nebbiolo> <1791863.aaK6fzoqOT@chertsey> <08afba233ce6847e01607a6d6ee96fdb-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBeX15ZVF0WWlpoBVc6XFxZRUcHWltfRw==-webmailer2@server02.webmailer.hosteurope.de> <d791c38954ade8f9b5bc912755026421-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBYWEJGUFEWXFloA1VTMl5cR0EAV19ZSVs=-webmailer2@server06.webmailer.hosteurope.de> <eaab616427395c36fe43345756276068-EhVcX1lFRQVaRwYcDTpQCEFddQZLVF5dQUNBAjBeX15ZVF0WWlpoBVc6XFxZRUYGX11QQQ==-webmailer2@server01.webmailer.hosteurope.de>
- Sender: mint-bounce@lists.fishpool.fi
- User-agent: Opera Mail/12.14 (Win32)
Ole, 27.03.2013 00:33:11:
When using XaAES 1.5.4 this version of netsurf works fine.
When using XaAES 1.5.5 - it crashes. Putting message boxes around
wind_open(), results in the first message box beeing shown... then
parts of the window got drawn (only parts of the AES objects, no
content yet!) , and the secone message box never appears.
Helmut, can you help on this? To me it strongly looks like some XaAES
Can you compile XaAES yourself?
Does it work with the current XaAES 1.6.0?
logging and post the log? Do we have other possibilities to enable more
debug output?
XaAES has debugging-facilities, but this needs to be built in for every
issue you're looking for.
In case wind_open does not return it should be possible to find the reason.
--
Helmut Karlowski