PGE History Manager

Description: General discussion regarding the current engine development.
Moderator: Moderators

Which system would you like to see?

The old history system (less memory, but less reliable)
0
No votes
The new history system (more reliable, but more memory)
6
Squishy Rex, Wohlstand, h2643, tb1024, Alucard, Veudekato
100%
 
Total voters: 6
Kevsoft M
Topic author, Angry developer
Angry developer
Avatar
Kevsoft M
Topic author, Angry developer
Angry developer
Age: 19
Reputation: 77
Posts: 376
Joined: 26 Apr 2014
Location: Austria

Post #1by Kevsoft » 18 Jan 2015, 10:59

I am currently rewriting the history manager and currently have a design decision to make.

The old system did always the opposite of the actions it recorded, but when a history operation is missing the whole system get messed up.
Anyway, I can redesign the new system that it will save up the state of the old data and the state of the new data. However, it will use more memory.

So in short:
- The old system Pros:
Does save memory.


- The old system Cons:
This system is not reliable.


- The new system Pros:
Will really restore the last operation on their exact position.

- The old system Cons:
Will cost more memory space.
▬▬▬▬▬▬▬▬▬▬ஜ۩۞۩ஜ▬▬▬▬▬▬▬▬ Signature.start() ▬▬▬▬▬▬▬▬▬▬ஜ۩۞۩ஜ▬▬▬▬▬▬▬
Image
Wohlstand in interview:
Spoiler
Image

▬▬▬▬▬▬▬▬▬▬ஜ۩۞۩ஜ▬▬▬▬▬▬▬▬ Signature.end() ▬▬▬▬▬▬▬▬▬▬ஜ۩۞۩ஜ▬▬▬▬▬▬▬▬

Squishy Rex M
Advanced Moderator
Advanced Moderator
Avatar
Squishy Rex M
Advanced Moderator
Advanced Moderator
Age: 22
Reputation: 114
Posts: 254
Joined: 24 Feb 2014
Location: Australia

Post #2by Squishy Rex » 18 Jan 2015, 13:10

To be honest, I would much rather sacrifice a little bit of memory space to have a more reliable history system as I'm sure others would agree. I'd definitely like to see a new history system.
Squishy Rex's CGFX Pack v1.7
Image
To show your support add any of these Userbars to your Signature!
Image

Veudekato M
Viscount
Viscount
Avatar
Veudekato M
Viscount
Viscount
Reputation: 57
Posts: 369
Joined: 19 Feb 2014
Location: Russia

Post #3by Veudekato » 18 Jan 2015, 19:19

i think old system enough (better) . But it saves not all changes in level(And new too?) If you do something wrong, and dont seen this, you make many changes in level. And you need to remove it. How it can be in new system? Or i didnt understood
My channel (PlatGEnWohl news and tutorials , smbx tests):
http://www.youtube.com/channel/UC6h-42umT14iR1wa3VkOs3Q

Wohlstand M
Lead Developer
Lead Developer
Avatar
Wohlstand M
Lead Developer
Lead Developer
Age: 25
Reputation: 320
Posts: 1297
Joined: 15 Feb 2014
Location: Moscow, Russia
Website Skype YouTube

Post #4by Wohlstand » 18 Jan 2015, 20:52

Veudekato wrote:i think old system enough (better) . But it saves not all changes in level(And new too?) If you do something wrong, and dont seen this, you make many changes in level. And you need to remove it. How it can be in new system? Or i didnt understood
Here about internal history implementation: what we will remember: whole entry of item or some setting of item.
If we will remember whole entry of item, we doesn't check each property and this way taking more RAM (by anyway, each item entry takes ~ 10-30 bytes)
But when we remember some settings, this will store only some setting values but not whole entry. This way requiring to implementation remembering for each setting when it was created (usually new settings aren't remembers because they aren't implemented into history manager).


Return to “Engine Development”

Who is online (over the past 5 minutes)

Users browsing this forum: 1 guest