Hey guys, In commit 63771 I added support for adding additional data to edje signals, and in commit 63773 I added additional info to entry,changed,user which allows users of the API to implement undo/redo nicely.
It should work just fine for "simple" entries but there's still one issue I'm aware of with entries that have formats (redo will miss the format in some cases). I went with the regular edje way and did it with signals. To be honest, I don't like the "delayed" invocation that much, I prefer the smart callbacks instant call behaviour. I just want to hear what you think about what's done there ATM and also, if you have better ideas. I'd like to hear your thoughts about both the method of passing additional info with signals (may have other uses as well) and about the implementation of the change info. Thanks, Tom. ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity and more. Splunk takes this data and makes sense of it. Business sense. IT sense. Common sense. http://p.sf.net/sfu/splunk-d2dcopy1 _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
