Bluepoint Design

Practical Cost-Effective Solutions


Variable Type column missing in Variables tab of scripting editor

Experienced on IPSD TS. Still a problem after supposedly fixed in build 99.

Tried reg hacks to no avail. Restoring program defaults worked. I think somehow the column was zero width. Although my problem is gone I'm not certain that the bug that caused it is fixed.

Solution:

  1. Open Macro Explorer
  2. Click Tools, Export Program Configuration
  3. Save to a file
  4. Close Macro Explorer
  5. Right-click on the system tray icon
  6. Click Tools, Restore Program Defaults
  7. Import Program Configuration from previous file.

ISS has marked this as resolved in their tracking system but I believe that some bug is responsible for this condition and therefore should not have been removed.

2009/02/21 1149 I made it happen yesterday. In a var selection box I dragged the Type to the header and it disappeared. I did the workaround and it was back. Have been unable to reproduce.

2009/05/18 1640 Just had it happen again on the TS. Type was up top and I dragged it down onto the Variable Name header and it simply disappeared. I messed around with the \$Temp\Grids\EditorVars\frmeVars.cxView\ values to no avail. Did notice that cxType\Visible = False. Setting to "True" did not fix the problem. I deleted the entire $Temp key and that caused the "Type" to go back up to again. But this time when I dragged and dropped it on the header it worked and was visible. I looked again at the Grids\EditorVars\frmeVars.cxView\cxType and all of the index numbers and such looked the same as they were before.

[HKEY_CURRENT_USER\Software\Insight Software Solutions\Macro Express 4\$Temp\Grids\EditorVars\frmeVars.cxView\cxType]
"GroupIndex"=dword:ffffffff
"Width"=dword:00000072
"AlignmentHorz"=dword:00000000
"Index"=dword:00000000
"Visible"="\"True\""
"SortOrder"="\"soAscending\""
"SortIndex"=dword:00000000
"WasVisibleBeforeGrouping"="\"False\""

 

After some experimentation I think my troubleshooting was flawed. MEP does not write the values to the reg until the editor is closed. Duh. So that means when I was first looking at the reg it was not reflecting values that might have been during the invisible state. Next time I'll try to do that first.

 

 
Practical Cost-Effective Solutions