Conversation
Update build flag in examples from C++11 to C++17 and add C++17 requirement to installation guide. Refactor code examples throughout documentation to use std::unique_ptr for memory management and std::string_view for efficient string passing. Clarify ownership model where Scene does not take ownership of entities. Add new section on memory management with smart pointers and update engine architecture to mention C++17 features.
- Update UI button example to use new UIVerticalLayout constructor and addElement method - Add comprehensive guide on handling forward declarations with std::unique_ptr - Cross-reference memory management section from scenes and entities documentation - Fix formatting and improve readability with consistent code blocks - Correct broken links to scenes and entities documentation
- Update logo size and add pixelated rendering - Implement custom color palette for light/dark modes - Simplify homepage title and improve spacing - Update sitemap dates and rebuild site assets
Ref/c++11 to c++17
Add visual architecture diagram to illustrate engine layers and improve documentation with new API reference pages, style guide, and migration guide for v0.9.0. The architecture document now provides comprehensive technical overview with detailed layer descriptions and system interactions.
- Add sin/cos functions and constants to Math module documentation - Update Actor, PhysicsActor, Entity constructors to use Scalar parameters - Replace float/int types with Scalar in physics collision structures - Document DisplayConfig pin configuration parameters for ESP32 - Clarify MAX_ENTITIES/MAX_LAYERS source location in Scene documentation
- Add section 7 to migration guide detailing Entity position refactoring from separate x/y to Vector2 position - Extend math module documentation with new Scalar functions (atan2, sign, is_equal_approx, is_zero_approx) - Document comprehensive Vector2 methods including geometric operations, interpolation, and utility functions
Update the "Last update" timestamps in multiple documentation HTML files from February 17, 2026 to February 18, 2026 to reflect recent documentation changes.
- Rewrite engine architecture to mention "Flat Solver" and specialized actor types - Add new API reference pages for StaticActor, RigidActor, and KinematicActor - Update PhysicsActor with new enums (PhysicsBodyType, CollisionShape) and methods - Completely rewrite CollisionSystem documentation to describe the new physics pipeline - Update collision_types.md to focus on enums, removing detailed geometry documentation - Revise the physics and collisions manual to reflect the new class hierarchy and usage - Update mkdocs.yml navigation and site URL - Regenerate sitemap with new pages and updated timestamps
- Add migration guide detailing changes from v0.9.0 to v0.9.1. - Update API references to reflect new solver pipeline, constants, and CCD. - Clarify that position integration is now handled by CollisionSystem. - Document fixed kinematic vs rigid actor interaction. - Update architecture and game development manuals with new pipeline details.
Feat/fixed point
Explain the new bounce flag property on PhysicsActor and detail the updated restitution calculation rules in the collision system. The bounce flag must be true on both colliding actors for restitution to apply; otherwise, restitution is zero. Micro-bouncing is prevented by a velocity threshold.
- Remove "v3.0" and version-specific tags from documentation to reflect current state - Add documentation for `is_on_ceiling`, `is_on_floor`, and `is_on_wall` methods in KinematicActor - Update migration guide to reference "Flat Solver" instead of versioned names
- Add comprehensive MusicPlayer integration guide with advanced examples - Create new memory management guide with C++17 smart pointers and ESP32 optimization - Add complete testing guide covering unit tests, integration, and CI/CD - Update Renderer API documentation with logical width/height methods - Add new documentation index with learning path and quick links - Update sitemap with new documentation pages and current dates
- Update mkdocs.yml navigation to reflect new version (v1.0.0) and add CHANGELOG - Update index.md with v1.0.0 core features and performance claims - Add performance optimization strategies section to engine_architecture.md - Update physics_and_collisions.md with new velocity API examples - Update collision_system.md with corrected pipeline terminology - Add hardware-specific DMA memory guidance to memory_management.md - Update code examples to use Scalar types and new velocity methods - Update resolution_scaling.md with v1.0.0 FPS analysis and DMA pipelining - Remove old migration guides (v0.9.0, v0.9.1) and add new CHANGELOG.md - Regenerate sitemap with updated timestamps
- Revise document structure to align with the current test tree, including a full list of unit test suites and correct include paths. - Split coverage scripts into platform-specific files for Windows and Linux, replacing the previous single coverage_check.py. - Add detailed PlatformIO configuration information and clarify test file naming conventions. - Enhance the overview section to provide a clearer introduction to testing practices for the PixelRoot32 Game Engine.
Update engine version and references in documentation files to reflect the final 1.0.0 release. This includes the testing guide and migration documentation for both markdown and generated HTML.
- Add input system guide covering button mapping, configuration, and platform differences - Add physics system guide detailing Flat Solver architecture, movement patterns, and performance tips - Add UI system guide explaining elements, layouts, styling, and common patterns - Update library version references from 0.2.0-dev to 1.0.0 in getting started guide - Refine changelog formatting for 1.0.0 stable release - Update site generation timestamps
Feat/physics system
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
1 participant
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.
No description provided.