Tab effect on the keyboard focus

[howard.thomson]

Hi,

I have an EV_WINDOW, with an EV_HORIZONTAL_SPLIT_AREA which in turn has two side-by-side EV_GRIDs.

Is there any way of suppressing key_tab changes of focus between the two EV_GRIDs without also removing response to mouse events ?

I want both grids to respond to mouse clicks, but have keyboard entry in only one, and all attempts so far have failed, or only partially achieved what I want ...

Regards,

Howard

[howard.thomson]

I have since realised that adding a set_focus to keyboard events to always return the focus to where I want it will be sufficient [I think!]

Thanks,

Howard

[Finnian Reilly]

Lately I have discovered the usefulness of the transient attribute modifier for the Eiffel-Loop reflection classes. (Before I was naming excluded fields in a string)

But why does it have to be so verbose? 5 words just to tell the compiler: I want this to be transient.

I was thinking it would be great if the deprecated is keyword could re-purposed as a shorthand way to add status modifiers, as in the following subscription_option example.

Other modifiers could be added in a list as for example

some_field: SOME_CLASS is transient, stable

-- Finnian

-- 
SmartDevelopersUseUnderScoresInTheirIdentifiersBecause_it_is_much_easier_to_read

[Rosivaldo Fernandes Alves]

Em 11/05/2021 08:43, Finnian Reilly escreveu:
> Lately I have discovered the usefulness of the transient attribute
> modifier for the Eiffel-Loop reflection classes. (Before I was naming
> excluded fields in a string)
>
> But why does it have to be so verbose? 5 words just to tell the
> compiler: I want this to be transient.
>

> I was thinking it would be great if the deprecated *is *keyword could

> re-purposed as a shorthand way to add status modifiers, as in the

> following *subscription_option* example.

>
> Other modifiers could be added in a list as for example
>

> some_field: SOME_CLASS*is* transient, stable
>
>
> (...)

Good idea. But "is" has not gone entirely. There is an obscure use to it
within across loops. For instance, the loop

across 1 |..| 10 as i loop print (i.item) end

may be slightly abbreviated by

across 1 |..| 10 IS i loop print (i) end

Personally, I like of getting rid of .item when accessing the... er...
item I'm visiting currently.

Best regards,

--
Rosivaldo.

[Bertrand Meyer]

"is" will go away for loops as well. Time to effect the transition.

-- BM

--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/59ad4e89-8057-4e3b-9fb6-731a2d6c6ccb%40gmail.com.

[Rosivaldo Fernandes Alves]

Em 11/05/2021 09:58, Bertrand Meyer escreveu:
> "is" will go away for loops as well. Time to effect the transition.
>
> -- BM
>

> (...)

That's a pitty. :-(

--
Rosivaldo.

[Finnian Reilly]

On 11/05/2021 13:40, Rosivaldo Fernandes Alves wrote:

Good idea. But "is" has not gone entirely. There is an obscure use to it within across loops. For instance, the loop

I didn't know that, but that shouldn't preclude a possible use for attribute modifiers. Many keyword are used in multiple contexts.

-- 
SmartDevelopersUseUnderScoresInTheirIdentifiersBecause_it_is_much_easier_to_read

[Ulrich Windl]

>>> Rosivaldo Fernandes Alves <rosiva...@gmail.com> schrieb am 11.05.2021 um
15:00 in Nachricht <fa0cbc10-1e73-a641...@gmail.com>:

Well, maybe it's "100% Ada-free", then ;-)

[Bertrand Meyer]

No, it's not a pity, you will not lose anything, except the need to explain the nuance between "is" and "as". Everything that you want to do will be doable, just more simply and concisely.

-- BM

-----Original Message-----
From: eiffel...@googlegroups.com [mailto:eiffel...@googlegroups.com] On Behalf Of Rosivaldo Fernandes Alves
Sent: Tuesday, May 11, 2021 15:00
To: eiffel...@googlegroups.com
Subject: Re: [eiffel-users] The "is" keyword re-purposed

--
You received this message because you are subscribed to the Google Groups "Eiffel Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to eiffel-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/eiffel-users/fa0cbc10-1e73-a641-14b3-cdbbe8d439db%40gmail.com.

[Rosivaldo Fernandes Alves]

Em 11/05/2021 10:04, Finnian Reilly escreveu:
> On 11/05/2021 13:40, Rosivaldo Fernandes Alves wrote:
>> Good idea. But "is" has not gone entirely. There is an obscure use to
>> it within across loops. For instance, the loop
>
> I didn't know that, but that shouldn't preclude a possible use for

> attribute modifiers. Many keyword are used in multiple contexts*.*
>
> (...)

Sure.

--
Rosivaldo.