The workspace is everything we see in DSPX's main window: the menus and toolbars, the image windows and the tabs that hold them, the panels around them, and the pages of the image area that keep one piece of work apart from another. This chapter describes how the window is made, how we arrange it, and how we keep the whole session, images and all, in a project that comes back as it was.

2.1The Main Window

DSPX is one program and one window. The menus run along the top, with the toolbars under them. The image area is in the middle, and the panels, which hold the settings of processes and tools and the information about the image in front, are docked around it. A bar of tabs under the image area switches between workspaces, and the status line at the bottom says what is under the pointer and what we know about the image in front.

Menus: File, Edit, View, Mask, Select, Tools, Process, Window, Layer, Scripts, Help Toolbars: File, Window, Settings, Tools (Pan, Crop, Paintbrush, Selection, Clipboard, Draw...) Image tabs (in Tabs); process icon strip below Image window: the view, with its top row of preview controls Wheel zooms, dragging pans, the title shows the zoom Workspace bar: one tab per workspace, and + to add one Log: what was opened, run and saved, and what went wrong Process, Tool and Scripts panels, in one place Process Shelf History, and Layers Screen Stretch, Guide Status line: the pixel under the pointer | size, channels, zoom, stretch, profile, mask
The main window in the Default layout. A sketch of where the parts are; the layouts below rearrange the panels, and any panel can float.
DSPX's main window with one image open
The main window. DSPX Dark theme, Default layout, a finished image of the Lagoon and Trifid Nebulae open in Tabs, the Process panel showing Curves. Look at the menus, the toolbars, the panels on the right and the status line.

2.1.1The Menus

Every command of the program is in a menu, and every menu command can be given a shortcut (Keyboard Preferences). A menu command that does not apply to the image in front, or to the state of the program, is dimmed, and its tooltip says why when it is not obvious.

2.1.2The Toolbars

Nine toolbars have buttons for the commands we use most, and a field to search them, drawn in the theme's colors. They show their icons with the names beside them, icons alone, or names alone (Preferences > Layout). The one exception is the Syrup Bottom Bar, described below, which always shows icons alone.

Tools, File, Window, Settings, Masks and Layers are built-in LaunchPads docked as toolbars: each is still a LaunchPad, serving as a toolbar. They look and sit as the toolbars always did, and we can change them as any LaunchPad (see LaunchPads): add, remove and reorder their buttons, give them a look of their own, float them or dock them elsewhere. Search, the Syrup Top Bar, the Syrup Bottom Bar and the Image Picker are fixed toolbars. Their controls can also be placed on any LaunchPad, floating or docked, as live controls (LaunchPads: Controls).

2.1.3The Syrup Bottom Bar

The Syrup Bottom Bar sits under the images, in a row of its own, and it works with every theme. Its buttons are icons whatever the Buttons setting of the Layout page says (two stacked rows of sliders and choices and a row of buttons read better without names; each button has a tip). From the left:

The range, the curve, Negative and False color change only what the screen shows: no pixel of the image changes, nothing goes in the history, and the image is not marked as modified. They are the look of that image's window, kept while it is open, and they act on the picture as the screen stretch and the color management have made it (so with a dark linear image, we turn the screen stretch on first). Tools, exports and the image's statistics see the image as it is.

Each toolbar has a grip at its left; we drag it to move the toolbar anywhere along the top of the window (the Syrup Bottom Bar, along the bottom), or let it float. A built-in LaunchPad docked on the left or the right lays its buttons out in a column, as a toolbar does. Window > Toolbars shows or hides each one shown as a toolbar (a built-in LaunchPad floating as a window is in Window > LaunchPads), and Reset Toolbar Positions puts them back along the top, docking again a built-in LaunchPad that floats. Which ones show when DSPX starts is a setting of the Layout page of the Preferences.

2.1.4The Command Palette

The command palette finds a process, a tool, a script or a menu command from a few letters of its name, and runs it. We open it with Ctrl+K (Cmd+K on macOS; Edit > Search Commands), by clicking the field of the Search toolbar, or with Process > Find Process... (Ctrl+Shift+F), which opens it already narrowed to the processes. It is a box over the top of the main window, the same on every system. The field of the toolbar and the box are two faces of one thing: the toolbar's field holds no text; clicking it, or typing a key in it, opens the box and the typing goes there. If the keyboard goes anywhere else the box closes, so nothing stays half open.

We type, and the results narrow under the field, grouped as Processes, Tools, Scripts and Commands. A group header and a short line under each name say what it is: a process's description, a command's menu (Edit), a script's group. A command with a shortcut shows it at the right. Up and Down move the highlight, Enter or a click runs it, Esc or a click outside closes the box. The field starts empty.

