Bug #3306

RCP: "send to" commands leads to wrong UUID/node path and persisted filenames

Added by Sebastien Jacquot 3 months ago. Updated 3 months ago.

Status:New Start date:10/27/2022
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:UI / Link / Command Spent time: -
Target version:TXM X.X

Description

All "Send to" commands have a different node path schema since we do not know the target class in the source handler.
The class string is at this moment replaced with "_link".
ex. when sending lines from Index to Progression we have:
Preference node qualifier = txm_res_20221027_154128198_0001_link
Persisted file name = txm_res_20221027_154128198_0001_link.prefs
instead of :
Preference node qualifier = txm_res_20221027_154128198_0001_Progression
Persisted file name = txm_res_20221027_154128198_0001_Progression.prefs

A solution could be to define a string in node path name created in source handler that must be replaced when creating the new result in target command.
eg. txm_res_20221027_154128198_0001_CLASSNAME
The replacement could be done in TXMResult constructor.
It's not a very good solution but should work.

History

#1 Updated by Sebastien Jacquot 3 months ago

  • Subject changed from RCP: "send to" commands to RCP: "send to" commands leads to wrong UUID/node path and persisted filenames

Also available in: Atom PDF