<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Hello Matthew,<br>
<br>
Sorry for my late reply.<br>
<br>
I believe you misunderstood me. I'm not developing a custom
Sailfish Dialog component, but creating a Sailfish app.<br>
The sources can be found <a
href="https://bitbucket.org/Superpelican/quick_clamshell/src">here</a>.<br>
<br>
My intent is also not to explicitly pop the dialog of the
pageStack, but I was forced to do this, because the dialog doesn't
do it itself!<br>
BTW I have already removed the code that should explicitly pop the
dialog of the pageStack because it didn't work.<br>
<br>
>Also, as the implementor of the Dialog, you should use the
onDone() handler to react to the user's actions, leaving the
accepted() signal to be handled by users of >your dialog.<br>
<br>
Because I'm not creating a custom dialog component, I am actually
the user of the dialog, so that's why I'm handling the
onAccepted() signal. ;)<br>
<br>
I've demonstrated what I'm experiencing in this video: <a
href="http://ubuntuone.com/71UqvktzqGWMvukeVTW8Qy">http://ubuntuone.com/71UqvktzqGWMvukeVTW8Qy</a>
(should be viewable in any HTML5 video supporting browser, that
supports WebM, like Firefox and Chromium).<br>
<br>
Kind Regards,<br>
<br>
Superpelican<br>
<br>
On 08/05/2013 01:38 PM, Matthew Vogt wrote:<br>
</div>
<blockquote
cite="mid:A85A5B205F68764C8A8C58654A9F49FAE0F87B@ord2mbx12c.mex05.mlsrvr.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<style id="owaParaStyle" type="text/css">P {margin-top:0;margin-bottom:0;}</style>
<div style="direction: ltr;font-family: Tahoma;color:
#000000;font-size: 10pt;">Hi Superpelican.<br>
Thanks for catching the errors in the Dialog documentation, I
will correct them.<br>
<br>
In your Clamshell dialog, you do not need to explicitly pop()
the dialog page in response to the accept action; it is popped
by the user's interaction (either a drag or an 'Accept' click),
and the accepted signal is generated in response to this event.<br>
<br>
Also, as the implementor of the Dialog, you should use the
onDone() handler to react to the user's actions, leaving the
accepted() signal to be handled by users of your dialog.<br>
<br>
Thanks,<br>
Matt<br>
<br>
<div style="font-family: Times New Roman; color: #000000;
font-size: 16px">
<hr tabindex="-1">
<div style="direction: ltr;" id="divRpF554313"><font
color="#000000" face="Tahoma" size="2"><b>From:</b>
<a class="moz-txt-link-abbreviated" href="mailto:devel-bounces@lists.sailfishos.org">devel-bounces@lists.sailfishos.org</a>
[<a class="moz-txt-link-abbreviated" href="mailto:devel-bounces@lists.sailfishos.org">devel-bounces@lists.sailfishos.org</a>] on behalf of
Superpelican [<a class="moz-txt-link-abbreviated" href="mailto:superpelican@zoho.com">superpelican@zoho.com</a>]<br>
<b>Sent:</b> Sunday, August 04, 2013 8:42 PM<br>
<b>To:</b> <a class="moz-txt-link-abbreviated" href="mailto:devel@lists.sailfishos.org">devel@lists.sailfishos.org</a><br>
<b>Subject:</b> [SailfishDevel] Bug in the Silica
Reference docs and possible bug in the Dialog component<br>
</font><br>
</div>
<div>Hello,<br>
<br>
Sfiet_Konstantin and I have had another debugging session on
IRC recently with my app.<br>
(<a moz-do-not-send="true"
href="http://merproject.org/logs/%23sailfishos/%23sailfishos.2013-08-03.log"
target="_blank">http://merproject.org/logs/%23sailfishos/%23sailfishos.2013-08-03.log</a>)<br>
<br>
I had defined a handler that would be called when the user
accepted a dialog. However<br>
we saw that the handler was never called. Then I noticed
that the documentation page<br>
on the Silica Reference about the Dialog component has an
error in it. The description part<br>
of the page described that an user can accept a dialog by
pushing it <b>from right<br>
to left</b>.<br>
<br>
But the onAccepted() signal hander description described
that the user could accept a dialog<br>
by pushing it <b>from left to right</b>. Well I tested it
in the emulator and the description of the<br>
Dialog component at the top of the page is correct. However
the description of the onAccepted()<br>
signal handler is incorrect. Instead when you push the
dialog <b>from left to right</b> you
<b>reject it</b>!<br>
<br>
So every time I thought I was accepting the dialog, I
actually rejected it! ;) I had only read the wrong part<br>
of the documentation page.<br>
<br>
The onRejected() signal handler description is incorrect
too. It says you can reject a dialog by pushing it<br>
<b>from right to left</b>. Which actually accepts the
dialog.<br>
<br>
I hope someone can edit the Silica Reference, so that not
more developers read the wrong part and wonder<br>
why their defined action doesn't occur! ;)<br>
<br>
<br>
Also we noticed that when a dialog is accepted, it isn't
popped from the pageStack. While according to
Sfiet_Konstantin<br>
this should happen. This is especially a problem in my app,
where the app has a homescreen where a mode is chosen.<br>
Then when a particular mode is chosen the user is first
prompted for a dialog, to enter information that is required
for<br>
that mode to operate. After the user has accepted the
dialog, the mode begins. The user can quit the mode and
return<br>
to the homescreen by simply pushing away the "mode page". <br>
<br>
However when the user does that, the dialog is still there
and he/she<br>
will have to reject the dialog too and will then finally
return to the homescreen. Not only does this require another
action from the user,<br>
it can also be confusing to see a dialog with the previously
entered value still in it. Some users will think they need
to accept the dialog.<br>
But if they do, they'll return to the "mode page", not the
homescreen. This can be very confusing.<br>
<br>
This can all be seen in this video: <a
moz-do-not-send="true"
href="http://ubuntuone.com/7MIfo6vKsdqg9PmgSQ9iH4"
target="_blank">
http://ubuntuone.com/7MIfo6vKsdqg9PmgSQ9iH4</a> (note:
this requires a browser that supports HTML5, otherwise<br>
you'll need to download the video and play it in your local
video player). Unfortunately the video has a very low
framerate. Sfiet_Konstantin and I<br>
don't know whether this is due to my laptop not being
particulary highly spec'd or Wayland causing the low
framerate. I can remember recording<br>
applications and games with another recordmydesktop frontend
on a much lower spec'd computer, so I doubt that computer is
too slow.<br>
<br>
The source code of my app can be found at <a
moz-do-not-send="true"
href="http://bitbucket.org/Superpelican/quick_clamshell/src/"
target="_blank">
http://bitbucket.org/Superpelican/quick_clamshell/src/</a><br>
<br>
I hope this is helpful for the sailors/Jollaians,<br>
<br>
Superpelican<br>
</div>
</div>
</div>
</blockquote>
<br>
</body>
</html>