I moved to a new repository for mudlet2+ development. Those who liked following my branch can follow along here:
https://github.com/Chris7/Mudlet2/tree/mudletDev
Summary of changes:
6-9-2013
Variable GUI is in place, you can:
add, delete, rename, recast variables, as well as reorder them via drag & drop. - Needs lot of testing/feedback from compilers to get any bugs out before being prime-time.
2-16-2013
script based ways to: install, sync, uninstall, get path of modules
downloadFile can use https
mudlet event duplication fixed
doors on area exits aren't offset
Mudlet2+ Branch
Re: Mudlet2+ Branch
Sweet. Watch set. Thanks.
Re: Mudlet2+ Branch
Newest stuff added:
script based ways to: install, sync, uninstall, get path of modules
downloadFile can use https
mudlet event duplication fixed
doors on area exits aren't offset
script based ways to: install, sync, uninstall, get path of modules
downloadFile can use https
mudlet event duplication fixed
doors on area exits aren't offset
Re: Mudlet2+ Branch
The exitRedesign branch doesn't compile atm, due to the Fix: setExitWeight won't accept invalid exits for setting room weights. commit directly accessing private members of TRoom.h. Maybe it should be using the TRoom->get<Exit>()'s instead?
Re: Mudlet2+ Branch
For anyone who likes the bleeding edge, please test out this branch:
https://github.com/Chris7/Mudlet2/tree/variableGUI
and stress test the hell out of it.
https://github.com/Chris7/Mudlet2/tree/variableGUI
and stress test the hell out of it.
Re: Mudlet2+ Branch
That 'Toggle Hidden Variables' label gets a little annoying. Could you hide() that unless the variables are actually selected and visible?
Re: Mudlet2+ Branch
This is pretty damned neat. Loving this. I have a question, though: If I select a bunch of vars to be saved, is that selection persistent through profile exports with the package exporter?
Re: Mudlet2+ Branch
The toggle hidden variables label now toggles. I need to serialize hidden variables as well, which I'll push out soon enough.
Variables aren't exported in a package exporter, and I don't envision them ever being. Packages/modules should have a variable initialization routine, and use conventions like:
On a good note: Anyone else besides kevutian/vadi test this out? I'm surprised there aren't a bunch of crash reports
Variables aren't exported in a package exporter, and I don't envision them ever being. Packages/modules should have a variable initialization routine, and use conventions like:
To initialize but not overwrite user customizations if they already exist.
On a good note: Anyone else besides kevutian/vadi test this out? I'm surprised there aren't a bunch of crash reports
Re: Mudlet2+ Branch
Some updated on GUI:
better duplicate detection
variables can be searched for
hidden variables serialize
panic protection added to prevent seg faults
can detect and list out table keys that are non key/number such as tables/functions
variables are sorted so they're easier to find
better duplicate detection
variables can be searched for
hidden variables serialize
panic protection added to prevent seg faults
can detect and list out table keys that are non key/number such as tables/functions
variables are sorted so they're easier to find
Re: Mudlet2+ Branch
Were aware of this? Only happens on 3.0.
Saracen: Fatal error: ./mudlet-lua/lua/geyser/GeyserLabel.lua:113: bad argument #1 to 'unpack' (table expected, got string).
Saracen: Fatal error: ./mudlet-lua/lua/geyser/GeyserLabel.lua:113: bad argument #1 to 'unpack' (table expected, got string).