20 results for "how-to/custom-value-editor-winforms"

Value Editors

/data-model-editor/value-editors

Here you can find the full list of editors and choose any you need in your work with Data Model:

Processing custom value editors in EasyQuery JS

/how-to/custom-value-editor

Here you can find tips how to value editor setup and how to value editor widget

Processing custom value editors in EasyQuery JS

/how-to/processing-custom-value-editors-in-easyquery-js

First, of you will need to assign a custom (user-defined) value editor for some attribute or operator in your data model. You have to ways to do it: Run Data Model Editor (DME). Select an entity attribute which you want to assign custom value editor to. You can add a custom editor to any entity attribute in your model at run-time. Here is an example of very simple value editor in TypeScript.

Introduction to value editors

/fundamentals/about-data-editors

For example, value editor allows you to define a list of available values - so your users will be able to select the value from a drop-down list. "Custom list" value editor raises an event which can be processed either on the client-side or on the server. All other editions of EasyQuery (WinForms, WebForms, WPF or Silverlight) has ListRequest event in QueryPanel control which is raised when a user adds an attribute (or operator) with Custom List or SQL list value editor assigned to that attribute/operator. Here we show how you can filter the returned list according to the value specified for some other attribute. If such condition is defined - we get the value (country code) from it and use that value as a filter for the list of regions.

About Data Model Editor

/data-model-editor/about

Here you can find detailed information about this instrument and guideline, how to use it to perform all needed tasks.

Customizing common SQL clauses

/how-to/customizing-common-sql-clauses

This article is about settings for adding different options to the whole query (like DISTINCT, LIMIT, etc)

Upgrading to 5.x: WinForms and WPF projects

/upgrade-instructions/net4-editions-from-3-x-to-5-x/winforms-and-wpf

This tutorial describes how to modify your old Windows Forms or WPF project with EasyQuery 3.x to upgrade to EasyQuery version 5.2.0 (or higher). Please note. Version 5.2.0 of EasyQuery works only on .NET Framework 4.6.1 or higher. So, if your project targets a lower version of .NET Framework - you will need to update Target Framework for your project first (right-click on the project in Solution

Customizing SQL query formats

/how-to/customizing-sql-query-formats

Detailed instruction with various examples of how to operate with different query formats.

Date/time values formatting

/how-to/date-time-formatting

In this article, you can find instructions how to set up different types of date & time formats, with code examples.

Dynamically populate value lists by information from other conditions

/how-to/dynamically-populating-lists-mvc

Suppose we have a database with Customer entity which has Country and City attributes. For both these attributes we define the value editors which return the lists of available values (countries and cities correspondingly). Now let's imagine the user adds a condition with the Country attribute e.g. Hera the steps needed to implement such a functionality: Define a value editor for the City attribute as SQL LIST with Cities.@{{Customer.Country}} list name (here Customer.Country is the ID of the Country attribute in the Customer entity). Let's name it "CitesSqlValueList") and then in a value list resolver modify its SQL according the currently selected country and get the list of values using GetValueListAsync method of EasyQueryManager class: What's happening here.

Custom client-side dialogs

/tutorials/custom-javascript-dialogs-saving-loading

Users who use some other dialogs libary usually want to replace those default dialogs with their own. We are going to replace those default dialogs with nice HTML dialogs made with JQuery UI dialogs library. The approach we will use is quite simple: our AdvancedSearchView JavaScript class has several methods which can be "overriden" to replace the default behavior with your own implemenation of those dialogs. In case of using JQuery dialogs we need to define some placeholders (read div elements) on our page where our new dialogs will be rendered. Here is an example: NB: Please note that this step is specific for JQuery dialogs.