Closed bmivzkrp closed 2 years ago
Hello,
Thank you for the suggestion and your interest in Discreet Launcher!
At first reading, I wonder if opening a context menu (which is usually done with a long press) could conflict with how the drag and drop process is implemented. I will have a look and try to think about another option if the context menu doesn't work as expected.
Just so that you are not surprised, I should mention that it will probably take a long time as I am currently very busy with my job.
Best regards.
No, everything works properly there. It s just that the current concept is not very convenient for blind users, and I think we need an alternative. Moving works, and the context menu also works when using TalkBack or Jieshuo. Just when working with applications, a blind user uses a double touch as opposed to a seeing user who uses a single touch. Although I don t know how all this has changed in the latest versions of Android, as it already supports multi-finger gestures for accessibility. Of course, in the screen reader settings, we can enable the activation of items with one touch, and everything will be the same as for users who see. But for many blind users, double touch is more convenient. Your Launcher is great, it works perfectly.
04.05.22 19:32, Vincent Falzon пише:
Hello,
Thank you for the suggestion and your interest in Discreet Launcher!
At first reading, I wonder if opening a context menu (which is usually done with a long press) could conflict with how the drag and drop process is implemented. I will have a look and try to think about another option if the context menu doesn't work as expected.
Just so that you are not surprised, I should mention that it will probably take a long time as I am currently very busy with my job.
Best regards.
Here is another alternative concept:
The user in the context menu, selects, for example, Move below;
He again gets to the list of items;
Focuses on the element below which he wants to place the element he needs;
The user touches this item;
The item that the user moves is below the item that the user touched.
Similarly, when the user selects Move above in the context menu.
Hello,
Thank you for the additional explanations and suggestion :-) I didn't had the time yet to start looking into this to be honest...
Best regards.
Hello,
This has been a long time but, good news, this will be implemented in the next release!
I implemented what you suggested in your first post but I changed it a bit to get Move before "app1"
and Move after "app2"
, with "app1" and "app2" the name of the apps respectively before and after the selected one.
The first and last apps in the list of favorites will display only the relevant option, as described in your step 7.
Best regards.
Hello,
I am pleased to inform you that this has been implemented in new release v6.4.0! This release has been published few minutes ago.
Here are the usual availability delays for each location:
Remarks: I will leave this ticket opened until the release is effectively published on F-Droid. You can use the export/import feature to switch from one version to another.
Best regards.
I just got 6.4.0. I can t find the functionality you described because the context menus don t have it.
Hello @bmivzkrp,
Sorry for the late reply, I was away last weeks.
When you open the page to order favorites by drag and drop, if you long press an item in the list a context menu should appear with options to move the item upwards or downwards (if this is not the first/last item of the list). I just tested on my phone and for me it appears as expect. This doesn't work for you?
Best regards.
@falzonv Please excuse me. I guess I didn t think the concept through properly when I proposed it. This currently does not work for blind users as it conflicts with the normal way to move items. Could you do it differently? Next to each item in the list should be a button called, say, the "Action Menu". If we click on it, a list of actions appears. It is better to do it this way, because otherwise the user will have to change the settings of the screen reader. I apologize once again for my carelessness.
Hello,
Ok no worries, I will have a look on how to change this from the current long press towards a dedicated button. However I am quite busy at the moment so the next release will probably not be before september...
Best regards.
Hello,
I have just published a new release v6.5.0 with a different way of doing it which, hopefully, should work for both blind and non-blind users while not conflicting with the normal way to move items.
There are now two arrows for move up and move down next to each item (except first and last items which are special). For these arrows, the field contentDescription
that should be read by TalkBack (if I understood properly) is filled with a relevant text such as "Move before (the name of the app above)" or "Move after (the name of the app below)".
Before implementing this, I also tried with a simple button opening a list of actions. It works of course, but I am afraid this would confuse non-blind users by sort of "hiding" that you can simply move the items to reorder the list (if people see a button they may not think other parts are clickable). It's kinda the same issue with arrows but at least the user experience stays more efficient, and even for blind users it should save a couple of clicks.
This ticket will stay open at least until v6.5.0 is available on F-Droid (usually takes 4 to 8 days).
Best regards.
@falzonv Many thanks.
Could we suggest an alternative concept of moving items that would be more convenient for some blind users? What it looks like now: