Then suddenly the notepad will no longer be placed in the foreground and the «stay always-on-top» option will no longer be checked. The test will require no more than 10 launches the first few times, the notepad will open in the foreground and by right-clicking on the title bar the «stay always-on-top» option will be checked. It's quite simple to check: create a rule so that the notepad always launches in the foreground, then launch the notepad several times, and each time check if AWM has placed it in the foreground by right-clicking on the title bar. Occasionally, often in fact, AWM will not behave as expected. For example, if a simple rule specifying that the notepad should always launch in the foreground is set, with a registered name other than RadiXX11, AWM will not always enforce the rule. I made extensive tests to come to this conclusion: if AWM is registered with a key generated by the keygen of RadiXX11 and with any name except RadiXX11, the registration is successful, but AWM will randomly apply the behavior rules of windows. However, I noticed an erratic behavior of AWM over the versions that I didn't understand. I've been using AWM for years and always registered it with RadiXX11 keygen using my first name. I made a discovery with Actual Window Manager.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |