[maemo-developers] Fremantle user interface behaviour and API

[From: Brent Chiodo]

On 5/14/09, Cornelius Hald <hald at icandy.de> wrote:
>
> Panable Area
> How exactly should I use it? I replaced my ScrollableWindow with a
> PanableArea, the rest of the code I left  as it is in Diablo. Inside the
> PanableArea is a GtkTextBox. Nothing else.
> Now, it renders correctly, that is it has only this small scroll indicator
> and not a real scroll bar. But I cannot pan. If I try to pan it always
> selects the text inside the text box. How is this supposed to work? How is
> the destinction made between selecting text and scrolling/panning the text?
>
> _______________________________________________
> maemo-developers mailing list
> maemo-developers at maemo.org
> https://lists.maemo.org/mailman/listinfo/maemo-developers
>

I have also run into this problem trying to update Quick Clip (the
text viewer part). If anyone here uses Quick Clip in Diablo, you will
see I have implemented Kinetic scrolling (via mokoui.FingerScroll) by
having a toggle-button to toggle whether the TextView is selectable or
not. The toggle-button callback is very simple (this is in Python):

def select_mode_button_callback(self, widget, button=False, check=False):
      if button == True:
         active = self.select_mode_button.get_active()
         self.m_select_mode.set_active(active)
      if check == True:
         active = self.m_select_mode.get_active()
         self.select_mode_button.set_active(active)

      if active == True:
         self.textview.set_sensitive(True)
         self.textview.set_editable(False)
      else:
         self.textview.set_sensitive(False)


Basically it just toggles the Textview sensitive/insensitive. But if
you try to do this in Fremantle, it grays out the Textview (when
insensitive) making the text unreadable. Maybe a viable solution would
be to not gray out the Textview? Anyway, there needs to be a solution,
because right now it's unworkable.

-- 
Best Regards,

Brent Chiodo