What Enter does is what choosing the same thing in the menu does, and nothing more:

The Search toolbar can be hidden like any other (Window > Toolbars > Search, or the Layout page of the Preferences); Ctrl+K opens the box all the same. Its key can be changed in the Keyboard page like any other. Preferences pages and open images are not searched yet.

2.1.5The Status Line

The status line has two parts. On the left, the pixel under the pointer: its coordinates and its sample values. On the right, what we know about the image in front, separated by bars: its size, its channels and sample type, the number of layers of a layered image, the zoom, whether the screen stretch is on and linked, the image's ICC profile and whether the view manages its colors, the mask (and whether it is disabled, inverted or hidden), the selection, and the tool whose session is open on the image. A long operation, such as saving a project, shows a progress bar here with a Cancel button.

2.1.6The Canvas

The area behind the image windows shows the theme's wallpaper, or nothing. A double click on the canvas where no image window is opens the Open dialog.

2.2Image Windows

Each open image has a window of its own in the image area. The title shows the image's name, with a star when it has changes that are not saved, and the zoom. Inside the window is the view: the image, the screen stretch, the mask's overlay, the selection and whatever the active tool draws, with the row of preview controls over the top (Previewing a Process). Several images can be open at once, as many as the memory allows.

2.2.1Cascade, Tile and Tabs

The Window menu and the Window toolbar arrange the image windows in one of three ways.

Cascade: The default. The windows float, each its own size, and the open ones are put in a cascade when we choose it, in the order they were opened: the first at the workspace's corner, behind, each next one a step down and to the right, fitted to its image, and the last opened in front. The step is large enough for every window's title bar to show. A new window opens at the largest zoom that shows the whole image (never above 1:1), the window of that size, in the cascade; it starts again at the corner when the workspace is empty.

Tile: The windows are tiled side by side over the area. Tile and Cascade are the two free modes: the windows float, process icons and the wallpaper are shown, and Tile in either mode tiles the windows on request.

Tabs: One image at a time, with a tab for each image along the top of the image area. We drag a tab to put the images in another order.

The choice is kept: DSPX starts in the mode it was left in, and each workspace remembers its own mode (Workspaces). Choosing Tabs while images are minimized brings them back first.

2.2.2Zoom and Pan

The wheel zooms about the pointer. Dragging pans, with the left button when no tool is using it, with the right or the middle button always, or with the left button while the Space bar is held, which works even while a tool is active. The View menu has Zoom In, Zoom Out, Fit in Window, 1:1 and Fit Window to Image, which sizes a floating window to its image. The zoom is shown in the window's title and in the status line.

2.2.3The Pixel Under the Pointer

As the pointer moves over the image, the left of the status line gives the pixel's coordinates and the value of each channel, in the units of the image's sample type. A color-managed view reads the pixel's data, not the color shown on screen.

2.2.4The Image's Own Menu

Right-clicking an image's tab or the title bar of its window opens the window's menu. Besides the usual commands of a window it has Move to Workspace, and the top row of the view has an image menu with shortcuts to common changes: Mode converts between RGB and grayscale and among the sample types, Rotation turns or flips the image (the astrometric solution follows), Extract makes a gray image of the luminance or of a channel, Invert inverts the image, and Duplicate makes a copy of the image, with its layers and mask, as a new image. Each one is a process of its own run on the image, and one history step.

2.2.5Minimized Images

In Cascade and Tile, minimizing an image window hides the window and puts an icon where it was: a small picture of the image as it was shown, with its name under it, in the theme's title bar colors. The icons lie on the workspace and are dragged anywhere. A double click on one, or Enter or Space with it selected, restores the window to the size and place it had, in front. Closing the image removes its icon. Choosing Tabs restores every minimized image, since tabs have no icons.

2.2.6Who Holds an Image

While a tool, a process, a script, a guided run or a workflow is working on an image, the image is held, and anything that would also change it is refused with a message that names who holds it: "The image is in use by the Curves process", "M8 is in use by the script Stars_Only", and so on, followed by what to do: apply or cancel the tool's session, or wait for the process to end. When a tool holds the image, the message has a button that closes the tool for us (a session with changes asks first).

2.3Workspaces

An image area can hold a lot of windows. A workspace is a page of it: its own images, in their own order, with their own Tabs or Tile arrangement, their minimized icons and their process icons, and its own arrangement of the panels. We use a workspace for one target, one stage of the work, or one comparison, and switch between them without closing anything. The program starts with two, and we can have up to 16.

The workspace bar with three workspaces
The workspace bar. Three workspaces named M31, M31 compare and Workspace 3, the first shown, under an image area in Tabs. Look at the tab of the shown workspace and the + after the last.

2.3.1The Bar

