OpenAccess Modal Windows

4 posts, 0 answers
  1. Jonathan Simmons
    Jonathan Simmons avatar
    107 posts
    Member since:
    Jun 2005

    Posted 24 Feb 2009 Link to this post

    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.
    • 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

  2. Ady
    Admin
    Ady avatar
    588 posts

    Posted 24 Feb 2009 Link to this post

    Hello Jonathan,

    Please find some explanation regarding your comments below

    1) OQL query browser - The way the browser works is that we load the compiled assembly (and other referenced assemblies) for the project in a new AppDomain and execute the specified OQL query. The browser requires the assemblies to be built. Making the dialog modeless would mean that you cannot make some changes to the sources while the browser is open, compile and use the browser with the compiled changes.
    What is the information that you frequently need from your VS project? Maybe we can provide that within the browser so that you don't feel the necessity to go back to VS. Regarding the query file name and size and position, we will definitely implement those suggestions.

    2) Reverse mapping - The 'Select All' option will be available in the next release. In the meantime could you use 'Ctrl+A' within the grid to select all the rows and then check the 'Generate Selected Classes' checkbox. I agree the wizard is not easy to use with source controlled files. This is a scheduled item and we are actively working on implementing a solution for this.

    Sincerely yours,
    Ady
    the Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
  3. DevCraft banner
  4. Jonathan Simmons
    Jonathan Simmons avatar
    107 posts
    Member since:
    Jun 2005

    Posted 24 Feb 2009 Link to this post

    Hi Ady, thanks for your very prompt reply.

    OQL query browser: I understand that the browser loads the current object model, but no changes can be made to the underlying model anyway since the browser is modal at the moment. If the browser were to be modeless, why not place a Refresh button on the toolbar to refresh the model if there are changes to the classes? In terms of the modal nature of the browser, my solution contains a number of projects and to disallow access to any part of VS is really a pain.

    Regards,
    Jonathan

     

  5. Ady
    Admin
    Ady avatar
    588 posts

    Posted 24 Feb 2009 Link to this post

    Hi Jonathan ,

     Keeping the dialog modless would mean 'locking' all the referenced assemblies till you press the 'Refresh' or maybe 'Unload' button. Maybe not a very convenient thing to do whenever you want to build the solution.

     We will definitely consider your suggestion and keep you informed.

    Best wishes,
    Ady
    The Telerik team

    Instantly find answers to your questions on the new Telerik Support Portal.
    Check out the tips for optimizing your support resource searches.
Back to Top