Empty strings are not rendered by the browsers and measure 0,0. The list items in the combo box don’t have a minimum height because Wisej supports variable height items. You can either use the html symbol for non-breakable spaces &nsbp; or set the minimum height of list items in the theme or a mixin.
The min height value depends on your app the font, etc. I’d use 22 or use
{
"appearances": {
"listitem": {
"inherit": "listitem",
"states": {
"default": {
"properties": {
"minHeight": 20
}
}
}
}
}
}
If you change the AppearanceKey then you have to restore it. Try
public string HobbsAlert => HobbsFinish == HobbsStart ? “textbox” : “required”;
Wisej only renders the changed apperance key name.
You’re right. I will do some extra research, using some custom extensions (adding some custom wisej extensions (dll) to vs references), tourpanel never shows and throw some javascript errors, maybe something about jquery. Seems some issue in jquery compatibility or something else (jquery used inside custom wisej extension (package))
007207 Wisej: onActionCreate Error creating: { false, false, wisej.web.ext.TourPanel, null, [...(3)], false, false, true, false, 500, null, true, id_20, true, TourPanel, null, false, false, 0, false, true, }
qx.log.appender.Native.process() @ qx.js?v=1.4.80.0:180294
qx.log.Logger.__log() @ qx.js?v=1.4.80.0:15638
WisejQX.log @ wisej.js?v=1.4.80.0:52550
WisejCore.log @ wisej.js?v=1.4.80.0:1997
WisejCore.logError @ wisej.js?v=1.4.80.0:1951
onActionCreateClosure @ wisej.js?v=1.4.80.0:699
WisejCore.onActionCreate @ wisej.js?v=1.4.80.0:727
processResponseClosure @ wisej.js?v=1.4.80.0:510
(anonymous) @ wisej.js?v=1.4.80.0:543
setTimeout (async)
WisejCore.processResponse @ wisej.js?v=1.4.80.0:541
WisejCore.onAjaxRequestComplete @ wisej.js?v=1.4.80.0:1746
ws.onmessage @ wisej.js?v=1.4.80.0:1622
Thank you very much for your support, it was useful!!
It’s working fine. It seems that Inser(-1, tab) messes up the tab visibility. Will log the bug. In any case, the correct call is TabPages.Add().
Hi, I’m attaching an example of the error. I appreciate helping me because I have many system users without working.
Hi,
I’m resurrecting this thread with a related issue.
I have implemented the “required” functionality sucessfully in code, however there seems to be a bug when databinding …
With the following property in the bound entity:
public string HobbsAlert => HobbsFinish == HobbsStart ? “” : “required”;
And the following binding:
this.textBox1.DataBindings.Add(new Wisej.Web.Binding(“AppearanceKey”, this.bsLesson, “HobbsAlert”, true));
It works until the first “required”, ie. the textbox remains normal while moving through records without a HobbsAlert, but as soon as one is encountered the textbox goes red (correctly) but then remains red regardless of HobbsAlert.
Cheers,
Neil
Hi Sergio,
tried reproducing with copy-pasting your code and it seems to work fine here. (see attached sample).
What type of error do you get ?
Best regards
Frank
Hi Carina,
I can’t reproduce and as you said it “happens only with some buttons”. So a sample with buttons where this happens would be really useful.
Hi Saul,
it seems that the TinyEditor is not maintained much anymore. Find some information here: https://github.com/jessegreathouse/TinyEditor
You could try using the TinyMCE editor. There are spell checker plugins available for it.
Best regards
Frank
Attached sample, anyway this.validate() solved the accelerator problem.
Thanks.
Thanks. The problem is that there was a bug in the toolbar that causes the control with the focus to lose the focus when clicking a button in the toolbar, which then in turn caused the Validating events on the control losing the focus, which activated the data binding. That has been fixed so the toolbar buttons do not steal the focus and do not cause validation.
Data binding can get updated in three ways: Never, OnPropertyChange or OnValidation. See DataSourceUpdateMode, it’s the last optional argument in new Binding(). The default is OnValidation.
We also added CausesValidation to the toolbar. So you can either change the binding to OnPropertyChange which will update the data source on each Value change, or set this.toolbar1.CausesValidation = true, which will validate when you press Ok without stealing the focus.
There is also a different behavior (which is identical to WinForms – but I think we probably want to change it) between modal dialogs and forms – modal dialogs do not trigger validation when closed and close even if a field fails validation, while forms always validate the active control and refuse to close if validation fails.
sorry if I did not explain well.
the checkbox that I have crate and place inside datagridview, are not checkable. is it normal, because it is in virtual mode?
Ok right, but anyway if I do
Me.Wallpaper =”….”
the “bingwallpaper” is over the image
Attached.
You can find a downloadable demo here:
https://wisej.com/blog/time-for-a-cool-smoothie/
Extensions are provided with the full source code because they are not meant to be the full integration of whatever third part widget they integrate and are available to the developers to customize, extend, change however needed in their projects. Each third party widget has its own documentation, features, and bugs which are not ours… thankfully 🙂
Hi Luca,
I downloaded the demo but it won’t compile/run because I’m missing Wisej.Web.Ext.SmoothieChart reference.
In my references, this has an exclamation mark on it!
I can’t understand what the code is expected to do. The checkbox is created and not shown or attached or assigned. Place it on a page or form and it will work. It’s not related to the DataGridViewCheckBoxColumn.
The datagrid sets VirtualMode on but doesn’t handle the data events. See https://docs.microsoft.com/en-us/dotnet/framework/winforms/controls/implementing-virtual-mode-wf-datagridview-control
You don’t need that. Every control has the BackgroundImage* properties. The Control property in the BingWallpaper component is not a BingWallpaper control, it’s the control being targeted by the component. In the case of a Desktop it can be left null.
ok temporary solution with
BingWallpaper1.Eval("qx.bom.Stylesheet.removeSheet(this.__stylesheet);")
BingWallpaper1.Dispose()
bye
Cristian