The workspace bar is always shown under the image area, even with a single workspace, so that + is there to make another. It has a tab for each workspace, at the bottom as PixInsight has them, and the image tabs stay at the top in Tabs mode. A click on a tab shows that workspace, a drag reorders the tabs, a double click renames, and the tab's tooltip says how many images it has. The right-click menu of a tab has New Workspace, Rename..., Delete, Move Left and Move Right; the menu of the bar off the tabs has New Workspace.

2.3.2The Window > Workspaces Menu

Window > Workspaces lists the workspaces, the one shown checked, then:

Alt+1 to Alt+9 show the first nine workspaces (the commands are named Go to Workspace 1 to 9 in the keyboard preferences). Every one of these keys can be changed.

2.3.3Names, Limits and Deleting

A workspace is called Workspace 1, Workspace 2 and so on until we rename it. A name has at most 32 characters, an empty name puts the default back, and a name another workspace shows is refused, whatever its case, so that Move Image To is never ambiguous. At 16 workspaces, + and New Workspace are dimmed and their tooltip says why; the last workspace cannot be deleted.

Deleting a workspace that has images asks what to do with them: Move to its neighbor, named in the box, (the default; the neighbor is the workspace to its left, or to its right for the first), Close Them (each image with unsaved changes asks as closing it does, and the workspace stays if one remains open), or Cancel. Its process icons go to the neighbor as well, renamed there if a name is taken. Deleting the workspace shown shows the one to its left. Closing the last image of a workspace leaves the workspace, empty.

2.3.4What a Workspace Keeps

The documents are shared, but each window belongs to exactly one workspace, which also keeps:

Tile, Tabs, Ctrl+Tab and minimizing act within the workspace shown. Undo, Redo, Close and Save act on its image in front; no keyboard command acts on another workspace's images. An empty workspace has no image in front, as when nothing is open.

2.3.5Moving Images Between Workspaces

Move Image To, and Move to Workspace in the window's menu, move the window itself, not a copy: the same view with its zoom and place, and any tool's viewport. We stay in the workspace we are in, and the image is in front of its new workspace. Into a tiled workspace the windows are tiled again. A minimized image moved to a workspace in Tabs is restored first; between two tiled workspaces its icon goes with it. An image held by a tool or a process can be moved.

In Tabs, an image's tab dragged up or down out of the row of image tabs turns into a drag of the image, with a small picture of it under the pointer. Dropped on a workspace's tab in the bar, the image moves there. Along the image tabs a drag still reorders them, and hovering over a workspace tab does not switch to it.

2.3.6Where New Images Go

2.3.7Lists of Images and Tools in Another Workspace

Where a list offers the open images (the Applies to list of a process panel, Select Mask, New Layer from Image, Add Mask from Image), they are grouped by workspace, in the order of the bar, under headings that cannot be chosen, when more than one workspace has images. Choosing one never switches workspace: the process works on the image where it is, and a mask may be in another workspace.

A tool's session stays on its image. When that image is in a workspace that is not shown, the Tool panel says "Working on M42 in Workspace 2", and the name is a link that brings the image back. The same holds for the guided run: what it previews or shows is brought to the front together with its workspace.

2.3.8Process and Tool Windows in a Workspace

With Each process and tool in its own window on (Preferences > Layout), every process and every tool has a window of its own, and each of those windows belongs to one workspace, the workspace it was opened in or moved to. The other panels, Log, History, Layers, Scripts, Guide and Screen Stretch, belong to the program and are not tied to a workspace; the Process Shelf is shared by all of them too.

With the option off, nothing changes: the sets are kept and come back when it is switched on again.

2.3.9What Is Kept Between Sessions

The list of workspaces, their names, modes, panel arrangements and process windows, and the one that was shown, come back the next time DSPX starts. The arrangement of the panels is applied only when Start with is Where I left off (Layouts); when it names a layout, each workspace starts in the Default layout. No image is reopened by this: that is what a project is for. The Preferences page General, with Reset Page, puts back two workspaces with their default names; the images of the others are moved to the second, none is closed.

2.4Panels

The panels are the windows of settings and information that dock around the image area. There is one of each, whatever the number of workspaces; each workspace arranges them as it likes. Each is toggled in Window.

PanelWhat it holds
ProcessThe panel of the process we opened: its settings, Reset, Instance and Apply (The Process Panel).
ToolThe panel of the active tool. It shares the Process panel's place (Interactive Tools).
ScriptsThe Siril scripts, each with its compatibility mark (Scripts and Python).
Process ShelfSaved processes and PixInsight process icons, kept at hand (Saved Processes and the Process Shelf).
Screen StretchThe histogram and the controls of the image's screen stretch (Screen Stretch).
Process ExplorerA way into the processes by what we want to do, and a list of the AI tools (The Process Explorer). It is hidden until we choose Window > Process Explorer.
HistoryThe steps of the image in front (Undo, Redo and History).
LayersThe layers of a layered image (Layers).
LogWhat the program says (The Log).
GuideThe questions and steps of a guided run. It appears with a guided run and goes with it, in every workspace (Guided Processing).

