This question is locked. New answers and comments are not allowed.
OpenAccess modal windows drive me MAD! By this I mean the OQL browser and the Reverse Mapping window.
The following changes to the OQL browser would make life so much easier.
The following changes to the OQL browser would make life so much easier.
- Don't make the window modal. There are plenty of times when I am testing classes, etc where I type in the OQL command and then need to reference something in the VS project. The only way to do this is to save the query, close the OQL browser, get the info I need from the VS project, open the OQL browser and open the saved query.
- If a query is opened from disk, persist the name of the file so that when the user choses to save, the filename is already entered into the filesave dialog.
- Allow drag + drop from the persistant model tree to the OQL window.
- Save the size and position of the OQL browser window.
Reverse Mapping Window:
- Again, don't make this modal for the same reasons as above.
- I use Visual SourceSafe which causes an issue when regenerating classes. In our current project there are 84 tables. Without a checkall facility to select/deselect the classes to regenerate (I know this is coming in the next release, or at least I am led to believe this), manually selecting the classes to generate and clicking the Generate/Save button results in an error saying that the existing files are read-only. The only option then is to quit the reverse mapping window losing all the changes to the checked classes to generate because reversemapping.config is read-only, check out the relevant files, open the reverse mapping window and again go through the entire process of checking/unchecking the classes. Could OpenAccess not force a checkout, or provide some other solution to solve this issue? It is extremely frustrating and time-consuming to have to work this way.
Regards,
Jonathan