|
|
Rank: Advanced Member
Groups: Member
Joined: 11/15/2008
Posts: 44
|
People (my venerable users) keep pressing enter for a newline in the EditableLabel and training them to use Shift-Enter is not the right answer. I cannot find an EO way to work-around this. Is there away to control which keys exit the EditableLabel? Yes, I could use z-order and grab the keys first but going back to a plain old textbox seems like a better trade-off.
Thanks! I Love EO.Web!!
Chris
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Hi,
Glad to hear that you like our product! I do not believe there is a way to replace shift-enter though. The reason is enter is reserved for leaving edit mode. So there is no way to make it work as inserting a new line.
Thanks!
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/15/2008
Posts: 44
|
Thanks!
Please put in my vote to modify the design. My users have convinced me that it is a problem. My job is to convince EO of the same. (I imagine I'll have to adapt by using a different control to satisfy my users.)
Thank you,
Chris
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
Thanks for your suggestion. I do not believe we can modify this though. I understand that some users wanted to use enter key to insert new lines, but a lot of users wanted to use the enter to exit edit mode. If we change it to work your way, not only those users won't be happy, but also we have to come up a new way to exit edit mode (we could use tab key, then some users will wanted to be able to use tab key to insert tabs instead of leaving edit mode). So it is impossible for us to satisfy them all.
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/15/2008
Posts: 44
|
The normal EO way to handle this would be
1. A client side event to decide on edit exit
or
2. Configure the set of exit edit keys.
So, yes, EO can and often does satisfy everyone!
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
No. Not this one. This is a relatively simple control and we have no intention to over complicate it. We have had no other complains about this feature. So we will not change it for now.
Thanks
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/15/2008
Posts: 44
|
Gosh ... my first time getting this tone. Hope it is not a trend. 8(
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
We have to be firm on what changes we will make and what changes we will not make. It is not possible for us to make changes to the product upon every request from our users. Some wanted this way and some wanted that way and we have to balance between how many people really benefit from such changes and whether the changes will have a negative impact on other users and the over all product quality. In this regard we simply can not say yes to everyone and we will say no in some cases. Usually a no is a no and will not change until we have more feedback from more customers. Hope you understand.
Thanks
|
|
Rank: Advanced Member
Groups: Member
Joined: 11/15/2008
Posts: 44
|
The responses in the past have been "wait and see" not a flat-out "No Never."... unusual.
It is a new control. Other new controls have received have adapted over time. Turns out that software designers do not often get a permanent perfect for all time on the first go.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,194
|
We are not saying never on this either. If we hear a lot similar feedbacks about this in the future, we probably will change it. I understand you wanted us to change it now for you, to which we have clearly gave you a no answer --- we will not change the product just for you NOW.
I am quite certain that any product, including ours, always have rooms for improvement. However you need to understand that we have a large user base, we can not afford to make changes to the product based every single user request, especially when it is very much a user preference issue. This has always been our position. It has not changed.
I believe we have clearly clarified our position on this issue. This issue is now closed.
Thanks
|
|