Changes between Version 4 and Version 5 of FAQ/Using YAM


Ignore:
Timestamp:
May 11, 2012, 2:48:30 PM (3 years ago)
Author:
damato
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FAQ/Using YAM

    v4 v5  
    1616=== Why is keyboard selection of multiple mails not working? ===
    1717According to the documentation and the configuration GUI of the NList.mcc class (which is used in YAM for displaying the mail list) one should be able to select multiple entries in a Listview by using the CTRL+Up/Down keys. However, when I use these keys the listview scrolls to the beginning or end rather than allowing to select multiple entries.
    18 
    1918The reason for this problem is, that the default keybindings of NList.mcc and the default keybindings of MUI itself clash. So when you use CTRL+Up/Down the default MUI keybindings will have preference over the NList settings and thus won't trigger the correct functions in NList itself.
    20 
    2119The solution is to either upgrade to NList release 0.108 or later as the default keybinding have been changed to use ALT+Up/Down rather than CTRL. Just make sure that you reset the keybinding settings in the MUI configuration pane of the NList classes after you have installed 0.108+ of the NList classes. Another solution (for older NList versions) would be to manually change the keybinding settings in the MUI configuration to use the ALT key rather than CTRL key (see all the "Select XXX" entries in the example screenshot below).
    2220
    2321[[Image(nlist-cfg.png)]]
    2422
     23=== I use AmigaOS 3.9 and activated the AISS theme. Unfortunately some of the icons display an ugly black background. Why? ===
     24The AISS icons are PNG icons which use alpha channels. With AmigaOS 3.9 the transparency can not be displayed correctly because of some incompatibilities between the datatypes.library.
     25
     26=== The graphical attachment list is displayed truncated and does not reflect all available attachments. Anything to prevent that? ===
     27For mails with lots of single attachments, the graphical display of attachments in a read window might be displayed truncated. This happens in case the attachment list object cannot enlarge itself to the required size (e.g. because the window is to small). Unfortunately it is even not possible to display/use a scrollbar for those cases due to technical reasons.
     28
     29But as the attachment list is virtual group object you should be able to use the virtual scrolling capabilities of MUI for that case. Please consult the MUI configuration for setting the scroll action hotkey/mouse button. But per default, MUI should allow you to hold down the middle mouse button while moving your mouse. This should then allow you to scroll the attachment list and view the other attachments that are normally hided. Another way for displaying all attachments of a mail is, of course to use the respective toolbar buttons (Display, Print, etc.) which will present you a full list of the attachments.
     30
     31=== Why is the mail preselection/transfer window sometimes active by default and sometimes not? ===
     32YAM can be configured to show the preselection/transfer window for downloading new mails only if certain conditions are met, for example always, never or only if very large mails are to be downloaded. Since mails can be fetched in the background while you continue your work with YAM it would be very inconvenient if the preselection window would steal the focus from the currently active window (i.e. a write window to compose a new mail). Just imagine that you press "C" in that very moment the preselection window opens. This would immediately cancel the transfer, even if you were just going to type in the word "Commodore"...
     33
     34To avoid such unwanted abortions YAM will open the preselection/transfer window in inactive state for automatically initiated mail transfers (i.e. timed mail fetch or mail transfers initiated by an ARexx script). For all user initiated transfers (import, export, get/send mail) the window will be activated, because this is an action that was explicitly triggered by the user and not some automechanism triggered by YAM itself.
     35
     36