[maemo-developers] Aw: Re: Fremantle user interface behaviour and API

[From: API]

From: Cornelius Hald <hald at icandy.de>

> On Thu, 2009-05-14 at 15:12 +0200, API wrote:
> > If you want to see the differences between the HildonUIModes, you can try to
> > take a look to the hildon-pannable-area-touch-list-example, included on the
> > examples directories. AFAIK, the example package is not included with the
> > beta, but you can download the hildon-widgets source code and compile it
> > by yourself. This example compare the two hildon modes and the "old
> > behaviour".
> 
> Thanks, I didn't know that there were examples... I downloaded and
> compiled them. Now it's time for playing :)

Yes, for any reason the package libhildon1-examples were not included with the
SDK, when in the end, can be really useful, as currently we have an example
for almost all hildon widgets, and in the complex ones, like pannable area,
several examples. I hope that this package will be included on the future
final SDK.

> > This is still a normal treeview, you use hildon_gtk_tree_view_new only to ensure
> > to get the proper theming. So when one of the rows are selected the GtkTreeSelection
> > of this treeview emits the signal "changed" [1].
> 
> I checked my code again and yes, the signals are emitted. The problem
> was, that I was using gtk_tree_view_get_selection() inside a
> "row-activated" handler which does not work with the hildonized tree
> view. I changed my code to use the provided GtkTreePath and now it's
> working fine.

Remember that "row-activated" is different to "selection". On the desktop,
on the treeview, if you select another element, the GtkTreeSelection emits
the signal selection change, but this doesn't mean that the row is activated.
To do that you need to explicitly activate the row, in the desktop you do a
double-click on the row selected. In this sense, you can use a "normal"
treeview on hildon (without the special modes), and this should work properly.

> 
> > In the same way, recently a new signal was added to the maemo-flavoured gtk, so
> > if a row is tapped on the treeview, the treeview emits the signal "hildon-row-tapped",
> > this could be useful to you too although I'm not sure if it was included on this beta,
> > take a look to the gtk code to confirm that.
> 
> I tried and it is included in the beta SDK. In which way should that be
> different from "row-activated"? For me it looks like both are doing the
> same. So I'll stick to "row-activated" for now.

The difference is that with the new HILDON_UI_MODE_NORMAL, used to select
elements easily, the treeview will not have any selection, and any press
on any row will emit the normal row-activated, as the interaction with the
screen is different on a embeded device (the one hildon is oriente for).

This new hildon-row-tapped was oriented to the mode HILDON_UI_MODE_EDIT, that
requires to now when the user taps on any row, as the selection could not change,
and it is slightly different to activate the row.

> > I hope this helps
> 
> It helped a lot. Thank you very much!

You are welcome ;)

===
API (apinheiro at igalia.com)