2.4.1The Process Explorer

The Process Explorer is for the moment when we know what we want to do but not which process does it. It is in Window > Process Explorer, and it is a panel like the others: we dock it, float it or tab it, and a layout we save keeps it. None of the built-in layouts shows it, so nothing changes until we ask for it.

The panel has two parts. Under Processing there is a search box, and under it a list of boxes, one for each category, with its icon, its name and a line about the tools in it. Which categories it lists is a choice of the theme: the tasks (Browse by task, the default), the categories of the Process menu (Browse by category) or categories of our own (see Browsing by Category and by Our Own Categories). Under AI Tools there is a box for each process that runs an AI model or an AI program, with that process's own icon.

How it looks is the theme's too: the size and weight of the headers, and for every box the icon's size (or none), a group box or none, and the font size, weight and color of the name and of the line under it (Appearance and Preferences, The Process Explorer).

Browsing by Task

Pointing at a task box opens a popup beside it, to its right, or to its left when the window has no room at the right. The popup has the task's name as its header, the task's line under it, and a box for each process of the task: the process's icon, its name, and a line about what it does. A click on a process opens it, exactly as Process does: its panel appears and nothing is applied. The popup stays while the pointer is on it or on the task box, and goes when the pointer is on neither. Clicking a task box shows its popup at once. With the keyboard, Tab moves from one task box to the next and shows the popup for the box in focus; Enter, or the Right arrow, moves into the popup, the Up and Down arrows move between its boxes, Enter opens the process and Escape or the Left arrow goes back to the task box.

TaskWhat is in it
CalibratePre-processing and astrometry: Superbias, Calibration, Cosmetic Correction, Defect Map, Debayer, Split CFA, Merge CFA, Registration, Local Normalization, Integration, Drizzle, Autocrop, Comet Alignment, Canon Banding Reduction, RGB Combination, Plate Solve, Finding Chart, Photometric Glow Subtraction, the two Spectrophotometric calibrations, FITS Header, Background Extraction and GraXpert Background Extraction, Linear Fit.
ToneIntensity, stretch and color: Histogram, Curves, Hyperbolic, Arcsinh, Masked and Adaptive Stretch, Exponential Transformation, Binarize, Invert, Background Neutralization, Color Calibration, Spectrophotometric Color Calibration, Catalog Star Color, Saturation, SCNR, Convert Color, the two color profile processes, Linear Fit, Statistics.
LayersThe Layers panel, PixelMath, and the processes that combine several images: Channel Combination, LRGB Combination, RGB Combination, HDR Composition, Star Trails Blending, Channel Extraction, the alpha channel processes, Text.
RestoreDeconvolution, GraXpert Deconvolution, Wavelets, Noise Reduction, Multiscale TGV Denoise, GraXpert Denoise, Canon Banding Reduction, Blur, Noise Generator.
FinishSharpening and the last touches: Deep Sharpen, Unsharp Mask, Multiscale, Texture, Flow and Filament Sharpen, Clarity, HDR Compression, Dark Structures, Saturation.
Stars and MasksDeep Star Removal, StarNet2, Deep Star Mask, Color Mask, Range Mask, Deep Morphology, Photometric Glow Subtraction and the alpha channel processes.
GeometryCrop, Dynamic Astro Crop, Rotate, Resample, Integer Resample, Autocrop, Mosaic, Surface Align.
All toolsEvery process, in alphabetical order. A process that is in no other task is here.

A process may be in several tasks; Linear Fit is in Calibrate and Tone. The products of RC Astro's tool, when we have allowed it (Preferences), are listed in the task their menu category belongs to and under AI Tools.

Browsing by Category and by Our Own Categories

With Browse by category the boxes are the categories of the Process menu, in the order the menu has them: Astrometry, Background, Channel Management, Color, and so on. A popup lists the processes that the menu lists in that category, by name; the pre-processing steps are in the order of a night, as in the menu. Every process is in exactly one box. Processes with no category are in Other processes, at the end. The menu's own All Processes list is not a box here: the search finds every process, and Process > All Processes is still in the menu.

With Custom the boxes are categories we wrote in the theme: a name, an icon, a line and the processes, in the order we want them. The theme editor has a box for them (Panels and title bars, Process Explorer), and the format, with an example, is in Appearance and Preferences. A process that a custom category names and the program does not have is left out, and the Log says so. A custom list with no usable category shows the tasks.

