|
| | | 
StrataFrame Novice
 
Group: StrataFrame Users
Last Login: 10/12/2008 10:41:53 AM
Posts: 69, Visits: 1,282 |
| | Hi, please do the following steps on a BrowseDialog, even with StrataFlix: Click on 'Advanced Options' (bottom) Click on 'Search Fields' (button bar above) Click on 'Save' (dialog toolbar above) Click on 'Advanced Options' as many times as you like... This is really looking wired, isn't it? Thanks for your attention! :-) Friendly greetings, Ralph
|
| |
| | | 
StrataFrame Developer
Group: StrataFrame Developers
Last Login: Today @ 2:14:29 PM
Posts: 4,901, Visits: 4,886 |
| A couple of things.- Do you have write permissions to the HKEY_CURRENT_USER\Software\MicroFour\StrataFlix registry key?
- Are the search fields retained between each run of the browse?
- Do these fields appear this way after closing the browse dialog and then showing it again?
|
| |
| | |
StrataFrame Novice
Group: StrataFrame Users
Last Login: 10/12/2008 10:41:53 AM
Posts: 69, Visits: 1,282 |
| | Hello Trent, as fast as ever! :-) 1. Do you have write permissions to the HKEY_CURRENT_USER\Software\MicroFour\StrataFlix registry key? It has nothing to do with StrataFlix, this problem exists since I found it a few month ago. I use Windows XP SP2/3, and yes, I have write permissions to HKEY_CURRENT_USER\whatever... At least running as administrator should have done the trick, I think. 2. Are the search fields retained between each run of the browse? Yes, they stay in order. Seems I actually have write permissons to HKEY_CURRENT_USER\whatever... Do these fields appear this way after closing the browse dialog and then showing it again? No, after closing and reopening the browse dialog they are looking OK. Did you follow my steps to reproduce the problem? It would take only four or five mouse clicks... Thank you very much and friendly greetings, Ralph |
| |
| | |
StrataFrame Developer
Group: StrataFrame Developers
Last Login: Today @ 2:14:29 PM
Posts: 4,901, Visits: 4,886 |
| | OK...yes, I reproduced it. I will add it to a list to look at. Since this is not a major or catastrophic issue, it may or may not make it into the 1.6.6 build. But at any rate, we will add it to the list. Thanks. |
| |
|
|