[sc-issues] [Issue 76137] cannot access two dimensio nnal array

2008-01-10 Thread fst
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76137


User fst changed the following:

What|Old value |New value

 Assigned to|spreadsheet   |er





--- Additional comments from [EMAIL PROTECTED] Thu Jan 10 10:36:09 + 
2008 ---
Hi Eike,

could you comment on this one and close it if applicable ?

Thanks

Frank

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sc-issues] [Issue 76137] cannot access two dimensio nnal array

2008-01-10 Thread er
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76137


User er changed the following:

What|Old value |New value

  CC|'rainerbielefeld' |'fst,rainerbielefeld'

  Status|UNCONFIRMED   |RESOLVED

  Resolution|  |INVALID





--- Additional comments from [EMAIL PROTECTED] Thu Jan 10 17:58:12 + 
2008 ---
@fst: What should I comment? Terry is correct, a 2D cell range is a sequence of
sequences.

I wouldn't call this crappy though, treating 2D arrays as an array containing
(pointers to) arrays is a common attempt in many program languages. Bear in mind
that the OOo API is used with different programming languages, and an abstract
2D array doesn't exist in all of them.


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sc-issues] [Issue 76137] cannot access two dimensio nnal array

2008-01-10 Thread er
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76137


User er changed the following:

What|Old value |New value

  Status|RESOLVED  |CLOSED





--- Additional comments from [EMAIL PROTECTED] Thu Jan 10 17:58:36 + 
2008 ---
Closing.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sc-issues] [Issue 76137] cannot access two dimensio nnal array

2007-12-17 Thread terrye
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76137





--- Additional comments from [EMAIL PROTECTED] Mon Dec 17 19:43:21 + 
2007 ---
This isn't a bug.  It's a feature by design.  The getDataArray method 
returns a Sequence of Sequence which the Basic RTL maps onto a VariantArray, 
where each element is itself a Variant Array.  This is *NOT* a 2-D array.  
Whilst this may seem counter intuitive, this is the current design, and not a 
bug.

I know that Noel Power was looking to support the VBA syntax for such 
constructs: 
 print v(r_idx)(c_idx)

The workaround specified isn't a workaround.  It's the documented (and 
somewhat crappy) metho of accessing such contructs.  Note that since Variant 
Arrays are passed by reference and not value the assignment tmp =  temp(c_idx)
is infact a reference and so 
temp(c_idx) = 999  
in fact updates v(r_idx)(c_idx)

So this is not a defect.  Sorry


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sc-issues] [Issue 76137] cannot access two dimensio nnal array

2007-12-17 Thread terrye
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76137





--- Additional comments from [EMAIL PROTECTED] Mon Dec 17 19:44:16 + 
2007 ---
This isn't a bug.  It's a feature by design.  The getDataArray method 
returns a Sequence of Sequence which the Basic RTL maps onto a VariantArray, 
where each element is itself a Variant Array.  This is *NOT* a 2-D array.  
Whilst this may seem counter intuitive, this is the current design, and not a 
bug.

I know that Noel Power was looking to support the VBA syntax for such 
constructs: 
 print v(r_idx)(c_idx)

The workaround specified isn't a workaround.  It's the documented (and 
somewhat crappy) metho of accessing such contructs.  Note that since Variant 
Arrays are passed by reference and not value the assignment tmp =  temp(c_idx)
is infact a reference and so 
temp(c_idx) = 999  
in fact updates v(r_idx)(c_idx)

So this is not a defect.  Sorry


-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sc-issues] [Issue 76137] cannot access two dimensio nnal array

2007-07-01 Thread rainerbielefeld
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76137


User rainerbielefeld changed the following:

What|Old value |New value

  CC|''|'rainerbielefeld'

Keywords|  |needmoreinfo, oooqa





--- Additional comments from [EMAIL PROTECTED] Sun Jul  1 07:04:05 + 
2007 ---
I checked with 2.2.1  Multilingual German version WIN XP: [680m18(Build9161)]
 and can confirm that the macro stops at print v(r_idx,c_idx) with error
message Object variable not set (not index out of bounds)

@prahal: 
Pls. attach a complete sample document with the macto in it.
Unfortunately my Basic knowledge is very poor, so can you please contribute a
more detailed description what you believe what might cause that problem?
cannot access is too general. You should argue with manual references and test
prints of variables in your macro why that _should_ work.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sc-issues] [Issue 76137] cannot access two dimensio nnal array

2007-04-05 Thread prahal
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76137
 Issue #|76137
 Summary|cannot access two dimensionnal array
   Component|Spreadsheet
 Version|OOo 2.2
Platform|All
 URL|
  OS/Version|All
  Status|UNCONFIRMED
   Status whiteboard|
Keywords|
  Resolution|
  Issue type|DEFECT
Priority|P3
Subcomponent|programming
 Assigned to|spreadsheet
 Reported by|prahal





--- Additional comments from [EMAIL PROTECTED] Thu Apr  5 18:10:03 + 
2007 ---
I use range getDataArray. I correctly get a two dimensionnal array though I
cannot   read it :
oDoc = ThisComponent
oSheet = oDoc.Sheets.getByName(Sheet1)
oRange = oSheet.getCellRangeByName(A1:B3)
v = oRange.getDataArray()

For r_idx = LBound(v) To UBound(v)
  For c_idx = LBound(v(r_idx)) To UBound(v(r_idx))
print v(r_idx,c_idx)
  Next c_idx
Next r_idx

fails with index out of bounds for v(r_idx,c_idx)

Please fix this for the next release ... this is quite a showstopper for working
with ranges.

Regards
Alban Browaeys

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[sc-issues] [Issue 76137] cannot access two dimensio nnal array

2007-04-05 Thread prahal
To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=76137





--- Additional comments from [EMAIL PROTECTED] Thu Apr  5 23:33:00 + 
2007 ---
a workaround to get the data which works under 2.2:
For r_idx = LBound(v) To UBound(v)
temp = v(r_idx)
'print temp(0)
For c_idx = LBound(temp) To UBound(temp)
tmp =  temp(c_idx)
print tmp
Next c_idx
Next r_idx

NB: I checked and the bug I reported is partially not present under 2.0.4.
v(i,j) are accepted though they in fact return v(i).
Maybe the current behaviour is more sane by not reporting buggy data even if not
working for mutlidimensional arrays.

-
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]