I have begun evaluating Creo 7 and have noticed that any mapkey that imports a config file is creating flashing windows when executed. These same mapkeys did not cause flashing windows in Creo 4.
I have the config option visible_mapkeys no this has no affect on the behavior of these windows in Creo 4 or 7 in the context of the mapkeys in question. Does anyone have any idea as to why the windows are now visible in Creo 7? Any ideas on how to not have mapkeys create any visible windows unless pausing for input?
This is the mapkey that is the root cause of the behavior. Every mapkey that has this nested into the definition causes flashing windows to appear.
!* Load config file mapkey .ifcp @MAPKEY_NAMEImport config .pro;@MAPKEY_LABELRead config;\ mapkey(continued) ~ Select `main_dlg_cur` `appl_casc`;~ Close `main_dlg_cur` `appl_casc`;\ mapkey(continued) ~ Command `ProCmdRibbonOptionsDlg` ;\ mapkey(continued) ~ Select `ribbon_options_dialog` `PageSwitcherPageList` 1 `ConfigLayout`;\ mapkey(continued) ~ Select `ribbon_options_dialog` `ConfigLayout.ImportExportBtn`;\ mapkey(continued) ~ Close `ribbon_options_dialog` `ConfigLayout.ImportExportBtn`;\ mapkey(continued) ~ Activate `ribbon_options_dialog` `ConfigLayout.Open`;\ mapkey(continued) ~ Trail `UI Desktop` `UI Desktop` `DLG_PREVIEW_POST` `file_open`;
I just ran your mapkey in Creo 4 and Creo 7 and the behavior appeared to be the same for me.
I had visible_mapkeys set to no for both tests.
Let me clarify some important context in that this mapkey run on its own is not the root cause.
Every mapkey that has this (mapkey .ifcp) nested into the definition causes flashing windows to appear. The windows are opened and closed by the mapkey causing the flashing.
Here is an example of it in context of a nested mapkey sequence. As you can see the window is invoked and closed in the sequence. Up to Creo 4 these windows are not visible when the nested mapkeys are run. I have not tested them in Creo 5 or 6.
!*selection glow mapkey $F4 @MAPKEY_LABELGlow Toggle;%.ifcp;\ mapkey(continued) ~ Input `file_open` `Inputname` `D:\\ProE Standards\\Config \ mapkey(continued) Calls\\on_glow.pro`;\ mapkey(continued) ~ Command `ProFileSelPushOpen_Standard@context_dlg_open_cmd` ;\ mapkey(continued) ~ Activate `ribbon_options_dialog` `OkPshBtn`;
ok can confirm I see the same white windows briefly flash in Creo 7. I ran in Creo 188.8.131.52.
I created a mapkey with your original mapkey and then created another mapkey that called importing that first mapkey file.
Given that we can both see it, it is part of the software and likely not some configuration option. If you want to try your luck you will need to open a ticket with PTC although I wouldn't get your hopes up about them changing it back.
Thx for confirmation. I have an open call with support. I will post the result of the support ticket here when it is closed.
Latest response from tech support. The latest benefit of making Creo MS windows compliant? Please ask as many people as you can to vote for the enhancement so this is corrected.
P-50( Creo 5.0) lets Windows 10 add the desktop window manager glow to the borders of its windows. When Windows does that it changes the composition level of the window, which affects the timing etc. of things such as map and unmap. What you are seeing in P-50(Creo 5.0) is surely the fact that Windows takes marginally longer now to show/hide a window.
Enhancement voting link:
This is the response I got back from R&D. No explanation of why the new behavior is now correct. I will add a request for enhancement but it will go nowhere without voting it up. Link to the idea:
R&D has added the following comments:
The new behavior is correct and we do not currently have any option to hide UI during mapkey replay. If there are number of requests coming in from various customers ,we could always investigate such a possibility in more detail. Also we don't even know in how many cases UI wouldn't be shown in earlier releases– it may have been very machine and mapkey dependent and for some mapkeys it may be shown.
In short, this will be considered in future based on the number of requests coming in from the customers. Let me know if you have any queries.