Quote:
Originally Posted by Powerlord
This particular use-case is likely rare. I know for the most part, when I'm storing things in a KeyValues, I'm looking things up by the key and not the value.
|
"The Kviz block is either missing a KvizJumpToKey or KvizExists counter-intuitively adjusts the internal pointer. If KvizExists isn't setting the internal pointer, it's an additional call that's still being made every single time which is unnecessary in the default KeyValues code (because KvGotoNextKey moves the internal pointer forward one entry)."
One of the ideas behind Kvizzle is that you don't have to worry about the internal traversal stack. Kvizzle handles that for you. The path is always relative to the root (unless you use KvizJumpToKey).
Regarding performance, Kvizzle usually doesn't make more Kv-calls than your ordinary Kv-code does. If you access "A.B" it will navigate using two KvJumpToKey calls. Then, if you now specify "A.B.C" it knows it is already at "A.B", so it only makes one more KvJumpToKey call.
Similarly, if you access "A:nth-child(1)" and then "A:nth-child(2)", it knows it is already at the first child, so it will simply call KvGotoNextKey to access the second child.
"Incidentally, KeyValues doesn't need the counter variable either."
When coding Kvizzle, I wanted to make it as simple and easy to understand as possible. One common piece of code for all developers, is to loop through an array:
PHP Code:
for (new i = 0; i < count; i++) {
// ...
}
We have all seen these lines of code thousands of times. Intuitively, looping through nodes in a KeyValues structure should be similar. That's why I made it the way I did.
PHP Code:
for (new i = 1; KvizExists(kv, ":nth-child(%i)", i); i++) {
// ...
}
I like it this way. But I can also fully understand people that prefer the enumeration way, with GotoFirstSubKey and GotoNextKey. So I will try to come up with a way to incorporate that into Kvizzle.
"KvizGet* functions can't retrieve a default value because they're VFormat functions. Which makes me wonder what happens when the "Access" key doesn't exist. This would cause me to waste logic in PropHunt Redux setting the rotation and offset keys to "0 0 0" manually."
Unlike the normal Kv-functions, Kvizzle has Get-functions with and without default values.
PHP Code:
// If the path is not found, this will set value to "<not found>"
KvizGetString(kv, value, sizeof(value), "<not found>", "Admins:nth-child(10)");
// If the path is not found, this will leave value intact, and return false.
KvizGetStringExact(kv, value, sizeof(value), "Admins:nth-child(10)");
So... you're telling me that Admins:nth-child behaves differently based on the internal call stack? Shouldn't that be an absolute reference?
Note that I was not using KvJumpToKey and KvGoBack.
The
KvizJumpToKey and
KvizGoBack functions are not the same as their Kv* counterparts.
KvizJumpToKey makes all subsequent calls to Kviz* functions relative to that path.
Similarly, KvizGoBack make all subsequent calls to Kviz* functions relative to the earlier path (before JumpToKey).
You can of course nest these calls.
Thanks for your interest, by the way. I am really happy to receive some critique, and to have these discussions.
Linear Mode