Only one list is shown at a time. The panel changes when we change the theme or the choice, also while the theme editor is open.

Searching

Typing in the search box replaces the two lists with the processes and tools that match, as the same kind of boxes, best match first. The search looks at names, as the command palette does (a few letters of the start of each word are enough), and at what the processes say they do. Enter opens the first match, the Down arrow moves to the list, and clearing the box brings the tasks back.

2.4.2Docking and Floating

Every panel docks on the left or the right of the window, because the panels are tall and narrow; only the Log may also dock at the top or the bottom. Several panels in one place are tabbed. We drag a panel by its title to move it, drop it on another panel to tab it, or drop it outside the window to float it. A floating panel is a window of its own, kept inside its screen.

A layout can also make every panel a floating window: with Dock panels at the sides off (Preferences, page General) the left and right of the window are no longer places to dock. The panels docked there float where they are, at their size, and a floating panel has no Dock button. The Log alone can still dock at the top or the bottom. Turned on again, the panels stay floating until we dock them. The choice belongs to the layout: it is saved with a layout we save, and applying a layout puts back its own. The built-in layouts, and layouts saved before the option existed, have it on.

A floating Process panel next to the image
A floating panel. The Curves panel undocked and placed beside an image in Tile mode, all of its sections shown without a scroll bar. Look at the sections' chevrons and the buttons right after the settings.

2.4.3Sections

The groups of settings in a process panel are collapsible sections. A click anywhere on a section's title bar collapses or expands it; the chevron before the title says which way it is, down for expanded and right for collapsed. Tab reaches a title and Space or Enter does the same. The state we leave a section in is remembered for each process and group, for the panels opened later and the next start. A section we never touched follows its default, and some sections of the long panels (Calibration, Integration, Registration, the wavelet tools) start collapsed. A setting the guide asks us to check opens its section.

Process > Close All Process Windows closes the windows of the processes. The tools, the Log, History and the Process Shelf stay. A process with a live preview on an image asks first, because closing its window ends the preview.

2.4.4The Size of a Panel

The content of a panel starts at the top and follows on directly, with the buttons right after the settings. A dock taller than the panel leaves the room under it empty, and a panel with a part that takes the room, such as a list, a histogram or a curve, gives the room to that part. A dock shorter than the panel scrolls its settings with the buttons kept in view.

The first time a panel is undocked its window takes the size that shows all of it, without a scroll bar and within the screen. Afterwards the window's place and size are remembered while it floats, and used the next time it floats; the Process and Tool panels remember a size for each process and tool. The window follows its content: collapse a section, or let a label wrap onto another line, and the height follows; a window we made shorter ourselves keeps our size but grows by what the content gained. A floating Process or Tool panel is never narrower than 400 pixels, and never taller than its content needs, even when it holds a list or table that could take room: it can be made shorter, not taller, and a section that closes shrinks the window while the list keeps its height. In a panel with a splitter between its inputs, its settings and its results, a handle we move stays where we put it: a section that opens or closes changes the height of the settings, and of the window, and nothing else. Window > Reset Panel Sizes and Positions forgets the remembered sizes and places of the floating panels. The Default fit button on the title bar of a floating panel, between Minimize and the float button, does the same for that panel alone: it forgets the size and place remembered for it and fits it again where it is. A process or tool panel also has Default fit in the menu of its title bar (right-click the bar).

2.4.5One Window per Process and Tool

By default there is one Process window and one Tool window, and whatever we open takes the place of the one before. With Each process and tool in its own window every process and tool opens in a window of its own, docked or floating, and the others stay as they are; opening a process that already has a window brings that window to the front. With Display process system toolbar a thin bar along the bottom of these panels offers a drag handle to apply the settings by dropping them on an image, and Apply, Instance, Help and Reset (Apply and Cancel for a tool). Both options and Hide classic buttons are described with the Layout page (Preferences); a layout holds them, so applying a layout puts them back.

2.5Layouts

A layout is a named arrangement of the panels and toolbars, with the size and place of the window.

2.5.1The Session

The arrangement is saved when DSPX closes and put back when it starts, unless Start with in the Preferences (page Layout) names a layout, in which case DSPX starts with that layout instead. Where I left off, the default, puts the session back. A window that would be off every screen after a change, a monitor unplugged or another resolution or scaling, is brought back onto one: the main window, the floating panels and the floating toolbars.

2.5.2The Built-In Layouts

Seven layouts are built in. Pre-processing and Processing are arranged by the program, so they fit any screen; every panel is docked again from scratch and the Layers panel shares the History's place. Default, Syrup, Psycho'n, Fix Inside and PhotonChop are arrangements saved as they are.

