How-to
Why C-more Micro Preview Screens Show Out of Order
Short answer
Preview thumbnails in C-more Micro follow the project's stored Screen Library list order, not the screen number, and Preview has no sort function. Fix the sequence by dragging entries in the Screen Library; never renumber screens, because every screen-change reference stores the number.
On this page
- Why won't the Preview pane sort by screen number?
- Is the scrambled Preview order a bug in V4.35.0.0?
- How do I put the Preview thumbnails in screen-number order?
- Why should I not just renumber the screens?
- What if drag-and-drop in the Screen Library will not take?
- How do I verify the reorder changed nothing else?
- How do I keep list order and screen numbers aligned as the project grows?
- Questions asked
Preview thumbnails in the AutomationDirect C-more Micro programming software follow the project's stored list order, not the screen number, and the fix is a drag-and-drop reorder in the Screen Library — never a renumber. Detail mode looks correct only because it applies a column sort that the Preview view does not have. Below: the two properties behind the behavior, the reorder procedure, the drag failures and their cures, and the verification that proves the running panel is untouched.
Why won't the Preview pane sort by screen number? #
No sort function exists in the Preview viewing selection: it draws thumbnails in the project's stored list order, which is a separate property from the screen number, so the pane shows 1, 2, 3, 4, 7, 8, 6, 5 whenever those two properties have drifted apart.
Every screen carries two independent properties:
| Property | What it controls | Where it is edited |
|---|---|---|
| Screen number | The numeric ID used by screen-change objects, PLC-driven screen changes and jump targets | Screen properties dialog |
| List position | The sequence of thumbnails shown by the Preview viewing selection | Screen Library, by drag-and-drop |
A screen added to an existing project is appended to the end of the stored list no matter which number it is assigned, and renumbering a screen later changes its number without moving its position. Detail mode sorts the screen-number column, so it always reads 1 through N, but that sort is a view attribute of Detail mode only and never writes back to the stored list.
Worked example: a project holds screens 1 through 4, and you add four screens, assigning the numbers 7, 8, 6 and 5 in the order you create them. Each addition appends, so the stored list becomes 1, 2, 3, 4, 7, 8, 6, 5 while every number stays valid — the exact split reported on V4.35.0.0. The decision: nothing is broken, and the pane is faithfully showing a real second property.
Is the scrambled Preview order a bug in V4.35.0.0? #
No — it is intended behavior, not a defect: the Preview viewing selection has never exposed a sort-by-number option in any release, and the Screen Library drag-and-drop has always been the mechanism for setting list order.
Nothing in the project is corrupted and the panel's runtime behavior is unaffected; only the development-time thumbnail sequence differs. Do not open a defect report — the Screen Library reorder is the documented workflow, and any newer build that changes it will say so in its release notes and in the help file installed with that version. The decision: spend the minutes on the reorder, not on a defect ticket.
How do I put the Preview thumbnails in screen-number order? #
Reorder the Screen Library: open it from the Screens group in the navigation pane, drag each out-of-place entry between its neighbors, and Preview then follows that sequence — there is no sort button anywhere else.
- Save the project so you have a rollback point.
- Open the Screen Library from the Screens group in the navigation pane of the main window.
- Locate the out-of-position entries — screens 5, 6, 7 and 8 in the worked example above.
- Click and hold a screen entry, drag it to the target position, and release it between the two adjacent entries.
- Repeat single moves until the list reads your target sequence, for example ascending screen number 1 through 8.
- Close the Screen Library and switch the navigation pane back to Preview; the thumbnails now follow the list.
- Save the project again to persist the new order.
The arithmetic favors acting immediately: 4 screens out of place cost 4 drags if you correct each one as it is added, while 10 accumulated screens cost 10 drags in one sitting — the work grows by one drag per deferred screen. Decide the full target sequence before the first drag, because a bulk reorder has no undo guarantee.
Why should I not just renumber the screens? #
Because every screen-change button, function key and PLC screen-change tag stores the screen number, renumbering a screen silently repoints all of those references, while a Screen Library reorder touches none of them.
The number is the reference target. Project objects store it, and PLC code that drives screen changes writes it to a register — the same class of mechanism as how the LS system area screen change register works in other panels. Change a number and each reference now points at whatever screen inherited that number, or at nothing. Electrical design software carries the same trap, where identifiers and cross-references travel together; how EPLAN cable DTs follow names when renumbering covers the wiring-side equivalent.
Treat any renumber on a commissioned machine as a navigation change: a screen-change object that now lands on the wrong screen can hide an alarm or a stop instruction from the operator. If a number genuinely must change, audit every screen-change object, function key and PLC screen-change mapping before the next transfer. The decision: reorder to fix order, renumber only for a deliberate reference change, and never mix the two in one session.
What if drag-and-drop in the Screen Library will not take? #
Three checks cover nearly every failed drag: confirm you are in the Screen Library window and not the Preview pane, drop on the boundary between two rows rather than the middle of a row, and move one screen per pass.
- Drag-and-drop is not supported in the Preview pane at all; the Screen Library is the only window that accepts the move.
- Drop the entry onto the boundary between two rows, not onto the middle of an existing row.
- Move one screen at a time and let the list refresh before starting the next move.
- If the list looks stale after a move, close and reopen the Screen Library to force a redraw.
The decision: one screen, one boundary drop, one refresh at a time — and a reopen of the Screen Library as the reset whenever the display looks stale.
How do I verify the reorder changed nothing else? #
Run five checks after every reorder: Preview must follow the new sequence, Detail must still sort ascending by screen number, every screen number must be unchanged, every screen-change object must still point where it did, and the sequence must survive closing and reopening the project.
| Check | Expected result |
|---|---|
| Navigation pane, Preview selected | Thumbnails appear in the sequence set in the Screen Library |
| Navigation pane, Detail selected | Still sorted ascending by screen number, unaffected by the reorder |
| Screen properties of each screen | Numbers identical to before the reorder |
| Screen-change objects and function keys | Same screen numbers, no re-linking required |
| Project saved, closed and reopened | Preview order persists |
Then transfer the project and step through the navigation path on the hardware. Runtime navigation follows the screen number and the configured screen-change objects, so the reorder must produce zero change on the panel; if navigation differs, a screen number was edited during the session, and the screen properties and the PLC screen-change mapping need auditing before the machine runs.
How do I keep list order and screen numbers aligned as the project grows? #
Number in blocks and reorder on arrival: assign main screens 10, 20, 30 with 11 through 19 reserved as sub-screens of screen 10, and drag each new screen into its place in the Screen Library the moment you create it — those two habits keep the two properties aligned.
- Number with gaps. Sub-screens 11 through 19 give screen 10 nine slots (19 − 11 + 1 = 9), and a fourth main screen takes 40: one assignment, zero renames, no forced reorder.
- Reorder on arrival. A new screen appends to the end of the list whatever number it carries; one drag now beats a batch of drags later.
- Group by function when it helps commissioning. Alarm screens together, setup screens together — Preview order is free, because list position has no runtime effect.
- Audit numbers in Detail mode. Its sorted number column exposes duplicates and gaps at a glance; thumbnails never will.
If you inherit a badly scrambled project, the recovery is one pass: record the sorted screen list in Detail mode, open the Screen Library, and drag the entries into that sequence from top to bottom — no property edits, no re-linking. Migration ends the same way: after importing legacy HMI screens when migrating to a new panel, run that one-pass cleanup before commissioning. The decision: gap numbering plus reorder-on-arrival for new work, the one-pass rebuild for inherited work, and renumbering off the table in both cases.
Questions asked
Why do screens I add land at the end of the Preview list?
New screens are appended to the end of the stored list whatever number you assign them, and renumbering an added screen does not move it — the number changes, the position does not — so the pane never corrects itself. Drag each new screen into place in the Screen Library as you create it.
Does changing the Screen Library order change anything on the panel?
No. Runtime navigation is driven by the screen number and the screen-change objects you configured, so list position is invisible to the panel. Treat any navigation change that appears after a reorder as evidence that a screen number was edited in the same session, and audit the screen properties and the PLC screen-change mapping before the next transfer.
Which view should I use to audit screen numbers?
Detail mode. Its screen-number column is always sorted, so a duplicate or a gap in the numbering shows immediately, while Preview hides both behind list position. Record the sorted list in Detail mode before you start reordering an inherited project, and use it as the target sequence in the Screen Library.
Should the missing Preview sort be reported as a software defect?
No. The Preview viewing selection has never included a sort-by-number option — the behavior is the same on V4.35.0.0 and earlier releases — and the Screen Library is the intended place to control the sequence. If a newer build changes this, its release notes will say so.