I could be wrong, but I can't think of any major benefits of having it as a list.
The array keeps it small in size and simple. What can a list do for it?
On Thu, 17 Feb 2005, robotron:2084 wrote:
On Thu, 17 Feb 2005 18:54:19 +0100, Sebastian Dransfeld <[EMAIL PROTECTED]> wrote:Implemented desktops as a list, instead of an array. Moved e_desk_current_get, e_desk_at_xy_get to e_zone_desk_current_get and e_zone_desk_at_xy_get.
Anyone against?
i am not necessarily against this move, and perhaps i am out of the loop, but what was wrong with keeping desktops in an array? i don't see any particular need to prefer one over the other, other than the array code is already in use and it has seen more testing than the list code. i don't think of e desktops as objects which will often fluctuate in size, which is the scenario i think the list code would have best served.
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
//========================================================\\ || D. Hageman <[email protected]> || \\========================================================//
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ enlightenment-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