Only Psycho'n shows the Process Explorer; Window > Process Explorer does in the others, and a layout of our own that we save with the Explorer shown shows it again.

The PhotonChop layout's two LaunchPads ship with DSPX. Applying the layout adds them to our LaunchPads when they are not there (again if we deleted them); once there, they are ours: an edit we make to them stays, and the layout docks them as they are.

2.5.3Our Own Layouts

Window > Layouts lists the built-in layouts, then ours in alphabetical order, the one in use checked. Choosing one arranges the workspace shown.

A layout arranges the workspace shown; the other workspaces keep their arrangements. A layout we save carries the process and tool windows of that workspace and the LaunchPads that are open and where, and applying it opens them in the workspace shown, leaving its other windows alone. It also carries the two toolbar choices of the Preferences, Buttons and Show at start (Layout); a layout we saved before they were part of it leaves them as they are. A built-in layout sets Buttons (icon and name, and icons only for Syrup, Psycho'n, Fix Inside and PhotonChop); Default, Syrup, Psycho'n, Fix Inside and PhotonChop also set Show at start, the others leave it as we set it. The image windows are Tabs in Pre-processing, Processing, Syrup and Psycho'n, cascaded in Default and Fix Inside, and tiled in PhotonChop.

A layout carries the options of the process and tool panels as well: Display process system toolbar, Hide classic buttons, Each process and tool in its own window, Auto-apply tools and Close panels after Apply. A layout we save keeps them as they are, applying a layout puts them back, and a layout saved before they were part of it leaves them as they are (except Close panels after Apply, which such a layout turns off). The built-in layouts carry their own: the system toolbar shown, the classic buttons shown, shared Process and Tool windows, Auto-apply tools on and Close panels after Apply off, except Default, which gives each process and tool its own window, Syrup, which has no system toolbar and closes panels after Apply, Psycho'n, which has no system toolbar, PhotonChop, which has no system toolbar and closes panels after Apply, and Fix Inside, which hides the classic buttons and gives each process and tool its own window. Themes do not carry these options any more.

2.5.4Layout Files

Window > Layouts > Export Layout... saves one of our layouts as a file, .dspxlayout: the layout in use when it is ours, else the one we choose. Built-in layouts are not exported: every DSPX has them. The file holds what a saved layout holds: the panels and toolbars, the process and tool windows, the LaunchPads that are open, the sides, the toolbar choices, the panel options and the arrangement of the image windows. The file window starts in the layouts folder of the data folder (General).

Import Layout... adds the layout of such a file to ours, on this computer or another. When we have a layout of that name, DSPX asks: Replace, Keep Both (the default: it is added as name 2) or Cancel. A file named as a built-in layout is added as Default 2 and the like, without asking. Applying an imported layout fits it to this computer's screens, as every layout is: a panel or toolbar that would be off the screens is brought back onto one.

The Layout page of the Preferences has the same list, with Save layout..., Export..., Import... and Reset to Default, and Start with, which chooses what DSPX starts with: Where I left off or any layout of the list.

2.6The Log

The Log panel is the program's record of what happened: the files opened and saved, what a process ran with and how it ended, what a file format could not keep, scripts' output, the messages of pre-processing runs, and every warning and error. Each line has the time; warnings and errors are colored in the theme's warning and error colors. The panel is read-only and keeps the last 5000 lines. When a process cannot do what was asked, the message in the status of the panel is short, and the Log has the reason: it is the first place to look (Reading the Log's Messages).

The Log is the one panel that can dock at the bottom. We select and copy its text as in any text field.

A right-click on the text opens a menu with Copy, Select All, Save Log..., which writes what the panel shows to a text file, and Clear Log, which empties the panel. A right-click on the panel's title bar has the last two.

2.7Undo, Redo and History

Edit > Undo (Ctrl+Z) and Edit > Redo (Ctrl+Y or Ctrl+Shift+Z) step through the history of the image in front. Every image has its own history. A process that changes the image is one step, an interactive tool's whole session is one step, and a script's run is one step. A step is undone and redone exactly, bit for bit.

2.7.1The History Panel

The History panel lists the steps of the image in front, from how it was opened (or "New image") to the latest, numbered, each with its title and, on a layered image, the layer it changed. A click on a row goes to that state, and the steps after it stay there until a new step replaces them. A summary at the bottom says, for example, "M31: step 4 of 6, 38.0 MB in memory, 2.10 GB on disk": how much of the image's undo data is in memory and how much is in the cache folder (the second part is left out while none is). A row's tooltip says how many tiles of the image the step kept, how much memory they would use, and where they are: in memory, on disk, or both (Undo Steps in the Cache Folder).

2.7.2Exporting the History

