Products

[admin]

Hi,
This looks like a bug, because the selection and focus visual appearance of an item is the same. The item looks like selected, but actually it is only focused. It is not part of the selectedIndexes collection anymore. Only items which appeal in the INPUT field are selected. The focused item is the item from which the keyboard navigation starts.
Best Regards,
Peter Stoev
Smart HTML Elements Team
https://www.htmlelements.com/

[admin]

Hi Mitesh,
Unfortunately, there is currently no way of disabling the built-in context menu while keeping the Actions icon, but we will consider adding a mechanism for doing so. Thank you for your valuable feedback.
Best regards,
Dimitar
Smart HTML Elements Team
https://www.htmlelements.com

[admin]

Hi davout,
To achieve that you may use this:

html, body {
   width: 100%; height: 100%; padding: 0; margin: 0;
}
app-public-home-header {
   display: block;
   width: 100%;
   height: 200px;
   background: #eee;
}
smart-splitter {
   width: 100%;
   height: 100%;
}

Hope this helps.
Best Regards,
B. Markov

[admin]

Hi,
Your code seems OK as a workaround for your application scenario with ComboBox.
Best Regards,
Peter Stoev
Smart UI Team
https://www.htmlelements.com/

[admin]

Hi Peter,
It is possible to use a licensed version through NPM. As this information is not for a public forum, please write to support@jqwidgets.com or support@htmlelements.com for license unlock instructions.
Best regards,
Peter Stoev
Smart UI Team
https://www.htmlelements.com/

[admin]

Hi Gerhard,
I would suggest you to check the code and required scripts in this demo: https://www.htmlelements.com/demos/grid/print/.
The printing internally uses the Data Export and the Web Browser’s Printing API.
Best Regards,
Peter
Smart HTML Element
https://www.htmlelements.com/

[admin]

Alright,
I found the scripts for exporting PDF and XLSX, but I’m still having problems with the print method.
Where is the function implemented? Or is my version too old? How could I check that?
Greetings,
Gerhard

[admin]

Hi Peter,
thank you very much! That worked for me.

[admin]

Hi Tr12,
Yes, it requires about 400ms for 30 textboxes. If this is slow for you, you can use our smart-input which is similar, but with more basic features.
Best Regards,
Peter
Smart HTML Elements Team
https://www.htmlelements.com

[admin]

Hi Tr12,
Actually, the previous was answered by my colleague. Anyway, you can call him Peter, too 🙂
When you add multiple HTML Elements, it would be better to add them just once in the DOM.

    const doc = document.createDocumentFragment();
            for(let z = 0; z < 30; z++) {
                let text = new window.Smart.TextBox();
                text.value = "abc";
                doc.appendChild(text);
            }
  document.body.appendChild(doc);

Best Regards,
Peter
Smart HTML Elements Team
https://www.htmlelements.com

[admin]

Hi,
Thank you for the feedback. The behavior is confirmed and we will look at it for the next scheduled release.
Best Regards,
Peter
Smart UI Team
https://www.htmlelements.com/

[admin]

Hi Tr12,
We are not sure from where the issue comes. We will have to test and debug that scenario.
Best regards,
Peter
Smart UI Team
https://www.htmlelements.com/

[admin]

Hi Gerhard,
That initialization requires the HTML Element to be in the DOM. If the querySelector by id, which in this case is ‘grid’, the component properties would not be set. In general, it is not necessary to use that kind of initialization. You can set properties as in the standard SELECT tags like myGrid.someProperty = someValue;
Regards,
Peter
Smart UI Team
https://www.htmlelements.com/

[admin]

Hi Tr12
Thank you for the feedback.
We will look into that Grid behavior for the next release which will be the last week of the month.
Best regards,
Peter
Smart UI Team
https://www.htmlelements.com/

[admin]

Hello,
Thanks for writing.
However, the correct tag is used in the referred demo.
Regards,
Peter
Smart UI Team
https://www.htmlelements.com/

[Author]

Posts