That is a really silly problem which meant that I had to set 12 custom
props 4 times before I worked
out how to do something that should be rather more intuitive.
Richmond.
On 17/7/2018 5:51 pm, Bob Sneidar via use-livecode wrote:
You may be referring to the issue when setting the value of a
Having worked with LiveCode 8 extensively now I can say
that the Property palette is far far more awkward to use thatn the
LiveCode 7 one,
and I wish there were an easy way to revert to that property palette.
Richmond.
On 17/7/2018 1:59 pm, Curry Kenworthy via use-livecode wrote:
Bob:
> I
You may be referring to the issue when setting the value of a custom prop, if
you click away, like to another stack or tool after editing in the value field,
the prop will not retain the value you entered. Also clicking on another
property will not retain the value. You have to tab out or click
Bob:
> I find that when I create a new property, or a new element
> in an existing property, having th click on the property, then
> on the name of the property is annoying.
Absolutely, and it's actually training people to learn and use
inefficient actions. Conceptually and with muscle
Mark,
but even then the “value” field still shows 3 lines of text and cannot be
resized
> Am 17.07.2018 um 01:33 schrieb Mark Wieder via use-livecode
> :
>
> On 07/16/2018 02:00 PM, panagiotis merakos via use-livecode wrote:
>> Hi all,
>> Thank you for the feedback.
>> We are aware of this
On 07/16/2018 02:00 PM, panagiotis merakos via use-livecode wrote:
Hi all,
Thank you for the feedback.
We are aware of this problematic behavior. There is a bug report about it:
https://quality.livecode.com/show_bug.cgi?id=20701
Also
https://quality.livecode.com/show_bug.cgi?id=19880
and by
Hi all,
Thank you for the feedback.
We are aware of this problematic behavior. There is a bug report about it:
https://quality.livecode.com/show_bug.cgi?id=20701
Best,
Panos
--
On Mon, Jul 16, 2018 at 9:34 PM, Matthias Rebbe via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Tom,
Tom,
so you are also living with this? In LC 8.1.10 it´s even not possible to
maximize the height of the Property Inspector. And the value field also
displays only 3 lines of text.
I can´t believe that this was not noticed by one of the LC Team. Are they not
using the PI?
I noticed it already
And since we are talking about it some more, open a property inspector pallet.
Expand the pallet size so that the property pane gross. Now resize again only
this time smaller. The property pane does NOT shrink with the pallet, but
instead introduces scroll bars. That is a bit irritating too. I
Sorry I misunderstood you.
Bob S
> On Jul 16, 2018, at 13:11 , Matthias Rebbe via use-livecode
> wrote:
>
> Bob, that doesn´t work. The list field of the custom properties expands, but
> the value field at the bottom still keeps its size and there is no way to
> resize it.
>
>
Bob, that doesn´t work. The list field of the custom properties expands, but
the value field at the bottom still keeps its size and there is no way to
resize it.
> Am 16.07.2018 um 22:06 schrieb Bob Sneidar via use-livecode
> :
>
> I believe if you expand the entire property inspector
Well since we are talking about it, I find that when I create a new property,
or a new element in an existing property, having th click on the property, then
on the name of the property is annoying. The same thing holds true for the
property inspector and datagrids. You have to add a column,
The PI has a lot of issues in 9.0 this is one of the more annoying ones. I
really should record a video and demonstrate them all to the team. not
great for new users.
I would say its a bug. a workaround would be sending messages to the
property inspector. and try to automate the resizing.
On
I believe if you expand the entire property inspector pallette, the properties
panel will expand.
Bob S
> On Jul 16, 2018, at 12:34 , Matthias Rebbe via use-livecode
> wrote:
>
> Hi,
> is there a way to resize the value field for custom properties in the
> Property Inspector? It just
Hi,
is there a way to resize the value field for custom properties in the Property
Inspector? It just shows 3 lines. I think that is not enough, especially if one
wants to store larger text files there.
Older versions of LC allowed to resize that field if i remember right. Why was
that
15 matches
Mail list logo
