Re: [pmapper-users] QueryEditor bug/question

2011-02-07 Thread Thomas RAFFIN 
Hi,

You've just found a real bug.

I will correct it in the dev version asap. If you need it quickly, just 
modify the file pmapper/plugins/queryeditor/queryeditor.php:
- search the line with $layers = 
$_SESSION['pluginsConfig']['queryeditor']['queryableLayers']['queryableLayer'];
- add just after it:
if ($layers  array_key_exists('name', $layers)) $layers = array($layers);

Thanks

Thomas

Le 04/02/2011 15:48, Dejan Gambin a écrit :
 Hi,

 I don't know if this is a bug or I am doing some stupid mistake:

 When I set layersType to 2 and have just one queryable layer I get 2 (and 
 wrong) values in Layer name select list (instead of one). I have this defined 
 in xml file:

  pluginsConfig
   queryeditor
   layersType2/layersType
   queryableLayers
   queryableLayer
   namekbroj/name
   descriptionKBR/description
   /queryableLayer
   /queryableLayers
   dlgTypedynwin/dlgType
   /queryeditor
  /pluginsConfig

 The values I get in Layer name select list are k and K

 thx for any info

 regards, dejan


 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users




--
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] QueryEditor bug/question

2011-02-07 Thread Dejan Gambin 
Thanks Thomas,

I have several more questions, neither one is very important but it is good to 
know the options:

1. When I open the dialog I get 3 comparison fields displayed - 
queryeditor-attributeCriteriaComparisonNone, 
queryeditor-attributeCriteriaComparisonNum and 
queryeditor-attributeCriteriaComparisonTxt. As I can they get hidden in 
setAttributeType function, that is called by setAttributeName called by 
setLayerName. setLayerName is also called by reset() function that is again 
called by ready() function which sets default interface status. So, should the 
two comparison fields be hidden by default?

2. I am using Quesry Editor by manually changing the values in Generated 
Query frame. When I have focus in this frame, every press on the arrow key 
makes the map pan. Is it possible to disable panning when focus is in this 
frame?

Thanks very much. This plugin is of so much help :D

regards, dejan
On 7. vel. 2011., at 11:49, Thomas RAFFIN wrote:

 Hi,
 
 You've just found a real bug.
 
 I will correct it in the dev version asap. If you need it quickly, just 
 modify the file pmapper/plugins/queryeditor/queryeditor.php:
 - search the line with $layers = 
 $_SESSION['pluginsConfig']['queryeditor']['queryableLayers']['queryableLayer'];
 - add just after it:
 if ($layers  array_key_exists('name', $layers)) $layers = array($layers);
 
 Thanks
 
 Thomas
 
 Le 04/02/2011 15:48, Dejan Gambin a écrit :
 Hi,
 
 I don't know if this is a bug or I am doing some stupid mistake:
 
 When I set layersType to 2 and have just one queryable layer I get 2 (and 
 wrong) values in Layer name select list (instead of one). I have this 
 defined in xml file:
 
 pluginsConfig
  queryeditor
  layersType2/layersType
  queryableLayers
  queryableLayer
  namekbroj/name
  descriptionKBR/description
  /queryableLayer
  /queryableLayers
  dlgTypedynwin/dlgType
  /queryeditor
 /pluginsConfig
 
 The values I get in Layer name select list are k and K
 
 thx for any info
 
 regards, dejan
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users
 
 
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world? 
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users


--
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] QueryEditor bug/question

2011-02-07 Thread Thomas RAFFIN 


Le 07/02/2011 12:37, Dejan Gambin a écrit :
 Thanks Thomas,

 I have several more questions, neither one is very important but it is good 
 to know the options:

 1. When I open the dialog I get 3 comparison fields displayed - 
 queryeditor-attributeCriteriaComparisonNone, 
 queryeditor-attributeCriteriaComparisonNum and 
 queryeditor-attributeCriteriaComparisonTxt. As I can they get hidden in 
 setAttributeType function, that is called by setAttributeName called by 
 setLayerName. setLayerName is also called by reset() function that is again 
 called by ready() function which sets default interface status. So, should 
 the two comparison fields be hidden by default?

OK, I've done the changes. I will commit them ASAP.

 2. I am using Quesry Editor by manually changing the values in Generated 
 Query frame. When I have focus in this frame, every press on the arrow key 
 makes the map pan. Is it possible to disable panning when focus is in this 
 frame?


What is your p.mapper version? And your web browser ?


 Thanks very much. This plugin is of so much help :D

You're welcomed!

Thomas


 regards, dejan
 On 7. vel. 2011., at 11:49, Thomas RAFFIN wrote:

 Hi,

 You've just found a real bug.

 I will correct it in the dev version asap. If you need it quickly, just
 modify the file pmapper/plugins/queryeditor/queryeditor.php:
 - search the line with $layers =
 $_SESSION['pluginsConfig']['queryeditor']['queryableLayers']['queryableLayer'];
 - add just after it:
 if ($layers  array_key_exists('name', $layers)) $layers = array($layers);

 Thanks

 Thomas

 Le 04/02/2011 15:48, Dejan Gambin a écrit :
 Hi,

 I don't know if this is a bug or I am doing some stupid mistake:

 When I set layersType to 2 and have just one queryable layer I get 2 (and 
 wrong) values in Layer name select list (instead of one). I have this 
 defined in xml file:

  pluginsConfig
 queryeditor
 layersType2/layersType
 queryableLayers
 queryableLayer
 namekbroj/name
 descriptionKBR/description
 /queryableLayer
 /queryableLayers
 dlgTypedynwin/dlgType
 /queryeditor
  /pluginsConfig

 The values I get in Layer name select list are k and K

 thx for any info

 regards, dejan


 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users



 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users




--
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] QueryEditor bug/question

2011-02-07 Thread Dejan Gambin 

On 7. vel. 2011., at 14:18, Thomas RAFFIN wrote:

 
 
 Le 07/02/2011 12:37, Dejan Gambin a écrit :
 Thanks Thomas,
 
 I have several more questions, neither one is very important but it is good 
 to know the options:
 
 1. When I open the dialog I get 3 comparison fields displayed - 
 queryeditor-attributeCriteriaComparisonNone, 
 queryeditor-attributeCriteriaComparisonNum and 
 queryeditor-attributeCriteriaComparisonTxt. As I can they get hidden in 
 setAttributeType function, that is called by setAttributeName called by 
 setLayerName. setLayerName is also called by reset() function that is again 
 called by ready() function which sets default interface status. So, should 
 the two comparison fields be hidden by default?
 
 OK, I've done the changes. I will commit them ASAP.
 
 2. I am using Quesry Editor by manually changing the values in Generated 
 Query frame. When I have focus in this frame, every press on the arrow key 
 makes the map pan. Is it possible to disable panning when focus is in this 
 frame?
 
 
 What is your p.mapper version? And your web browser ?
The version is 4.0. Browser is FF.
 
 
 Thanks very much. This plugin is of so much help :D
 
 You're welcomed!
 
 Thomas
 
 
 regards, dejan
 On 7. vel. 2011., at 11:49, Thomas RAFFIN wrote:
 
 Hi,
 
 You've just found a real bug.
 
 I will correct it in the dev version asap. If you need it quickly, just
 modify the file pmapper/plugins/queryeditor/queryeditor.php:
 - search the line with $layers =
 $_SESSION['pluginsConfig']['queryeditor']['queryableLayers']['queryableLayer'];
 - add just after it:
 if ($layers  array_key_exists('name', $layers)) $layers = array($layers);
 
 Thanks
 
 Thomas
 
 Le 04/02/2011 15:48, Dejan Gambin a écrit :
 Hi,
 
 I don't know if this is a bug or I am doing some stupid mistake:
 
 When I set layersType to 2 and have just one queryable layer I get 2 (and 
 wrong) values in Layer name select list (instead of one). I have this 
 defined in xml file:
 
 pluginsConfig
queryeditor
layersType2/layersType
queryableLayers
queryableLayer
namekbroj/name
descriptionKBR/description
/queryableLayer
/queryableLayers
dlgTypedynwin/dlgType
/queryeditor
 /pluginsConfig
 
 The values I get in Layer name select list are k and K
 
 thx for any info
 
 regards, dejan
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users
 
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users
 
 
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world? 
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users


--
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
___
pmapper-users mailing list
pmapper-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pmapper-users

Re: [pmapper-users] QueryEditor bug/question

2011-02-07 Thread Thomas RAFFIN 
With my version I don't have this issue. Does it appear with printing 
dialog for instance?

Maybe those changes could help:
- http://svn.pmapper.net/trac/changeset/1079
- 
http://svn.pmapper.net/trac/changeset/1120/trunk/pmapper/javascript/src/pm.zoombox.js

Are you able to test the development version?

Le 07/02/2011 14:37, Dejan Gambin a écrit :
 On 7. vel. 2011., at 14:18, Thomas RAFFIN wrote:


 Le 07/02/2011 12:37, Dejan Gambin a écrit :
 Thanks Thomas,

 I have several more questions, neither one is very important but it is good 
 to know the options:

 1. When I open the dialog I get 3 comparison fields displayed - 
 queryeditor-attributeCriteriaComparisonNone, 
 queryeditor-attributeCriteriaComparisonNum and 
 queryeditor-attributeCriteriaComparisonTxt. As I can they get hidden in 
 setAttributeType function, that is called by setAttributeName called by 
 setLayerName. setLayerName is also called by reset() function that is again 
 called by ready() function which sets default interface status. So, should 
 the two comparison fields be hidden by default?
 OK, I've done the changes. I will commit them ASAP.

 2. I am using Quesry Editor by manually changing the values in Generated 
 Query frame. When I have focus in this frame, every press on the arrow key 
 makes the map pan. Is it possible to disable panning when focus is in this 
 frame?

 What is your p.mapper version? And your web browser ?
 The version is 4.0. Browser is FF.

 Thanks very much. This plugin is of so much help :D
 You're welcomed!

 Thomas


 regards, dejan
 On 7. vel. 2011., at 11:49, Thomas RAFFIN wrote:

 Hi,

 You've just found a real bug.

 I will correct it in the dev version asap. If you need it quickly, just
 modify the file pmapper/plugins/queryeditor/queryeditor.php:
 - search the line with $layers =
 $_SESSION['pluginsConfig']['queryeditor']['queryableLayers']['queryableLayer'];
 - add just after it:
 if ($layers   array_key_exists('name', $layers)) $layers = 
 array($layers);

 Thanks

 Thomas

 Le 04/02/2011 15:48, Dejan Gambin a écrit :
 Hi,

 I don't know if this is a bug or I am doing some stupid mistake:

 When I set layersType to 2 and have just one queryable layer I get 2 (and 
 wrong) values in Layer name select list (instead of one). I have this 
 defined in xml file:

  pluginsConfig
   queryeditor
   layersType2/layersType
   queryableLayers
   queryableLayer
   namekbroj/name
   descriptionKBR/description
   /queryableLayer
   /queryableLayers
   dlgTypedynwin/dlgType
   /queryeditor
  /pluginsConfig

 The values I get in Layer name select list are k and K

 thx for any info

 regards, dejan


 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical 
 server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users



 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users


 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users




--
The modern datacenter depends on network connectivity to access resources
and provide services. The best practices for maximizing a physical server's
connectivity to a physical network are well understood - see how these
rules translate into the virtual world? 
http://p.sf.net/sfu/oracle-sfdevnlfb
___
pmapper-users mailing list

Re: [pmapper-users] QueryEditor bug/question

2011-02-07 Thread Dejan Gambin 
You are right. It doesn't happen in 4.1 :D

dejan
On 7. vel. 2011., at 14:50, Thomas RAFFIN wrote:

 With my version I don't have this issue. Does it appear with printing 
 dialog for instance?
 
 Maybe those changes could help:
 - http://svn.pmapper.net/trac/changeset/1079
 - 
 http://svn.pmapper.net/trac/changeset/1120/trunk/pmapper/javascript/src/pm.zoombox.js
 
 Are you able to test the development version?
 
 Le 07/02/2011 14:37, Dejan Gambin a écrit :
 On 7. vel. 2011., at 14:18, Thomas RAFFIN wrote:
 
 
 Le 07/02/2011 12:37, Dejan Gambin a écrit :
 Thanks Thomas,
 
 I have several more questions, neither one is very important but it is 
 good to know the options:
 
 1. When I open the dialog I get 3 comparison fields displayed - 
 queryeditor-attributeCriteriaComparisonNone, 
 queryeditor-attributeCriteriaComparisonNum and 
 queryeditor-attributeCriteriaComparisonTxt. As I can they get hidden in 
 setAttributeType function, that is called by setAttributeName called by 
 setLayerName. setLayerName is also called by reset() function that is 
 again called by ready() function which sets default interface status. So, 
 should the two comparison fields be hidden by default?
 OK, I've done the changes. I will commit them ASAP.
 
 2. I am using Quesry Editor by manually changing the values in Generated 
 Query frame. When I have focus in this frame, every press on the arrow 
 key makes the map pan. Is it possible to disable panning when focus is in 
 this frame?
 
 What is your p.mapper version? And your web browser ?
 The version is 4.0. Browser is FF.
 
 Thanks very much. This plugin is of so much help :D
 You're welcomed!
 
 Thomas
 
 
 regards, dejan
 On 7. vel. 2011., at 11:49, Thomas RAFFIN wrote:
 
 Hi,
 
 You've just found a real bug.
 
 I will correct it in the dev version asap. If you need it quickly, just
 modify the file pmapper/plugins/queryeditor/queryeditor.php:
 - search the line with $layers =
 $_SESSION['pluginsConfig']['queryeditor']['queryableLayers']['queryableLayer'];
 - add just after it:
 if ($layers   array_key_exists('name', $layers)) $layers = 
 array($layers);
 
 Thanks
 
 Thomas
 
 Le 04/02/2011 15:48, Dejan Gambin a écrit :
 Hi,
 
 I don't know if this is a bug or I am doing some stupid mistake:
 
 When I set layersType to 2 and have just one queryable layer I get 2 
 (and wrong) values in Layer name select list (instead of one). I have 
 this defined in xml file:
 
 pluginsConfig
  queryeditor
  layersType2/layersType
  queryableLayers
  queryableLayer
  namekbroj/name
  descriptionKBR/description
  /queryableLayer
  /queryableLayers
  dlgTypedynwin/dlgType
  /queryeditor
 /pluginsConfig
 
 The values I get in Layer name select list are k and K
 
 thx for any info
 
 regards, dejan
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical 
 server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users
 
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical 
 server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual world?
 http://p.sf.net/sfu/oracle-sfdevnlfb
 ___
 pmapper-users mailing list
 pmapper-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/pmapper-users
 
 
 
 
 --
 The modern datacenter depends on network connectivity to access resources
 and provide services. The best practices for maximizing a physical server's
 connectivity to a physical network are well understood - see how these
 rules translate into the virtual