The steps applied to an image can be exported to repeat them on another image, as a script, as a blueprint or as a process container. Export... under the list, or Edit > Export History..., opens a window for the steps applied now, in order, up to the row of the current state. The steps that redo could bring back are not included. To export only some steps, Ctrl+click or Shift+click them first (a plain click still goes to that state); with none selected, all the applied steps are exported.

The window offers the three formats, a table with every step and a check or a dash for each format, the steps the chosen format leaves out with the reason, and the file to write. The file is named from the image and the format. An existing file is handled as the output files of pre-processing are (When an output file already exists in the Preferences: keep both, ask or replace; keep both is the default).

Only a step that a process run made can be exported, because only a process run keeps a process and its settings. Everything else cannot be repeated from the History, and is listed as not exported with the reason; in the script it is a comment at its place.

StepScriptBlueprintContainer
A process run from its panel, a process icon, a container, a blueprint or the guideYesYesYes, when PixInsight has the process
A tool's work: brush strokes, clone stamp, selection, clipboardNoNoNo
A layer operationNoNoNo
A selection or mask changeNoNoNo
A script's run (one step, whatever the script did)NoNoNo
A step of a project opened againNoNoNo

A step keeps its settings in memory, while the image is open. A project does not save them: after opening a project, its earlier steps are listed as recorded before settings were kept, and the steps applied afterwards can be exported. A script's dspx.run calls are part of the script's one step, and not steps of their own.

A selection, a mask or a layer that a step ran with changed what it did. They are not reproduced: the script notes each in a comment before the step, the blueprint in the note of the step, and the container ignores them. The same is said for a step that ran with PixInsight compatibility off, which a script or a blueprint runs with it on.

2.7.3Undo Steps in the Cache Folder

Undo steps keep the parts of the image that changed. The newest steps stay in memory, so that undoing the last thing is instant. The older ones move to the cache folder in the background, compressed, and are read back when we undo or redo them, which takes a fraction of a second even for a large image (about a tenth of a second for a 24-megapixel color image on a fast drive). While we look at the result, the step before it is read back in advance, when it fits in the memory kept for the newest steps and no process is running, so that pressing undo again finds it ready. Nothing needs setting, and the heavy work never has to compete with the undo steps for memory.

A step that deletes or flattens layers keeps those layers whole, in memory, as the layered image's own pixels are.

2.8LaunchPads

A LaunchPad is a small floating window of buttons, each of which launches something: a process with its settings, a tool, a script, a workflow, a file, a panel or a menu command. We make as many as we like, place them next to the image or dock them as toolbars, and keep them open at start. The LaunchPads page describes the pads, their look, the Manager, the editor and the import of PixInsight launchpads in full: LaunchPads. This section says how they fit in the window.

A LaunchPad beside an image
A LaunchPad in the window. The Main LaunchPad in DSPX Dark, floating over the image area next to a stretched image. Look at the group of common processes and the Manager button.

2.8.1A LaunchPad Docked as a Toolbar

A LaunchPad can be docked as a toolbar. It is still a LaunchPad, serving as a toolbar: the same buttons, the same editor, the same file. Docked, it sits in one of the main window's toolbar areas, at the top, the bottom or a side, like the program's own toolbars.

2.8.2Built-in LaunchPads

The program's toolbars of buttons, Tools, File, Window, Settings, Masks and Layers, are built-in LaunchPads, docked as toolbars by default. Until we change one, it is the toolbar it always was: the same buttons in the same order, in the same place, in the theme's colors.

2.9Process Icons on the Workspace

A process icon, PixInsight's term, is a process with its settings kept on the workspace itself: a small bar with the process's icon and a name made of its id and a number, such as Curves1. It is the quickest way to keep a few processes at hand for the session, next to the images they will be applied to. The Process Shelf is the other: a shared list of processes that is not tied to a workspace.

Process icons on the workspace behind two image windows
Process icons. A tiled workspace with three icons, Curves1, Blur1 and Blur2, one of them selected, and a tooltip over Blur2 listing the settings that differ from the defaults. Look at where the icons lie, behind the windows.

2.9.1Making Process Icons

Dropping any of these on the background of a workspace, or on the strip in Tabs, makes an icon there:

Process > Load Process Icons... does the same for files chosen in a dialog, on the workspace shown. The pointer shows a + when a drop will be taken: a process is taken over an image (applied), over the background or the strip (made an icon), and refused anywhere else.

2.9.2Where They Are

In Tile and Cascade, the icons lie on the workspace's background where they were dropped, always behind the image windows. In Tabs they are in a row in a thin strip under the image tabs, in the order of the row. The strip is shown while the workspace has icons, and while a process is dragged over the window, so that the first icon can be dropped. Window > Process Icon Strip hides it, as does the strip's right-click menu; it is available in Tabs only. A long row scrolls with the wheel.

