The way you are testing - using the members method is not going to
work that well (the catalog is willing to cache member titles if I
remember it was something Jesse added). Remember that these are
handles to the external resource and we do our best to put off using
them until needed.
Can you chec
I have added the instructions for turning on the heap widget to a page
of debugging tips:
- http://udig.refractions.net/confluence/display/DEV/7+Debugging+Tips
Jody
On Thu, Jun 4, 2009 at 1:25 AM, David Middlecamp
wrote:
> Thanks Mark and Jody for the quick reply!
>
> I'm glad there wasn't any
Not a problem; we had nice Thai food before hand so it was still a fun evening.
If you try the trace settings mentioned in the earlier email you
should be able to reproduce my results; also note that this test was
on trunk (so you may actually have a leak in 1.1.x I am not sure).
In testing Jesse
Delete Feature problems.
Key: UDIG-1522
URL: http://jira.codehaus.org/browse/UDIG-1522
Project: uDIG
Issue Type: Bug
Components: tools and editing
Affects Versions: UDIG 1.2.M4
Environment: Win
Thanks Mark and Jody for the quick reply!
I'm glad there wasn't any serious memory leak, hope I didn't raise any
false alarms. Maybe what I was seeing is just uDig and the postgres
driver warming up? We've been trying to tweak our memory use,
and garbage collection settings for low-end hardwar
Hello again,
I tried:
CatalogPlugin cp = CatalogPlugin.getDefault();
ICatalog catalog = cp.getLocalCatalog();
List resueltos = null;
try {
resueltos = catalog.members(new NullProgressMonitor() );
} catch (IOException e1) {
e1.printStackTrace();
}
for(int i=0; imailto:udig-devel-bou
I have put another 15mins into redrawing and panning; and have not run
out of memory. I can make memory use go up and down by adding and
removing layers - this is to be expected since we keep a raster per
layer in order to draw the features into. If anyone wants a rainy day
project we could really
Hi Gabriel:
The readme in the udig arcsde plugin talks about not replacing the
"empty" jars you provided; right now those empty jars are filling up
my log with zip exceptions -- all the time :-) Can you replace these
with a valid empty jar file?
Jody
PS. Hi Andrea apparently we did not cause thi
[...]
>> I am starting to get afraid that this might explode. :)
>
> Okay "stop drop and roll"
> - stop thinking up problems we do not have right now
> - drop crazy ui ideas to solve problems we do not have yet
> - roll on getting us netCDF reading so we can do live experimenting :-)
Okky dokky, I
>> I am starting to suspect that you are going to want:
>> - a global slider for time
>> - a style page for time; in which the user can choose "the default"
>> which is the global slider; or a specific time - kind of like
>> "pinning" a layer in time
>
> That is exactly what should be there.
>
>> N
>> That is not the problem. The problem is bound to the case in which we
>> have two netcdf files, both with time layers and vertical (say for
>> example elevation) layers.
>
> If they are both elevation layers; even if in different units; we
> *could* make use of a global elevation slider in order
Hi Admin:
Svn up; and the refractions website is down for me again today. I
think we are ready to shut off the geotools svn repository if that
would help? We have also migrated a lot of development environments
away from the refractions lists.refractions.net/m2 server which should
of decreased the
> That is not the problem. The problem is bound to the case in which we
> have two netcdf files, both with time layers and vertical (say for
> example elevation) layers.
If they are both elevation layers; even if in different units; we
*could* make use of a global elevation slider in order to chan
[...]
> The handling of the different sliders in the navigation model should
> be pretty easy ...
> just like we layers that do not have a sense of time (say a base tile
> server layer) will not respond as time changes; layers that do not
> have height would remain unchanged if you changed the heig
You can provide a description of the dimensions and so on of the layer
as part of its description (or even title).
The handling of the different sliders in the navigation model should
be pretty easy ...
just like we layers that do not have a sense of time (say a base tile
server layer) will not re
> My thought would not to display the deegrees of freedom (space / time
> / height) and only list the variables. The idea is to identify a
> dataset (ie a variable) and then to allow the user a visual way to
> navigate through the dataset.
>
> So lon/lat in your example...
That would be good, addi
16 matches
Mail list logo
