Hello @xeo4.it!
I believe there's several ways you can do that. But it depends on how your application is drawn.
For example, if you use in WebForms a shared viewport (or panel) for all your pages, you can just set:
<Defaults>
<ext:Parameter Name="enableTextSelection" Value="true" Mode="Raw" />
</Defaults>
But that's going to affect not just views within, but anything that supports this setting.
In MVC, if you use a shared layout, you could also use a similar approach.
Another alternative, if using free and arbitrary layouts on your page, would be to pull a custom client-side script to apply the setting to any view on grid panels throughout the page. Would involve getting all the view components after page is loaded.
As the component instances are independent, you can't really set the gridview's EnableTextSelection="true" from global.asax, for example. Instead, modifying Ext.NET server-side code so that it always imprints this value would be a reliable solution across the program, but would require you to always run a custom-built Ext.NET code.
In a similar approach, you can extend the Ext.NET component and make it always output
EnableTextSelection="true", but this one wouldn't be really helpful as you would probably need to change the component reference (for example, from
<ext:View /> to something like
<mySpc:View />) and well, if you need to do this then you could just add the setting to everyone.
Well, and another option would be to edit an Ext.NET override for the view component, setting this as default, always. This will have some complexity for the first time you do and will also require to keep a custom-built Ext.NET version.
Similar to above, you can just add an override similar to this:
Ext.define("my_overridden_view_defaults", {
overrides: 'Ext.view.View',
enableTextSelection: true
});
And have this code injected (the .js file run or attached to the file) to every page you load (by a shared view or master page, maybe).
Well, so there's a lot of ways to do so, but I can't think on a way, for this kind of default override, setting on
global.asax or something like it (app_start, web.config...).
I hope one of the alternatives above is feasible for you.