Once I fixed the build issues and added back a couple of our private patches I
was able to build a working Subsurface-mobile for iOS based on Kirigami 1.0
(plus patches).
Nice. Took me a LOT longer than I wanted, but hey... it's all good.
4.5.2.1525 should be available for testing on TestFlight
> On Aug 15, 2016, at 10:06 AM, Marco Martin wrote:
>
> On Monday 15 August 2016, Dirk Hohndel wrote:
>>> On Aug 15, 2016, at 7:50 AM, Marco Martin wrote:
>>>
>>> On Monday 15 August 2016, Dirk Hohndel wrote:
Line numbers in kirigamiplugin.cpp are slightly off since I have a few
line
On Monday 15 August 2016, Dirk Hohndel wrote:
> > On Aug 15, 2016, at 7:50 AM, Marco Martin wrote:
> >
> > On Monday 15 August 2016, Dirk Hohndel wrote:
> >> Line numbers in kirigamiplugin.cpp are slightly off since I have a few
> >> lines of debug output in there; frame #9 is foreach (const QStr
> On Aug 15, 2016, at 7:50 AM, Marco Martin wrote:
>
> On Monday 15 August 2016, Dirk Hohndel wrote:
>> Line numbers in kirigamiplugin.cpp are slightly off since I have a few
>> lines of debug output in there; frame #9 is foreach (const QString &style,
>> m_stylesFallbackChain) {
>> frame #10 is
On Monday 15 August 2016, Dirk Hohndel wrote:
> Line numbers in kirigamiplugin.cpp are slightly off since I have a few
> lines of debug output in there; frame #9 is foreach (const QString &style,
> m_stylesFallbackChain) {
> frame #10 is
> qmlRegisterSingletonType(componentPath(QStringLiteral
> On Aug 15, 2016, at 7:10 AM, Marco Martin wrote:
>
> On Monday 15 August 2016, Dirk Hohndel wrote:
>> Do you have any idea, though, while this is crashing for me on iOS?
>> The crash is always in some Qt internal - and it's always that some
>> internal Qt managed pointer is set to 0x1 which th
On Monday 15 August 2016, Dirk Hohndel wrote:
> Do you have any idea, though, while this is crashing for me on iOS?
> The crash is always in some Qt internal - and it's always that some
> internal Qt managed pointer is set to 0x1 which then of course gives a bad
> access when dereferencing it.
on
On Mon, Aug 15, 2016 at 11:33:08AM +0200, Marco Martin wrote:
> On Monday 15 August 2016, Dirk Hohndel wrote:
> > Kirigami as is has a few oddities. It compiles neither with cmake nor with
> > qmake. Hmm.
> >
> > I have patches for that, but on iOS it still dies at startup with a
> > BAD_ACCESS to
On Monday 15 August 2016, Dirk Hohndel wrote:
> Kirigami as is has a few oddities. It compiles neither with cmake nor with
> qmake. Hmm.
>
> I have patches for that, but on iOS it still dies at startup with a
> BAD_ACCESS to address 0x1 when trying to loop over the
> m_stylesFallbackChain in Kirig
On Sun, Aug 14, 2016 at 09:38:27PM +0200, Thomas Pfeiffer wrote:
> On 14.08.2016 06:29, Dirk Hohndel wrote:
> > I still haven't managed to make the latest Kirigami work. And I don't think
> > I'll finish that today as I'm jet lagged and about to fall asleep on my
> > keyboard. But at least our iO
10 matches
Mail list logo
