as far as i know arcgis has some kind of update button.. so we could it this way as well.
(i know i should not propose something in the far future, but the colour theming should be extended in the future - providing different types of classification. Erwan/SIGLE did some first work on it (contained of the FOSS4G 2006 edition). I started to transfer the code but I lost it during an update because I did not check it in immediatly as i discovered some bug - so a "re-design" should also include thought on additional classification methods so a.. what i am going to tell was that i thought about adding classification capabilities. But actually Arnd proposed to have such a functionality external, which adds a new attribute with the result ???) stefan Martin Davis schrieb: > Sounds good to me, Larry. > > Having the Attribute dropdown always live might not be the 100% best > solution, but at least it will let the user avoid the latency issue. > Once it's out there and in use, a better approach might become apparent. > > I'm not crazy about the idea of an "Update Styles" button, because it's > nice to do this automatically. But it's also not nice of JUMP to block > for a long period of time unexpectedly. I guess a third approach would > be to prompt the user if he wants to continue if the style list > population is likely to take a long time. But that's got it's own > annoyance... > > M > > Larry Becker wrote: >> Hi Martin, >> >> Yea, I think enabling the Attribute dropdown all of the time would >> be acceptable. I am familiar with the code and can do it tonight if >> no one objects or has a better idea. >> >> regards, >> Larry >> >> On 9/12/07, Martin Davis <[EMAIL PROTECTED]> wrote: >> >>> One thing that is very annoying and that we never got around to fixing >>> in JUMP is the sometimes extremely poor responsiveness when enabling >>> Colour Theming on a layer. It often happens that when you click the >>> "Enable colour theming" checkbox JUMP decides that you want to theme on >>> FID and goes off and builds a list of colour styles for every single >>> feature in a layer. This can be VERY slow. >>> >>> A better approach would be to let the user choose exactly what he wants >>> to theme on, before the style list is created. I'm not sure what the >>> best workflow for this is. Options I can see are: >>> - let the Attribute dropdown be live all the time, and only build the >>> colour list when the Enable box is checked >>> - Only refresh the Styles list on user command, via a "Update styles" button >>> >>> There's probably other possibilities too. >>> >>> Has anyone thought of taking this on to improve? >>> >>> Martin >>> >>> -- >>> Martin Davis >>> Senior Technical Architect >>> Refractions Research, Inc. >>> (250) 383-3022 >>> >>> >>> ------------------------------------------------------------------------- >>> This SF.net email is sponsored by: Microsoft >>> Defy all challenges. Microsoft(R) Visual Studio 2005. >>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >>> _______________________________________________ >>> Jump-pilot-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel >>> >>> >> >> > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Jump-pilot-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
