> We should fix bugs not circumvent them.
Ok, I will do a test program to show the problem.
But ASAP (sorry I a m overbooked).
Fre;D
--
Sent from: http://mseide-msegui-talk.13964.n8.nabble.com/
--
Check out the
On Wednesday 01 November 2017 14:12:06 fredvs wrote:
> > Why? A crash should not happen.
>
> Because the wrong value is still there (if not corrected).
t*editwidget.value will not be changed by an invalid entry. If you have a
wrong value in "value" property it is a MSEgui bug which must be
> Why? A crash should not happen.
Because the wrong value is still there (if not corrected). And the mix is
done by a timer of 100 ms. So when the mix occurs, each 0.1 second there is
a modal error message (no time to close it). And finally it crash.
PS: All works like wanted with the tuned
On Tuesday 31 October 2017 19:07:35 fredvs wrote:
> > It can be closed by pressing "Enter".
>
Or "Esc", -> in order to restore the origin value press "Esc" twice.
> Yes, but for lazy people (like me) it is lot of work to press a key. ;-)
>
> Also, because the message-form is modal, if a process
> It can be closed by pressing "Enter".
Yes, but for lazy people (like me) it is lot of work to press a key. ;-)
Also, because the message-form is modal, if a process is running that needs
to access value of the spinedit, it can make trouble if the message-form was
not closed.
Also, in the
On Tuesday 31 October 2017 11:46:09 fredvs wrote:
> > It contradicts the value entry philosophy of MSEgui.
>
> Hello Martin.
>
> OK, I I have kept the philosophy of MSEgui.
>
> But I did change only one thing: in place of a modal error-message (that
> need to manually be closed),
It can be
> It contradicts the value entry philosophy of MSEgui.
Hello Martin.
OK, I I have kept the philosophy of MSEgui.
But I did change only one thing: in place of a modal error-message (that
need to manually be closed), I use a hint-timed-form (that closes it-self
after 2 seconds). And to avoid
> Press Esc in order to restore the previous value.
Ha, good to know (and to add to the hint text of a spinedit).
Perfect Martin.
(But I think that I will use "ontextedited" to check-correct value and a
kind of timed-hint-message-self-closed-form to explain the error value
entered).
Many
On Monday 30 October 2017 18:19:20 fredvs wrote:
> > It contradicts the value entry philosophy of MSEgui
>
> OK, I understand but maybe it could be good, if for example a new value >
> valuemax is entered, that a error range message is displayed (like MSE do
> now) but after the old value before
> It contradicts the value entry philosophy of MSEgui
OK, I understand but maybe it could be good, if for example a new value >
valuemax is entered, that a error range message is displayed (like MSE do
now) but after the old value before changing is restored.
For example if you assign:
valuemax
On Monday 30 October 2017 13:44:46 fredvs wrote:
> > Please set "valuemax" to a very big value instead.
>
> Ok, valuemax = 99 and valuemin = '' .
>
> Now, if for example 200 is entered ---> reset to 100.
> And if value = '' or < 0 --> reset to 0.
>
> Perfect.
>
> Huh, for the totally dummies,
> Please set "valuemax" to a very big value instead.
Ok, valuemax = 99 and valuemin = '' .
Now, if for example 200 is entered ---> reset to 100.
And if value = '' or < 0 --> reset to 0.
Perfect.
Huh, for the totally dummies, is it possible to do a filter if a character
is entered in
On Monday 30 October 2017 12:54:04 fredvs wrote:
> Hello Martin.
>
> Tanks for answer.
>
> So I did remove "valuemin", "valuemax" .
>
If valuemax = '' then the biggest accepted value is an empty value -> no
numeric value is allowed. Please set "valuemax" to a very big value instead.
The default
13 matches
Mail list logo
