Comments you submit will be routed for moderation. If you have an account, please log in first.

Opened 6 years ago

Closed 5 years ago

#60 closed bug (fixed)

Snapshot column widths in Preselect window

Reported by: video@… Owned by: tboeckel
Priority: low Milestone: YAM 2.7
Component: user interface Version:
Severity: minor Keywords:
Cc: OS Platform:
Blocked By: Blocking:
Release Notes:

Description (last modified by tboeckel)

Can the column positions in the preselect window be made snapshotable?

The column positions on the preselect window will not snapshot like the other windows will, and the download goes easily three times faster if the column positions are locked (sibce column positions no longer need to be computed, I assume). Hence, every time I use the preselect I grab the columns and move them slightly to lock them in place. This often crashes the machine, [I suppose that aspect should be a bug report] but the download speedup is worth it anyway. :)

Moved from SF:

Attachments (0)

Change History (6)

comment:1 Changed 6 years ago by damato

  • Component changed from stable build to undefined

comment:2 Changed 6 years ago by damato

  • Cc yamos-svn@… removed

comment:3 Changed 6 years ago by damato

  • Component changed from undefined to user interface
  • Milestone set to YAM 2.7
  • Priority changed from undecided to low
  • Severity changed from major to trivial
  • Status changed from new to accepted

I agree that the column width of the preselection windows should be snapshotable. So I flag this ticket to be addressed in the next YAM version, however with low priority.

comment:4 Changed 6 years ago by tboeckel

  • Severity changed from trivial to minor

The solution is not as easy as one might think on the first glance. This is because MUI will invoke MUIM_Export for existing objects only.

This means that the preselection list can be snapshotted, but currently only by snapshotting the main window, NOT the preselection window. While this may sound unfortunate, the biggest drawback is yet to come...

As soon as the preselection window is closed again after a transfer the next snapshot action will remove the previously remembered information about the preselection list again from the ENV:MUI/YAM.cfg file, because the object no longer exists and thus there is no configuration to be saved now. This is how MUI handles its objects. Only living objects at the time of MUIM_Export will be respected.

Thus we either live with the non-snapshotable preselection list or we find another way how to workaround this issue. One solution would be to have the preselection/transfer window being alive all the time and just open/close the window as needed. But this will consume memory even when no preselection/transfer window is visible.

comment:5 Changed 5 years ago by tboeckel

  • Description modified (diff)
  • Owner set to tboeckel
  • Status changed from accepted to assigned

comment:6 Changed 5 years ago by tboeckel

  • Resolution set to fixed
  • Status changed from assigned to closed

(In [5419]) * mui/PreselectionWindow.c, YAM_UT.c: the column layout of the preselection

window can be saved permanently. This is accomplished by using the new
Base64Dataspace class to store the layout of the dynamically added NList
object. MUI itself will save the window's dimensions, but I cannot save
further exported data by MUIM_Export of already dead objects. This is why
we have to take this detour. This finally closes #60.

Add Comment

Modify Ticket

as closed The owner will remain tboeckel.
The resolution will be deleted. Next status will be 'reopened'.

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.

This list contains all users that will be notified about changes made to this ticket.

These roles will be notified: Reporter, Owner, Subscriber

  • Thore Böckelmann(Owner, Participant)
  • video@…(Reporter)