I have a listview like this:
<listview id="filelist" notify="active; doubleclick" Multiselect="None">
The cursor keys are working with the list on MUI5.0 OS4, but not on MorphOS.
Is there some settings in MUI/MOS or the xml which enables it or should I handle it by keyboard events?
Listview keyboard on MorphOS
Re: Listview keyboard on MorphOS
Have you tried to activate the listview (clicking/tab) before using the cursor keys?
Re: Listview keyboard on MorphOS
@JPV: Yes, tried it.
Running the MUI-Demo.hws and selecting the Listviews window in it, cursor keys are not working on my MOS installation.
Checked some MorphOS Preferences items and found that the listview gadgeds there are useable with keyboard.
I am quite unexeperienced in MOS, so don't know if it is a default feature or not.
Running the MUI-Demo.hws and selecting the Listviews window in it, cursor keys are not working on my MOS installation.
Checked some MorphOS Preferences items and found that the listview gadgeds there are useable with keyboard.
I am quite unexeperienced in MOS, so don't know if it is a default feature or not.
Re: Listview keyboard on MorphOS
Hmm.. true. The listview in the Listviews window doesn't work, but then the listview in the Strings window does work. It looks like that you need to activate the cyclechain and then keyboard controls do work.
This put to listview definition in XML seems to do the trick and then the Listviews demo works too:
cyclechain="true"
Bug or feature, I don't know
This put to listview definition in XML seems to do the trick and then the Listviews demo works too:
cyclechain="true"
Bug or feature, I don't know
Re: Listview keyboard on MorphOS
Many thanks!
Cyclechain does the trick.
Cyclechain does the trick.
- airsoftsoftwair
- Posts: 5443
- Joined: Fri Feb 12, 2010 2:33 pm
- Location: Germany
- Contact:
Re: Listview keyboard on MorphOS
I don't know whether this is a bug or feature either but it certainly concerns MUI, not MUI Royale... so if you want some clarification, ask Thore by filing a ticket concerning this inconsistent behaviour over on http://muidev.de/