Alarm lists need to show the 'top-most' line after update

[A.Demkovic]

Hello everyone,

There is a behaviour of the standard alarm list that after insert or removal of an alarm the alarm list scrolls to the bottom-most line.
How could I re-configure it or change somehow to keep the currently selected-line in view or alternatively show the 'top-most' line?

Thanks a lot for help in advance!


Regards,
Aleksandar

[leoknipp]

In the AEScreen you can define the sorting order in the Properties panel.
Then it should be possible to show newest information on top of the table.

Best Regards
Leopold Knipp
Senior Support Specialist

[A.Demkovic]

Hi Leopold, thank you for the response.
The list is already sorted in a certain way and therefore it should not be resorted.
Also, what I am trying to achieve is not to show the newest information, but to keep focus on the top of the list (table), regardless of the changes on the bottom (where low-priority items are added).

[leoknipp]

Which alarm list are you talking about?
The standard AEScreen?

With the table property "lineVisible" you can define which line shall be visible.

Best Regards
Leopold Knipp
Senior Support Specialist

[A.Demkovic]

Well, I do refer to AEScreen, or even better to say we only use AESRow.
But, I'm trying to refer also to any table, since the behaviour is default for any table object - every time a line is added, table jumps to the end (I don't even think it jumps to that specific item, but really to the end).

Therefore, I was thinking there's a way to disable this and implement a "silent update", where a row will be appended, but scroll event will not be triggered.

I did already experimented with "lineVisible(0)", which indeed bring the scroll to the top, but still cannot find the proper event on which this action can be best performed. I would prefer to trigger this on table row (i.e. alarm) added event, but couldn't find it yet - @leoknipp do you maybe have some suggestions on this?

[kilianvp]

For Tables you can use "stop"

Code: Select all

main()
{
  MY_TABLE.stop(true);
}

works in 3.15+

[leoknipp]

If you want to avoid that the AEScreen/AESRow scrolls to the newest line you will have to modify the aes.ctl CTRL library and the work function which is used for the update of the table.

Best Regards
Leopold Knipp
Senior Support Specialist

[A.Demkovic]

Thanks both @kilianvp and @leoknipp, I managed to change the behaviour as desired.
First, I had to introduce the table_top.stop() call in AESRow, but since aes.ctl also make those scroll jumps under certain conditions, I also had to disable those "this.lineVisible = -1/0" calls as well.

It behaves exactly as we wanted, so thanks a lot again.