How kessity/test1 works
Project type and purpose
• From the file tree and README, this is a LabWindows / CVI 2017 desktop application written in C. It uses .UIR (User Interface Resource) files for GUI panels, a splash screen, and a small database interface (cvi_db.h). It appears to be a monolithic, callback-driven test application.
File structure
• Top-level files:
• MAIN.UIR, splash.uir – GUI panel definitions for the main window and splash screen.
• MAIN.c, mainTdm.c, speical0.c, splash.c, common.c – C source modules implementing callbacks, business logic, and helpers.
• MAIN.h, splash.h, cvi_db.h – headers for public APIs, callbacks, and DB functions.
• main.prj – LabWindows / CVI project file.
• This shows a UI layer (.UIR + .c/.h callbacks), a “common” utility layer, and a lightweight DB interface.
Key advice
• Be precise about each file’s role (e.g., MAIN.UIR defines the main panel layout; MAIN.c implements its callbacks).
• Splash screen’s lifecycle (load → init → handoff to main UI).
• Single-process, callback-driven nature—no hidden external services.