Fixed Possible division through 0

[hackepeter101]

#107

[Copilot]

Pull request overview

Guards the FPS calculation in the 14-bit VGA demo against a division-by-zero when millis() returns 0, addressing issue #107.

Changes:

• Caches millis() into a local unsigned long t.
• Only performs the (f++ * 1000) / t division when t > 0; otherwise resets the frame counter.

Comments suppressed due to low confidence (1)

examples/VGADemo14Bit/VGADemo14Bit.ino:46

• When t == 0 (the only moment millis() returns 0, which is essentially just at boot), this branch prints the "fps: " label without any following number, leaving the display in an inconsistent state. Consider printing a placeholder (e.g. 0) in the else branch so the output always has the same structure.

	else{
		f = 0; //starting FPS calculation again from frame 0
	}

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 2 comments.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.