Issue 11133

Title
Allow to edit readonly fields with drag and drop
Priority
feature
Status
chatting
Superseder
Prevent drag and drop of event with readonly dates (issue 9012)
Nosy list
acaubet, ced
Assigned to
Keywords

Created on 2022-01-13.12:33:55 by acaubet, last changed 1 week ago by ced.

Messages

Author: [hidden] (ced) Tryton committer Tryton translator
Date: 2022-01-13.13:12:51

If the end date should adapt, it is not readonly.
If I understand the use case, it is for event with fixed duration so with only one of the start or end date, you can deduct the other. In such case I would make the end date a Function field with a setter that compute back the start date.
The only missing feature would be to prevent changing the duration of an event with DnD.

Author: [hidden] (acaubet)
Date: 2022-01-13.12:33:55

From issue9012,

I think the drag and drop should be deactivated if any of those dates are readonly

In my case I have the following:
start = datetime field
estimated time = timedelta field
end = function field of type datetime
def get_end = start + estimated_time
So the end field is readonly but I also need to drag and drop because I can set a start time and the end should adapt.

History
Date User Action Args
2022-01-13 13:12:51cedsetcomponent: + tryton
messages: + msg73228
nosy: + ced
status: unread -> chatting
2022-01-13 12:33:55acaubetcreate

Showing 10 items. Show all history (warning: this could be VERY long)