wpf - avoid creating empty row in datagrid -


i'm having 2 classes cricket, football , list of observable collections of type object. based on condition want add object of type cricket/football observable collection. i'm not assigning data i.e creating , instance of class cricket/football , adding instance observable collections , binding ui. expectation is, i'm not assigning data instance of cricket/football, header has create in datagrid. found row default value of variables defined under respective class along row header i'm creating instance of class. how shall avoid creating void row datagrid header unaffected. 

<datagrid selectionmode="single" verticalalignment="stretch" itemssource="{binding itemsource, updatesourcetrigger=propertychanged}"  canuserreordercolumns="false" canuseraddrows="false" isreadonly="true" canuserdeleterows="false" canuserresizecolumns="false" horizontalgridlinesbrush="black" verticalgridlinesbrush="black" horizontalscrollbarvisibility="disabled" verticalscrollbarvisibility="disabled" />

edit

i think datagrid's canuseraddrows property set true. set false fix issue.

canuseraddrows="false" isreadonly="true"

edit : sorry. read question right now. it’s because observablecollection’s type object. show small sample understand how binding works in datagrid. collection should have public properties, datagrid bind columns it. if use collection type of object have no properies binding, empty rows displayed.

xaml :.

<datagrid autogeneratecolumns="false" height="253" horizontalalignment="left" margin="27,24,0,0" name="datagrid1" verticalalignment="top" width="448">             <datagrid.columns>                 <datagridtextcolumn header="first" binding="{binding path=field, mode=twoway, updatesourcetrigger=propertychanged}" />             </datagrid.columns>  </datagrid>

code behind :

public partial class mainwindow : window  {      public observablecollection datasource;     public mainwindow()     {         initializecomponent();          this.datasource = new observablecollection<somedatasource>();          this.datasource.add(new somedatasource { field = "123" });         this.datasource.add(new somedatasource { field = "1234" });         this.datasource.add(new somedatasource { field = "12345" });          this.datagrid1.itemssource = this.datasource;     } }  public class somedatasource {     public string field {get;set;} }

Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more