You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is there a specific reason, why the hex win_id values needed e.g. for moving and deleting windows are gathered via the section (quadrant / current position on the monitor) and not by the primary db-key?
It seems to be quite easy to produce a state, where a new and an existing window would have the same section value:
Add two windows. (id=1 has section=1 and id=2 has section=2)
Switch their sections. (id=1 has section=2 and id=2 has section=1)
Delete one window. (E.g. there's now only id=2 with section=1)
Add a new window. (Now there's id=1 with section=1 and id=2 with section=1)
Is there a specific reason, why the hex
win_id
values needed e.g. for moving and deleting windows are gathered via the section (quadrant / current position on the monitor) and not by the primary db-key?It seems to be quite easy to produce a state, where a new and an existing window would have the same
section
value:Ultimately, I think it comes down to assigning
id
andsection
individually and not derive them from the same value as it's currently happening: https://github.com/UB-Mannheim/PalMA/blob/master/control.php#L273-L279Still I haven't understood, why all the window controls work via section (called "window" in the request) and not id in the first place.
The text was updated successfully, but these errors were encountered: