Hi all,
The current behaviour for Feature Info panel is different from previous
versions:
Now, when a Feature Info row is clicked, the corresponding feature is
automatically selected.
It is not possible to just flash the selected row, as the corresponding
feature is selected.
Furthermore, when a
Ok, I see this discussion: "LayerView/AttributeTable selection
synchronization" and in the code, I see a attributeTable is used in
FeatureInfoPanel.
Could an option be added to OJ to control the attributeTable selection ?
IMO, previous behaviour was fine: select row(s), then decide if you want a
m
Revision: 4942
http://sourceforge.net/p/jump-pilot/code/4942
Author: edso
Date: 2016-07-01 15:28:42 + (Fri, 01 Jul 2016)
Log Message:
---
fix tabs
Modified Paths:
--
core/trunk/src/com/vividsolutions/jump/io/datasource/ReaderWriterFileDataSource.java
M
Revision: 4943
http://sourceforge.net/p/jump-pilot/code/4943
Author: edso
Date: 2016-07-01 15:34:36 + (Fri, 01 Jul 2016)
Log Message:
---
add GeoJSON read support
Modified Paths:
--
core/trunk/etc/readme.txt
core/trunk/src/com/vividsolutions/jump/io
Revision: 4944
http://sourceforge.net/p/jump-pilot/code/4944
Author: edso
Date: 2016-07-01 15:36:23 + (Fri, 01 Jul 2016)
Log Message:
---
update
Modified Paths:
--
core/trunk/ChangeLog
Modified: core/trunk/ChangeLog
=
I kind of agree
stefan
On 7/1/16 07:14, Nicolas Ribot wrote:
Ok, I see this discussion: "LayerView/AttributeTable selection
synchronization" and in the code, I see a attributeTable is used in
FeatureInfoPanel.
Could an option be added to OJ to control the attributeTable selection ?
IMO, prev
Revision: 4945
http://sourceforge.net/p/jump-pilot/code/4945
Author: edso
Date: 2016-07-01 17:06:24 + (Fri, 01 Jul 2016)
Log Message:
---
leftover from geojson commit
Modified Paths:
--
core/trunk/pom.xml
Modified: core/trunk/pom.xml
===
hey Jukka,
please try r4945 or later.
..ede
On 27.06.2016 11:47, Rahkonen Jukka (MML) wrote:
> Yes, sure, having all as strings is a good start.
>
>
> -Jukka-
>
> edgar soldin wrote:
>
>> Jukka,
>
>> could you live with all attributes being read as Strings for now? ..ede
>
> On 27.06.2016
marvelous Ede!
GeoJSON is more than a hipster format nowadays ;)
stefan
On 7/1/16 15:04, edgar.sol...@web.de wrote:
> hey Jukka,
>
> please try r4945 or later.
>
> ..ede
>
> On 27.06.2016 11:47, Rahkonen Jukka (MML) wrote:
>> Yes, sure, having all as strings is a good start.
>>
>>
>> -Jukka-