Hi Christian,
This is a known issue we are working on addressing!
Please try some of these solutions:
Please let me know if this solves your issue!
Best Regards,
Levie
Hi Glenn,
Thanks for reporting! The fix will be available in the next release.
Best regards,
Levie
Ok.
Hi Simone,
this is fixed in Wisej 2.0.24.
Best regards
Frank
Hi Gabriele,
it´s fixed in the latest Wisej release (2.0.24).
Best regards
Frank
Hi Eric,
this should work (again) with our latest releases (1.5.58 and 2.0.24).
Best regards
Frank
Hi Benjamin,
The NavigationBarItem components are not working in 2.0.13, but the component has been updated since then (and is working in all updated versions of Wisej).
You can find all of the extensions as open source projects on https://github.com/iceteagroup/wisej-extensions/ . I’ve also attached a copy of the dll.
To get the latest working version and use it from GitHub:
Please let me know if this solves your problem!
Best regards,
Levie
Hi Benjamin,
I’m sorry you’re getting this error!
Please try the following solutions to see if one (or more) solve your issue:
If none of these work, could you please attach your sample solution?
Best Regards,
Levie
Hi,
Will this update be available for version 1.5.x?
Thanks
Frozen rows aren’t available yet, but they will be sometime in the future!
You can add a second datagridview on top of the first one and dock it to the bottom. The datagridview will automatically adjust and make space for it. You can then add events to the column width changed events to keep them in sync.
The following code will help you calculate the total of the visible cells (You can modify to get certain column):
public void GetVisibleCells(DataGridView dgv)
{
var visibleRowsCount = dgv.DisplayedRowCount(true);
var firstDisplayedRowIndex = dgv.FirstDisplayedCell.RowIndex;
var lastvisibleRowIndex = (firstDisplayedRowIndex + visibleRowsCount) - 1;
for (int rowIndex = firstDisplayedRowIndex; rowIndex <= lastvisibleRowIndex; rowIndex++)
{
var cells = dgv.Rows[rowIndex].Cells;
foreach (DataGridViewCell cell in cells)
{
if (cell.Displayed)
{
// This cell is visible...
// Your code goes here...
}
}
}
}
I hope this helps! Let me know,
Best regards,
Levie
Hi Levie,
thanks for the reply, for the moment i found a solution by adding to the drop down the Event DropDown (when the portion of drop-down was shown) and into the event i call the javascript code only for android as IOS devices works:
this.Eval(“document.querySelectorAll(‘[opener=\”myComboBoxName\”]’)[0].addEventListener(‘touchmove’, function (e) { e.preventDefault(); e.stopPropagation(); })”);
with this trick when oppen on android device the scrolling of combobox items seems works.
Maybe this trick can help you.
Best regards
Hi,
We are still working on ways to increase the fluency of scrolling on mobile and overall compatibility with mobile, but don’t have a great solution yet.
This JavaScript library could be useful for you if you want to limit the over scrolling of the page:
https://github.com/lazd/iNoBounce
You can also add:
“options”: { “mobile.mode”: true }
to your Default.json file to enable experimental mobile features.
If you have fewer than 100 items in your DropDown, you could try playing with the ComboBox.DropDownHeight property to show them all and just scroll your normal page that way.
We hope to improve this feature in the future!
Sorry I couldn’t be more help, I’ll keep you updated if I find another solution!
Best regards,
Levie
Hi Glenn,
If your DataGridView is unbound: one way you can accomplish this is to programmatically add a new row to the bottom:
var index = dgv.Rows.Add();
dgv.Rows[index].Cells["Column1"].Value = "Column1";
dgv.Rows[index].Cells["Column2"].Value = 5.6;
If your DataGridView is bound you can use a DataTable:
DataTable dt = myDataGridView.DataSource as DataTable;
//Create the new row
DataRow row = dt.NewRow();
//Populate the row with data
//Add the row to data table
dt.Rows.Add(row);
To calculate the totals of the columns:
int sum = 0;
for (int i = 0; i < dataGridView1.Rows.Count; ++i)
{
sum += Convert.ToInt32(dataGridView1.Rows[i].Cells[1].Value);
}
label1.Text = sum.ToString();
Some useful links:
Calculating Sum of Column: https://stackoverflow.com/questions/3779729/how-i-can-show-the-sum-of-in-a-datagridview-column
Adding Row to DataGridView Programmatically: https://stackoverflow.com/questions/10063770/how-to-add-a-new-row-to-datagridview-programmatically
DataBound DGV Row Adding: https://stackoverflow.com/questions/18125147/how-to-programmatically-add-a-row-to-a-datagridview-when-it-is-data-bound
I hope this helps! Let me know if you have any questions about it!
Best regards,
Levie
Thank you.
Will be fixed in the next release.
Best regards
Frank
The Widget.Options object is the initialization JSON object. Changing it’s properties doesn’t update the widget. It depends on the the widget and the integration. Most javascript widgets cannot update their initial configuration and have either specific methods or need to be destroyed and recreated.
Also, when interacting with the widget, it doesn’t update the options. The configuration options and the widget behavior can be very different.
It works the first time because Wisej (both client and server side) only update the differences.
In this case, you can handle the MapPropertyChanged event to receive updates from the google map widget:
private void MobjGoogleMap_MapPropertyChanged(object sender, Wisej.Web.Ext.GoogleMaps.MapPropertyChangedEventArgs e)
{
if (e.Name == "zoom")
mobjGoogleMap.Options.zoom = (int)e.Value; // in case you want to keep track like this, or use a different variable.
}
To update the zoom level on the client use:
mobjGoogleMap.Call("this.map.setZoom", 16);
The method to call to update a property depends on the widget.
Levie, to make your sample reproduce the bug, call the ZoomInLocation function with a fixed zoom level, like 16.
1. Click button (notice what “zoom level 16” looks like)
2. Zoom out several levels
3. Click button again —> zoom goes maybe 1-2 levels, not to “zoom level 16”
Your original code didn’t show the bug, but my modifications made the error. Also I pass in the “fudged” new latitude, just like my sample code, but that didn’t make the difference.
Hi Levie,
I’m using Wisej 2.0.13.0 and i still have the issue even with the latest Update of Firefox 66.0.3.
I’ll wait for the release of Wisej 2.0.22 then.
Best regards,
Alex.
Hi Alexandru,
I tried running your solution on Firefox and didn’t get any issues with the latest version of Wisej (2.0.22 in development).
Please let me know if you still have issues after upgrading to the latest version!
Best regards,
Levie
I cannot open the sample.