<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
svaa wrote:
<blockquote cite="mid:47BDF328.6060301@ciberpiula.net" type="cite">
<pre wrap="">Hello:
For me there is no doubt. When I set a control as readonly, I expect
that the user won't be able to change it at all.
In fact, years ago I hacked rxlib to avoid pop a list when they where
readonly. Particulary if they are attached to a database, it's confusing
for the user to change it clicking the button but updating nothing. The
downside is that they won't be able to show the calendar, but I think it
is better than confusing user. If the popped calendar could show clearly
that is not changeable, it would be the best, but a low priority
enhacement. By the way, when I say TDateTimeEdit, I mean any control
with a combo etc.
Anyhow, if you want people see that a control is not usable, it is
better to assign enable:=false. The pity of disabled controls it that
they are not easily readable.
Sometimes I think that there should be three colors to inform the user
of the state of the control: enabled, disabled and readonly. Long time
ago I played with the idea of changing the Dataware controls to have a
yellow background when they where not editable (because they were
readonly or because the TDatasource was not autoedit or because the
underlaying table was readonly.)
Just my 0.25 cents.
Reagards
Santiago A.
</pre>
</blockquote>
+1<br>
<br>
I usually change the colour or background colour of a control if it
*always* readonly, it would be great to have an easy way to do it. I
probably tend to disable a control if its mode changes, but it can
still be useful to distinguish between "valid, but read only" and
"invalid in this context".<br>
<br>
I think the difference between the two views depends on whether you see
the TDateEdit as two controls ( in which case I agree with Vincent) or
a single control, in which case I agree with Gerard. <br>
<br>
If it were two controls, you make the edit box readonly (to
keystrokes), but the button is changing it programatically. But if it
is a single control, readonly = readonly = readonly - no user changes
of any kind.<br>
<br>
As it appears to only a single control - you can't disable the button
without disabling the whole control - I think I have to agree with
Gerard <br>
<br>
cheers,<br>
John Sunderland<br>
<br>
<blockquote cite="mid:47BDF328.6060301@ciberpiula.net" type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">There's a discussion going on about TDateTimeEdit.ReadOnly in Mantis
report 10861.
It's not a technical discussion, it's more about what ReadOnly should
and shouldn't do.
See. <a class="moz-txt-link-freetext" href="http://bugs.freepascal.org/view.php?id=10861">http://bugs.freepascal.org/view.php?id=10861</a>
The list is probably a better place to discuss this, so please read
the report and give your opinion here.
Regards,
Gerard.
------------------------------------------------------------------------
_______________________________________________
Lazarus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lazarus@lazarus.freepascal.org">Lazarus@lazarus.freepascal.org</a>
<a class="moz-txt-link-freetext" href="http://www.lazarus.freepascal.org/mailman/listinfo/lazarus">http://www.lazarus.freepascal.org/mailman/listinfo/lazarus</a>
------------------------------------------------------------------------
</pre>
</blockquote>
<pre wrap=""><!---->
_______________________________________________
Lazarus mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Lazarus@lazarus.freepascal.org">Lazarus@lazarus.freepascal.org</a>
<a class="moz-txt-link-freetext" href="http://www.lazarus.freepascal.org/mailman/listinfo/lazarus">http://www.lazarus.freepascal.org/mailman/listinfo/lazarus</a>
</pre>
</blockquote>
<br>
</body>
</html>