GridProtectionAlliance/openECA

InputMapping Screen Width

Closed this issue · 0 comments

When Input Mappings are long, like this: RANNISH_RANNISH_A_pos_V;RANNISH_RANNISH_B_pos_V;RANNISH_RANNISH_C_pos_V;RANNISH_RANNISH_D_pos_V;RANNISH_RANNISH_E_pos_V;RANNISH_RANNISH_F_pos_V;RANNISH_RANNISH_G_pos_V;SEVEREN_SEVEREN_A_pos_V;SEVEREN_SEVEREN_BUS1_pos_V;SEVEREN_SEVEREN_BUS2_pos_V;SEVEREN_SEVEREN_B_pos_V;SEVEREN_SEVEREN_C_pos_V;SEVEREN_SEVEREN_D_pos_V;SEVEREN_SEVEREN_E_pos_V;SEVEREN_SEVEREN_F_pos_V;SEVEREN_SEVEREN_G_pos_V;TINUE_TINUE_A_pos_V;TINUE_TINUE_BUS1_pos_V;TINUE_TINUE_BUS2_pos_V;TINUE_TINUE_C_pos_V;TINUE_TINUE_UN_pos_V;TINUE_TINUE_B_pos_V;
The screen auto-stretches all of the way out to include the long string and the edit/delete buttons get pushed all the way out. Suggest clipping the widget of a Mapping display string to a more reasonable length so that access to the controls is not hindered.