Hello,<br><br>i hope i've found the cause for the trouble in freecell. This fix worked for me:<br><br>freecell.cpp : Line 137 (in: Freecell::moveCards(CardList &c, FreecellPile *from, Pile *to) )<br>-- waitfor = c.first();<br>
++ waitfor = c.last();<br><br>Explanation:<br>When a card is clicked and dragged ( cardscene.cpp : mousePressEvent ) the program checks from the bottom of the pile to the top and adds the card that has been clicked and all above. So the card on the top of the pile is c.last(), not c.first()<br>
My Freecell worked after this change, i hope it will fix it...<br><br>I also checked Spider, but there is no CardList.first() that could be changed into .last() but i'll have a deeper look to it later.<br><br>Greetings,<br>
julian <br><br><br><div class="gmail_quote">2009/12/14 Parker Coates <span dir="ltr"><<a href="mailto:parker.coates@gmail.com">parker.coates@gmail.com</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><div></div><div class="h5">On Sun, Dec 13, 2009 at 16:56, Andreas Pakulat wrote:<br>
> On 12.12.09 12:29:03, Parker Coates wrote:<br>
>> On Fri, Dec 11, 2009 at 20:34, Andreas Pakulat wrote:<br>
>> > On 11.12.09 16:50:45, Parker Coates wrote:<br>
>> >> On Fri, Dec 11, 2009 at 16:14, Andreas Pakulat wrote:<br>
>> >> > Hi,<br>
>> >> ><br>
>> >> > I'm wondering if anybody else has problems with KPat not accepting<br>
>> >> > mouse-clicks/drags anymore after a couple of initial moves when playing<br>
>> >> > Freecell? The first oddness is that a double-click to move a card to the<br>
>> >> > free-stack doesn't result in an undoable action. And then after a couple<br>
>> >> > of movements of cards around I can suddenly not click anything anymore,<br>
>> >> > no card reacts. Seems this happens as soon as more than one card is<br>
>> >> > moved at once.<br>
>> >><br>
>> >> Yes, others have seen it. It's been reported as bug 218019. [1]<br>
>> ><br>
>> > Thanks and sorry for being lazy :) Thats basically all I needed...<br>
>> ><br>
>> >> > The same happens in Spider when the first complete line from ace to king<br>
>> >> > vanishes.<br>
>> >><br>
>> >> Crap. I was hoping it was Freecell specific. The reporter claimed that<br>
>> >> he didn't have any issues in Spider, but maybe he didn't play for long<br>
>> >> enough to clear a run.<br>
>> ><br>
>> > Just to be sure we're on the same page: A "run" means adding up cards<br>
>> > from King down to ace so it gets nicely moved to the bottom-left<br>
>> > stack-place, right? Oh, btw, this was single-suite spider<br>
>><br>
>> Yeah, that what I meant by "run".<br>
>><br>
>> >> > Saving and reloading the games helps "fixing" the problem with Spider,<br>
>> >> > i.e. it doesn't block access to the cards until I start a new game. In<br>
>> >> > Freecell loading a game that previously blocked also makes it playable,<br>
>> >> > but only until the next move that involves more than one card.<br>
>> >><br>
>> >> Thanks for the details. Please add them to the report, if you don't<br>
>> >> mind. If you start then stop the demo, does that have any affect?<br>
>> ><br>
>> > For Freecell it didn't hit the problem as the demo mode always moved<br>
>> > only a single card.<br>
>><br>
>> Makes sense.<br>
>><br>
>> > For Spider it was a bit tricky to get it to complete a run as it always<br>
>> > "hangs" when one can still move cards around, but not in a meaningful<br>
>> > fashion (i.e. one empty 9 and one thats build down to 6, so you can move<br>
>> > 8 and following around). But once I had it complete a run it didn't<br>
>> > stop. When I then completed the next run manually it again stopped<br>
>> > accepting any input.<br>
>> ><br>
>> > Oh, wait now I understand what you mean with "start and stop demo"...<br>
>> > No, once the mouse stops working the demo button also stops working.<br>
>> ><br>
>> > Added that and the other text to the report. I took the liberty to mark<br>
>> > the bug as NEW and kde-4.4.0-blocker as IMHO this breaks the app quite<br>
>> > heavily. Feel free to change the latter back (in the Keywords)<br>
>><br>
>> Those both seem fair.<br>
>><br>
>> >> This bug is definitely my fault, and I'm feeling pretty bad about it.<br>
>> >> Just before the freeze I cleaned up the mouse handling and it seemed<br>
>> >> to be working well, but I didn't really consider the custom weirdness<br>
>> >> that Freecell adds. The major problem here is that I'm out of town for<br>
>> >> work, away from my dev machine and I will probably won't be back until<br>
>> >> January 5th.<br>
>> >><br>
>> >> I read through the code at <a href="http://lxr.kde.org" target="_blank">lxr.kde.org</a>, but I couldn't really see any<br>
>> >> obvious problems. I probably need to run it to figure out what's going<br>
>> >> on, but if I had to guess, I'd say the fix won't be that complicated.<br>
>> >> If someone else wants to take a stab at fixing this, I'd be more than<br>
>> >> happy to try to support them, but I realise that this is asking a lot.<br>
>> >> If anyone has a git-svn checkout and is willing to run a git-bisect to<br>
>> >> figure out which commit broke this, that would certainly help narrow<br>
>> >> down the issue, too.<br>
>> ><br>
>> > As I love to play Spider and Freecell I'll definetly have a look<br>
>> > sometime (probably not this weekend though). No git-svn here, but the<br>
>> > bug (at least in freecell) is easy enough to trigger. So if you can give<br>
>> > me a hint where to start looking that would be nice :)<br>
>><br>
>> Okay, I think I figured out what is wrong, at least in Freecell. If<br>
>> someone try out the following changes to freecell.cpp, test them and<br>
>> commit, it would be most appreciated. There's a much cleaner way to do<br>
>> this, but these minimum changes should get the things working again.<br>
>><br>
>> Line 257:<br>
>> - m->disconnect( this );<br>
>> + disconnect(m, SIGNAL(animationStopped(Card*)), this,<br>
>> SLOT(waitForMoving(Card*)));<br>
>><br>
>> Line 264:<br>
>> - c->disconnect(this);<br>
>> + disconnect(c, SIGNAL(animationStopped(Card*)), this,<br>
>> SLOT(waitForMoving(Card*)));<br>
>><br>
>> Let this be a lesson, kids. Always make your disconnects as specific<br>
>> as possible to avoid breaking connections made elsewhere.<br>
><br>
> Unfortunately that doesn't help. Freecell still stops doing card-moves<br>
> once one stack of cards has been moved.<br>
><br>
> A grep for similar disconnects yielded one more result in dealer.cpp,<br>
> but also adjusting that one didn't help unfortunately (line 741)<br>
><br>
> BTW: There's a disconnect() call in dealer.cpp, unless you need to<br>
> disconnect exactly at that point its not overly useful as ~QObject will<br>
> disconnect everything from the deleted object too.<br>
<br>
</div></div>Crap. Well thanks for trying it out. Back to the drawing board.<br>
<font color="#888888"><br>
Parker<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
kde-games-devel mailing list<br>
<a href="mailto:kde-games-devel@kde.org">kde-games-devel@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-games-devel" target="_blank">https://mail.kde.org/mailman/listinfo/kde-games-devel</a><br>
</div></div></blockquote></div><br>