Marius Mutu
8fa842888a
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_011Euno5AmwoFEvBTdWH8C8S
18 lines
1.1 KiB
Markdown
18 lines
1.1 KiB
Markdown
# Capcana: coloana noua intr-un grid existent ajunge la coada (preferinte GridExtras)
|
|
|
|
`GridExtras` (`COMUN\utile\GridExtras\gridextras.vc2:1051`, `restoregridpreferences` /
|
|
`savegridpreferences`) salveaza **per utilizator** latimea si ordinea coloanelor fiecarui grid,
|
|
in `%APPDATA%\...\gridprefs.tmp`, sub cheia `SYS(1272, grid)` (ex. `frm_modific2024.grid1`).
|
|
Salvarea se face live, la `columnmoved`/`columnresize`, nu la iesirea din formular.
|
|
|
|
Consecinta: `ColumnOrder` setat in clasa e neutralizat la runtime pentru orice utilizator care a
|
|
deschis deja formularul inainte de livrare - `gridextra1.setup()` restaureaza ordinea veche, iar
|
|
coloana nou adaugata (care nu exista in preferinte) ajunge ultima.
|
|
|
|
Solutie: repozitionare la runtime, in `Show()`, **dupa** `gridextra1.setup()`, aplicata o singura
|
|
data - cat timp preferintele salvate nu acopera toate coloanele (implementat pe
|
|
`frm_modific2024`, `COMUN\clase\omodificari.vc2`, coloana `nnir`).
|
|
|
|
La testare: pozitia coloanei nu e o asertiune stabila intre masini. Se asertesteaza tare
|
|
`ControlSource` si `ReadOnly`; `ColumnOrder` ramane informativ.
|