• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!

WindowSmasher's Full Screen Window System (Made back in 2007, updated)

This bundle is marked as useful / simple. Simplicity is bliss, low effort and/or may contain minor bugs.
A Full screen Window System (Made by me back in 2007), WindowSmasher.

A Window system template made for buying items or units or whatever you put in there.
Some guy apparently updated the system and made it more detailed for purchasing units, however the idea was to be able to remake it to a item window for example.

I will upload the updated version as I no longer have access to my version.

Cred to Jaydenn for continuing a project I started and reuploading it.

Hope it still works fine, this was very "cool" back in 2007 and one of my best works.

// WindowSmasher
Contents

Window System v1.6 Final (Map)

Reviews
Pyrogasm
There are a massive number of location, sfx, and floating text memory leaks all throughout the triggers for this system. For this to ever be approvable they will all have to be fixed. However, the biggest problem with this system is that in 1.31...
Level 38
Joined
Feb 27, 2007
Messages
4,951
There are a massive number of location, sfx, and floating text memory leaks all throughout the triggers for this system. For this to ever be approvable they will all have to be fixed. However, the biggest problem with this system is that in 1.31 (which is currently on the PTR) we will have new UI element natives to create and display UI windows at will. Systems using methods like this one will become obsolete overnight unless they're updated to use those new natives (which will probably exist in GUI, though I'm unsure).
 
This was made to prove that a full screen window mode was possible in GUI back in the days (2007). I figured I'd put the "template" out there to inspire, not updating this anymore.

There are a massive number of location, sfx, and floating text memory leaks all throughout the triggers for this system. For this to ever be approvable they will all have to be fixed. However, the biggest problem with this system is that in 1.31 (which is currently on the PTR) we will have new UI element natives to create and display UI windows at will. Systems using methods like this one will become obsolete overnight unless they're updated to use those new natives

Given the state of the resource not being net-safe (replay-safe), this will have to be deprecated and moved to Substandard.
 
Top