Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » U++ Library support » LineEdit, EditFields, DocEdit » Limited EditString...- MaxChars [SOLVED AND FIXED...]
Re: Limited EditString... [message #2195 is a reply to message #2193] Mon, 03 April 2006 21:31 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 13980
Registered: November 2005
Ultimate Member
forlano wrote on Mon, 03 April 2006 15:02

fudadmin wrote on Mon, 03 April 2006 17:49

luzr wrote on Mon, 03 April 2006 16:29

fudadmin wrote on Mon, 03 April 2006 10:53

Quote:

Well, I believe is that what forlano requests may not be desirable (at least, such limiting editing is very annoying in practice).


In my opinion, it is very annoying the authoritarian approach of U++ to user tastes, when some worldwide used features are exluded...



Ok, ok... Puttin' to ToDo...

Mirek


Sorry about that... Smile There's no rush. But I imagine how U++ users-programmers are frustrated when they waste time and they can't find what they had been used to...


To say the truth I found such option in many tools that are from far below U++ for power and widget richness. From other side the designer permits to limit the lenght of the string. I supposed that when this limit was reached no other imput was possibile... maybe some 'beep' is not bad to attract the attention of the user in this case. Instead now the user can continue to write and overcome the limit without problem. This is very annoying because when he realize the mistake he must delete the excedeed characters. To avoid the same experience he must keep his sight costantly on the screen to stop at the pink colour (... and delete one character). This way to proceed in my modest opinion is time consuming and not very friendly.
Thanks for the attention.
Luigi


I think I owe you explanation - as it is designed now, it is not only about pink color (actually, that is recent month addition per users request). I agree that pink color is not enough.

However, there is usually a moment in GUI dialog lifetime when users acknowledges editations (usually by pressing OK butten). For that very moment there is an Accept method of TopWindow (it is automatically invoked if you bind OK button to your dialog using CtrlLayoutOKCancel). Accept method will, in case that there are any errors like this, stop the process and display error, setting focus to invalid widget.

Means while user is allowed to exceed EditString length for editational purposes, he is not allowed to accept invalid value (send to further processing).

Mirek
 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: EditMinMax ctrl implementation
Next Topic: Why there is no WhenEnter for EditField?
Goto Forum:
  


Current Time: Fri May 17 13:04:02 CEST 2024

Total time taken to generate the page: 0.01611 seconds