|
Post by kurtis on Aug 30, 2018 17:55:34 GMT
Recently started using UI++ with our new SCCM deployment. Great tool and has offered us a great deal of flexibility!
What I have noticed though, is we use a TextInput element to edit a predefined OU string for the machine when it joins the domain. Problem is, this OU string is quite long. While the default value sets the TextInput to the full correct string (which I get from a Task Sequence variable), we are unable to edit it, as the string extends beyond the size of the TextInput box. Basically, when typing in a TextInput, you are limited on how much text you can type based on the size of the TextInput box.
Any way of possibly changing this, so we can enter text beyond the size of the input box and have it just 'scroll' left or right as it extends beyond the input box size?
I really hope I've explained this properly.
Thanks for a great tool!
Kurtis
P.S. Here's an attempt to illustrate the issue: _______________________________ | OU=This random OU,OU=Some oth | |----------------------------------|
Can't finish entering the OU, because it won't let me type beyond the physical size of the input box
|
|
|
Post by Jason on Aug 31, 2018 18:00:36 GMT
I'll take a look at this -- it shouldn't be too difficult to implement. Do you really want folks to be typing in OUs though? Wouldn't it be better to have them choose from a list?
|
|
|
Post by codyftw on Sept 11, 2018 22:34:32 GMT
I am having the same issue and also require a longer string limit. We have a build option for Kiosks where the users can enter a custom URL to configure the Kiosk to use. Many of the URLs that users are attempting to use exceed the character limit. Thanks!
|
|
|
Post by kurtis on Oct 29, 2018 17:41:32 GMT
I'll take a look at this -- it shouldn't be too difficult to implement. Do you really want folks to be typing in OUs though? Wouldn't it be better to have them choose from a list? My bad, Jason! I totally lost site of this after I posted. Busiest time of the year for us. Our end users don't have access to this part of SCCM, it's really just our technicians, and while I agree, the idea of typing an OU out is not ideal, they already have a default OU in the box and really just 'might' (rare circumstances) need to change a few characters in the string. A drop down would be nice, but we have far too many OUs that machines should be going into in our environment and creating and maintaining that is a little daunting. Nonetheless, like codyftw mentioned, there is other uses that seem to be affected by the length limit. Thanks for looking into this and I'll keep an eye out for an update to hopefully come out soon!
|
|
|
Post by Jason on Nov 9, 2018 18:55:02 GMT
This is now implemented in 2.11.0.0 (which I will hopefully be releasing this weekend).
|
|
|
Post by Jason on Nov 13, 2018 2:22:07 GMT
|
|