On Tue, 1 Sep 2020 20:57:40 +0200 Alfredo Fernández Díaz wrote:
>
>Hi everyone,
>
>On 20/08/31 02:46, Lewis wrote:
>>On 08/30/20 06:06 pm, Alfredo Fern⌂¨«ndez D⌂¨«az wrote:
><snip>
>>>Yes, will split 'Servidor', sure. As for 'crucial para la
>>>temporizaci⌂¨«n',
>>>that is just about the worst possible translation I could come up with
>>>yesterday, in more ways than one, but it wasn't my finest hour. I know
>>>what
>>>the help says 'time-critical' is, but could anyone please try and give
>>>me a
>>>couple synonyms that I can hopefully use tomorrow as an inspiration?
>>
>>Well the dialog itself just says "Cr⌂¨«tica". Whether this may be
>>improved upon
>>is another matter. Let's see...
>>
>>Perhaps "Critical" is the best English substitute (not a synonym, as
>>it's part
>>of the original). The point is that threads of this class will take
>>precedence
>>even over foreground server. Unlike foreground server, these threads
>>cannot be
>>interrupted by any other class for any reason.
>>
>>>Thank you in advance.
>>
>>HTH
>
>Yes, the problem with "Cr⌂¨«tica" was adding something to it, which
>always made it look less critical. Also, "crucial" kind of requires
>"for", which can be understood as nearly the opposite of "because of"
>there. I hope this will look better in the next live review. (I have
>compiled the help and read it again, it was just too soon to have proper
>perspective.) Thank you for your input. (hey, isn't that the same as
>"because of" now? ;)
>
>>PS - I'm also somewhat confused concerning process priority as it
>>pertains to
>>VDMs. AFAIK, the only control over VDMs is delta, and this may only be
>>set in
>>the DOS SETTINGS, prior to session start. I thought all VDMs were class
>>2
>>priority, and the delta applied to all active VDMs in the system. More
>>investigation needed for this, I guess.
>
>Wow. After all these years, it's really refreshing to bump into an area
>of the system still totally unbeknownst to me as a user. :O
>
>Now, while programs expanding system capabilities as above (developers
>please confirm!) is something I am always happy to hear of, similar
>'expansions' may not work as intended in some areas. For some reason the
>system won't let you Cascade or Tile some windows, such as the Desktop
>itself, or the DHCP monitor from the Window list, and I just did it with
>lSwitcher. However, results do not always look 'happy' -- have a look at
>the screenshots.
The screenshots are irrelevant to cascade and tile. These only change the size and position of the program relative to the desktop. Many programs do not allow this (not my problem).
If you wish to convince me there is a problem you need to show me a case where what happened is different than using cascade or tile from the window list.
That mean a full screen screen shot before the tile or cascade and a full screen screen shot post. You then need to start from the exact same position and size and repeat this with the windows list. If they are the same it is performing as designed.
>
>On a different note, I noticed it's much easier than I thought to make
>the legend of keys and functions clip at the popup window edges (see
>'clip' screenshot). Wouldn't this look better wrapped into two lines? I
>also noticed there are often other active hotkeys not shown, which is
>suboptimal for UIs (if users turn the option on but hotkeys are not on
>screen how will they ever learn them? you certainly don't expect them to
>read the manual, do you?). I think a legend that expands to two lines as
>needed will always hold everything comfortably.
Yes it is clipped and also wrong. I will look into it.
>
>And now that we're fringing RFE territory, something that I finally had
>the time to pinpoint before reporting:
>
>Help says "'Reduce Desktop workarea' /will/ fail " [with XCenter], and
>now lSwitcher actually prevents you from checking it with 'auto-resize'.
>I thought this would be because of the new XWP, but there must be
>some other reason -- I just checked a fresh AOS5055 (so newest XWP)
>with Andrei's last lSwitcher and it can reduce the Desktop workarea
>cooperatively with XCenter (see lsw_old), so no need to prevent users
>from checking this. I would consider this a regression.
>
>As for a real RFE, PM popup icons have a context menu that you can bring
>up by clicking on them with MB2. How about making the PM popup react
>to the same PM message coming from the keyboard? (Originally mapped to
>Shift-F10, can also be triggered on Windows keys with Styler).
The change is based on the documentation and I don't know how safe or consistent this is. Thanks
back to list