Repository navigation
MapWinGIS6 ActiveX Control and Modern Rendering Architecture - #10
Merged
pmeems merged 2 commits intoOct 25, 2026
Merged
Conversation
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
🟡 Changes recommended
Conflicting component and testing boundaries in the existing guidance must be reconciled with the new architecture baseline.
1 open issue
What changed in this PR
Documents the planned ActiveX and rendering architecture while keeping MapWinGIS.Core independent of COM and graphics APIs. No runtime code or dependencies change.
Changes:
- Defines component responsibilities, ownership, lifetimes, and rendering input boundaries.
- Describes runtime backend selection, CPU fallback, and GPU-independent testing.
- Clarifies compatibility expectations and distinguishes planned capabilities from implemented functionality.
| File | Description |
|---|---|
docs/ARCHITECTURE.md |
Adds the ActiveX/rendering design baseline and clarifies implementation status. |
Review effort: Balanced
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
pmeems
deleted the
phase-1-define-modern-activex-rendering-architecture
branch
October 25, 2026 19:21
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Motivation
Define a stable architecture before introducing the ActiveX control or renderer, while keeping MapWinGIS.Core independent of COM and graphics APIs.
Context and design
Documents component boundaries, ownership and lifetimes, runtime backend selection, CPU fallback and GPU-independent tests. The OCX initially composes internal rendering components; OpenGL remains optional, and GIS data and map state stay outside backend-specific resources. Legacy API parity and OpenCL are deferred.
Dependencies
None added. Existing VectorDataset/VectorLayer APIs are documented as data sources; a render-ready map scene is not yet implemented.