All Answers

0 votes

Thanks Frank and Luca, awesome support!

  • Mariano answered Nov 12, 2016 - 12:22 am
0 votes

Hi Mariano,

please note that we added AutoComplete property to TextBox to make it use/deny browsers autocomplete.

We also added TextBox.AutoCompleteList that allows to set any list to be used for auto completion.

Both are included with our latest build (1.3.6.)

Best regards
Frank

0 votes

Hi Michael,

this problem is also fixed in our latest build (1.3.6).

Best regards
Frank

0 votes

Hi Michael,

the problem is fixed in our latest build (1.3.6).

Best regards
Frank

0 votes

Hi Frank,

I did not get a notification. I just checked manually. Also, when installing the update it could not kill the AutoUpdater. It was removed from the taskbar icon list but not from memory. I had to kill in task manager to finish the update.

Thanks,
Robin

  • Robin answered Nov 11, 2016 - 10:24 pm
0 votes

Great, thanks Robin.

Did you receive a notification of the AutoUpdater for 1.3.6 ?

Regards
Frank

0 votes

Confirmed fixed in 1.3.6

Thanks!
Robin

  • Robin answered Nov 11, 2016 - 10:14 pm
0 votes
In reply to: Address Lookup

Hi Ewan,

we are working on a Wisej version of your sample and will send you the code next week.

Best regards
Frank

0 votes

Hi Michael,

Modal workflow works fine, the code is suspended and when you click OK it resumes. It’s the return code that doesn’t work because of a bug that tries to parse “ok” to “Ok” and then DialogResult.OK (all uppercase). If you change the button to Yes you can see that it’s parsed. This is fixed in the current (pending) update.

Best,

Luca

  • Luca answered Nov 11, 2016 - 8:53 pm
0 votes

Fantastic, a developer that reads the documents. 🙂

You can either fire a message to a control or call a remote method.

Best,

Luca

  • Luca answered Nov 11, 2016 - 6:32 pm
0 votes
  • Antonio answered Nov 11, 2016 - 6:25 pm
0 votes

Hi Gunter,

The scrollbars are displayed when AutoScroll = true. It’s the same in WinForms and Wisej, I don’t know about VWG, I can’t run it anymore. Otherwise the controls are truncated, the flow layout panel doesn’t resize the child controls unless they are anchored.

Best,

Luca

  • Luca answered Nov 11, 2016 - 3:43 pm
0 votes

Hi Michael,

I could reproduce and logged bug WJ-7767 for it. We will inform you when it´s fixed.

Best regards
Frank

0 votes

Hi Luca

ok that’s the behavior of winforms, in VWG the FlowLayoutPanel shows ScrollBars, when the contained controls exceed the size of the FlowLayoutPanel

Sorry for the xx, i misend something

  • Gunter answered Nov 11, 2016 - 3:34 pm
0 votes
In reply to: Solved: AspNetControl

Hi Luca

Having tested your example with some of my server reports I have noticed the following:

  1. In IE 11 you have to press the page icon twice to change the page (once in Chrome)
  2. In IE 11 if you have linked parameters picking one does not cause the others to update unless you press refresh report
  3. After you have changed parameter values having run the report once you have to press refresh report twice to get the report to redisplay.
  4. If you are just working within the report window you get the session timeout message.

So it appears that something is preventing report viewer from running independently (I have set AsyncRendering to true).

These issues were not present in the VWG wrapper.

This issue seems to be, having looked into this further that OnInit is not firing reliably.

Thanks for your help

Ewan

  • Ewan Walker answered Nov 11, 2016 - 10:07 am
  • last active Nov 11, 2016 - 11:52 am
0 votes

Hi Michael,

did you add your keys to existing <appSettings> section or added another one ?

Having more than one <appSettings> section will fail.

Can you please post your complete web.config or send it to me: frank@iceteagroup.com

Thanks in advance.
Frank

0 votes

Hi Luca, has the guide been published yet?

  • Andrew Niese answered Nov 10, 2016 - 9:35 pm
0 votes

Hi Mariano,

Good question. We will add the AutoCompleteType property to the TextBox class. However, modern browsers more or less all ignore this attribute, but there are some workarounds, see https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion.

You can easily patch the base javascript class that creates input elements in wisej by addin this code in Default.html:

<!DOCTYPE html>
<html>
  <head>
    <title></title>
    <meta charset="utf-8" />
    <script src="wisej.wx"></script>
    <script>
        Wisej.onLoad = function () {

          // define the MAutoComplete mixin
          // to override the _createInputElement method.
          qx.Mixin.define("MAutoComplete", {
            members: {

              _createInputElement: function () {
                return new qx.html.Input("text", null, { autocomplete: "off" });
              },
            }
          });

          // patch the textfield base class using the MAutoComplete mixin.
          qx.Class.patch(qx.ui.form.AbstractField, MAutoComplete);
      }
 </script>
</head>
<body></body>
</html>

 

You can add more attributes and  and choose the value to set.

Best,

Luca

 

  • Luca answered Nov 10, 2016 - 8:39 pm
0 votes
In reply to: Toolbox

Hi Ewan,

copy of my answer to the AspNetControl:

the base class AspNetControl is not a UserControl and has the attribute [ToolboxItem(false)].

So derived components to appear in the toolbox must have the attribute [ToolboxItem(true)] and may have to be added to the toolbox.

Hope that helps.

Best regards
Frank

0 votes
In reply to: Solved: AspNetControl

Hi Ewan,

the base class AspNetControl is not a UserControl and has the attribute [ToolboxItem(false)].

So derived components to appear in the toolbox must have the attribute [ToolboxItem(true)] and may have to be added to the toolbox.

Hope that helps.

Best regards
Frank

Showing 10161 - 10180 of 11k results