The Origin Forum
File Exchange
Try Origin for Free
The Origin Forum
Home | Profile | Register | Active Topics | Members | Search | FAQ | Send File to Tech support
Username:
 Password:
Save Password
Forgot your Password? | Admin Options

 All Forums
 Origin Forum for Programming
 LabTalk Forum
 Grey workbook cells		  New Topic  Reply to Topic
 Printer Friendly
Author Previous Topic Topic Next Topic Lock Topic Edit Topic Delete Topic New Topic Reply to Topic

ds755

57 Posts
Posted - 12/30/2019 :  7:47:28 PM  Show Profile  Edit Topic  Reply with Quote  View user's IP address  Delete Topic
Origin Ver. and Service Release (Select Help-->About Origin): Origin 2019
Operating System: Windows 8.1

Hello,

I have noticed that some workbook cells are grey, and the assignment commands in LabTalk behave strangely.

In the image below, the grey cell cannot be edited with "col(J)[1]=30;", but "cell(1,10)=30;" works.

Could you please help me understand why this happens?

Thank you
Edited by - ds755 on 12/30/2019 7:48:40 PM

yuki_wu

896 Posts
Posted - 12/30/2019 :  10:21:31 PM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi,
You might set the second row of Column J as begin by accident, so you can select the grey cell( or the whole first row) then right click to select Set as Begin. You are allowed to set the cell value via “col(J)[1]=30;” now.

You mentioned "col(J)[1]=30;" and "cell(1,10)=30;" results in inconsistent results. I think this is a bug and I have reported it to our developer (ID: ORG-21311).

Regards, Yuki
OriginLab
Go to Top of Page

ds755

57 Posts
Posted - 12/31/2019 :  10:16:10 AM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi Yuki,

I am reading the webpage below and beginning to understand.

https://www.additive-net.de/en/software/support/minitab-support/minitab-faq-graphiken/584-software/originlab/origin/v2019/6151-origin-2019-improved-handling-of-empty-cells

The "Set As Begin" works and the values appear normally. So, why are these cells registered as "unused cells" by my script, as opposed to "missing value cells"? This is something I need to figure out. And why does the col(J)[1] command fail when used on unused cells?

I uploaded the bug in a project file, so that the company can study it.

https://www.dropbox.com/s/e5htezql3g1tx3d/bug.opju?dl=0
Edited by - ds755 on 12/31/2019 10:39:23 AM
Go to Top of Page

Chris D

428 Posts
Posted - 01/02/2020 :  08:26:23 AM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
Hi,

I have your OPJU. Can you provide a series of col()[] examples and what you expect to be the output?



Thanks,
Chris Drozdowski
Originlab Technical Support
Go to Top of Page

adamgreengr

United Kingdom
1 Posts
Posted - 01/05/2020 :  08:00:59 AM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
I also need series of col()[] examples and what you expect to be the output?


<a href="https://www.packntrade.co.uk/">CakeBox</a>
Go to Top of Page

ds755

57 Posts
Posted - 01/07/2020 :  5:16:45 PM  Show Profile  Edit Reply  Reply with Quote  View user's IP address  Delete Reply
quote:
Originally posted by Chris D

Hi,

I have your OPJU. Can you provide a series of col()[] examples and what you expect to be the output?



Thanks,
Chris Drozdowski
Originlab Technical Support




Hi Chris,

For example you can type: col(J)[1]=30; in the command line and see what happens. If you do "Set As Begin", as Yuki mentioned, the values assigned by my script will appear on the unused cells. Of course, the question is why is my script unable to assign values to unused cells.
Go to Top of Page
  Previous Topic Topic Next Topic Lock Topic Edit Topic Delete Topic New Topic Reply to Topic
 New Topic  Reply to Topic
 Printer Friendly
Jump To:
The Origin Forum © 2020 Originlab Corporation Go To Top Of Page
Snitz Forums 2000