2.9.3Names

A new icon is its process id and the lowest number no icon of the workspace has with it, so Blur1, Blur2, and Blur1 again once Blur1 has been renamed. An icon from a file or a shelf row keeps its name, made unique by adding a number. To rename one, press F2, choose Rename in its menu, or click the name of an icon that is already selected, and type in place: Enter renames, Esc leaves it. A name up to 40 characters, with any text, is accepted; one another icon of the workspace has (case ignored) or an empty one is refused, and the Log says why.

2.9.4Using Process Icons

2.9.5Selecting and Moving

A click selects an icon, Ctrl adds or takes away, Shift selects a run in the order of the row, a click on the background clears the selection, and a rubber band on the background selects the icons it touches. Dragging on the background moves the selected icons by the same amount; with Ctrl it copies them, with new names and the same settings. Along the strip a drag moves them in the row. Delete deletes the selection, after asking ("Delete the process icon Curves1?", "Delete 3 process icons?").

2.9.6The Icon's Menu

The right-click menu of an icon has:

Window > Arrange Icons lines the workspace's icons up in columns from a corner chosen in its submenu: Top Left, Top Right, Bottom Left or Bottom Right. The tooltip of an icon gives its name, its process and the settings that are not at their defaults, as the History panel gives them.

2.9.7Keeping Them

The icons of every workspace are saved for the next start when Keep process icons between sessions is on (Preferences, page General; on by default). With it off they are gone at the next start, and quitting with process icons asks whether to save them. A project keeps the icons of its workspaces.

2.10Projects

A project is the whole session on disk: the images, their histories, masks and selections, layers, metadata, windows, workspaces, the process panels' settings, and the Process Shelf. It is how we leave a piece of work and come back to it, with every step still undoable. A project is two things on disk: a manifest file, Orion.dspx, and a data folder beside it, Orion.dspx.data, with the images and the histories. Moving them together, to another computer, moves the project.

2.10.1The Commands

The project commands are in the File menu.

While a project is open the window's title names the project and DSPX, as in Orion - DSPX.

2.10.2What a Project Keeps

The save dialog, shown the first time a project is saved and for Save Project As, has nine choices, all ticked at first. Each has a tooltip, and the first two show their sizes.

The Save Project dialog
The Save Project dialog. The first save of a session of four images, all nine choices ticked, with the sizes beside Image data and Image history. Look at the line under Image data.

2.10.3Saving

Saving is careful. The new files are written under new names first, then the manifest is replaced, and only then are the old files removed, so a save that fails or is canceled leaves the old project whole. An image unchanged since the last save of the project keeps its files; a save after a few steps writes only what changed. The images are read on a thread of their own, so the window stays responsive, with "Saving the project: image 3 of 7", a bar and Cancel in the status line.

A save is refused, with the reason in the Log and in a box, while a process, a script, a workflow, a process on files or a container is running, and while a guided step runs or an image is held; a tool's session ends first, and one with changes asks whether to apply it, discard it or keep working. While the guide is waiting, the save goes ahead, but the run itself is not saved: the project keeps the images as they are now.

DSPX never silently overwrites a project. Save Project As onto another project asks (Replace or Cancel); Save Project asks before replacing a project that changed on disk since it was opened or saved here.

2.10.4Opening

Opening a project reads the manifest first. Each image comes from its data file or from its own file, looked for next to the project first, so a project moved with its images finds them, then by its full path. Files that are missing are listed in one dialog, where Locate... chooses the file (and finds the other missing files of the same folder in it) and Skip leaves the image out; Cancel leaves the session as it was, since nothing has closed yet. Then the session is replaced: every open image closes (those with unsaved changes ask), and the project's images open, each in its workspace and place, read on a thread of their own while the window keeps drawing.

An image that is skipped, or whose file cannot be read, stays in the project: Save Project keeps it and its files, and it opens again once its file is back. Save Project As to another place leaves it out, and the Log says so.

An image read from its own file, or from a file chosen with Locate..., is checked against the project's record of its pixels. If the file was saved over since, or is another image, the image opens as it is now, without its history and its window's state, and the Log says so. Histories are read last and held to the limits of the undo steps; if a limit drops the oldest steps, the Log says how many. Then masks, layers, screen stretches, process panels, the shelf (its rows are added, never twice), the windows, and the workspace that was shown come back.

Closing, quitting, or opening another project does not ask about an image that is unchanged since the open project was last saved; the others ask as usual.

A project made by a newer DSPX than the one opening it is refused with a message that names the version needed. Names the program does not know are listed in the Log and skipped. A history file that cannot be read (damaged, or made by a newer DSPX) loses only that image's history, and the project keeps the file.