Total Commander

Samsung Galaxy S20 5G - Android 13, One-UI 5.0
TCA 3.40b4

When I try to create a Widget fot Totalcmd-Editor via the phones Widget editor it fails - see videos:

https://madsenworld.dk/tcmd/TCAndroidEditorWidgetCreationByTapError.mp4
https://madsenworld.dk/tcmd/TCAndroidEditorWidgetCreationByDragError.mp4

I can though make a shortcut to the Editor on the Startscreen from TC by long-press on a filename, choose "Create link on the desktop", tap on >> in the "Command" field and then choose "Totalcmd-Editor"
.

It's actually not a widget, it's a desktop link. I don't know why this fails on some devices, it works fine here.
You can instead long tap on the Total Commander icon and then drag the editor icon to a place on your launcher.

I can though make a shortcut to the Editor on the Startscreen from TC by long-press on a filename, choose "Create link on the desktop", tap on >> in the "Command" field and then choose "Totalcmd-Editor"

That's not the same, you need to create a Total Commander link "widget" for that. The editor widget only creates a link to an empty editor.

2ghisler(Author)

You can instead long tap on the Total Commander icon and then drag the editor icon to a place on your launcher.

Yes, that worked on my phone.

That's not the same, you need to create a Total Commander link "widget" for that. The editor widget only creates a link to an empty editor.

Hmm, they are closely related then. If I make a link to a file to be opened the Editor as I described (1), and I also have an icon to the Editor, made the way you describe (2), and I tap on the link to the file (1), and I thereafter tab on the Editor icon (2), then the already opened Editor with the file is shown, not a new empty Editor.

The issue still remains in TCA 3.40 final on Samsung Galaxy S20 Android 13.

It works OK on my HTC One Android 6, but here the Editor is seen as a shortcut and not a widget, as it is on the Samsung phone. The Samsung phone apparantly lists widgets and shortcuts together for each app.

Sorry, I don't have a solution to this problem.

Same problem here on Samsung Galaxy A53, SM-A536B/DS
Christian's 2022-11-25, 16:05 UTC answer solved it.

Thank you Christian