Hi thanks for comment Us about it
When these feature will be released in vs2919 (not preview 😉 ) we will make a test
Wisej must compatible with vs2015 and 2017 too and these new feature is about vs2019 only 🙁
Regards and happy coding
Hi Huynh,
you can use a ClientEvent to achieve this.
Please add the following to your TextBox.ClientEvent on e.g. KeyUp:
if (this.getValue().toUpperCase() == "HELLO") this.selectAllText();
Find more information here:
https://wisej.com/support/question/textbox-selectionlength-attribute-always-0
Best regards
Frank
I found the solution already, thanks.
The error is coming from IIS. It’s not a Wisej issue.
I tried using POSTMAN, it gives me the same error, please see attached image.
Hi,
After searching I found this link
Excerpts:
Updated:
Thank you for the update. The “method: put. method not allowed.(405)” error is a generic HTTP error that occurs on the server side and it is not related to our components. Our components are client-side and we do not have any control under the server implementation.
Thanks.
Hi,
But I noticed when I set the URL to webservice not using this.getPostbackUrl(), it’s working fine. I tried the suggestion from stackoverflow, but it’s not working.
Thanks.
Hi Glenn,
this does not seem to be a Wisej issue.
Find more information here:
https://stackoverflow.com/questions/6147181/405-method-not-allowed-in-iis7-5-for-put-method
Best regards
Frank
Hi Glenn,
this.dataGridView.Columns[“yourcolumn”].ReadOnly = true;
Just tried with a checkbox column and it works ok.
Can you please send a small test case?
TIA
Frank
OK, got it to work using the WidgetFunction, entering the following:
return App.FornecedoresMaintenance.tcView.tpGrid.dxDataGrid1.widget.state();I saw the this.Instance.state() in the DevEx Sample solution from Wisej GitHub. Why is it it works in that case?
Cheers.
Ivan
Thank you very much for your answer, however what I want is to hide only the upper part of the tabcontrol, where the titles of the tabs are.
I have done it by adding the Stylesheet component to my window and putting the code in it:
div.qx-widget-barTop {display: none}
but this makes it affect all the tabcontrols in the form, and I only want it to affect one.
It’s possible?
Thanks a lot for your sample.
A final question regarding your implemented solution: Will the server resources (session) be freed even when the javascript dialog stays displayed in the open browser tab ?
The problem PDF export of the grid was just solved. Thank you! We may close the case!
Hi Jesus,
yes, just use the Hidden property.
Find more about how Wisej extends the TabControls here:
https://wisej.com/blog/extended_tabcontrols/
Best regards
Frank
All my customers that use chrome or edge have this problem with my wisej portal 2.2.48.
For example with wisej 2.2.47 I have not this problem, then it is a Wisej issue only with 2.2.48
Wisej 2.2.48 read old cookies saved with previous version of Wisej but don’t save correctly, at chorme/edge close it loose the cookie.
best
Cristian
this.dxDataGrid1.Eval(@”
window.jsPDF = window.jspdf.jsPDF;
applyPlugin(window.jsPDF);
var dxDataGridinstance = $(‘.dx-gridbase-container’).parent().dxDataGrid(‘instance’);
//console.info(dxDataGridinstance);
const doc = new jsPDF();
window.DevExpress.pdfExporter.exportDataGrid({
jsPDFDocument: doc,
component: dxDataGridinstance
}).then(function() {
doc.save(‘Customers.pdf’);
})”);
This code partially works. At least do not generate error messages. But the grid just blinks once and nothing happens. What can be done to make it working?
DevEx refuse any support as they say they do not support Wisej platform. So you are my only hope. PDF export of the grid is vital for reporting model of my application.
Thank you!
Hi Praveena,
Thank you for reporting this issue.
We’re currently investigating it and we’ll get back to you with a response soon!
Best regards,
Alaa
Hi Tobias,
I create a sample for this case.
Best,
Kevin (ITG)
Hi @all,
I miss the important detail: close the browse and reopen it
Chrome and Edge lose the cookies.
I attach sample
best
Cristian
Hi Cristian,
in addition to Alaa´s answer, please also check your Chrome and Edge cookie setting.
Maybe they have changed to block cookies?
Best regards
Frank