-
-
Notifications
You must be signed in to change notification settings - Fork 262
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error when starting designer #340
Comments
I cannot successfully load the file "6th longer maillard.alog" attached in either v1.5.0 nor v1.6.2 of Artisan. Somehow this profile is broken. How did you generate this. Does this shows anything on loading in your Artisan v1.6.2 (or v1.5.0)? |
That's strange, I can open it even on another computer. I generated it by
loading a set of points in designer, moving around a few of the points,
leaving designer and saving.
søn. 24. mar. 2019 kl. 10:27 skrev Marko Luther <[email protected]>:
… I cannot successfully load the file "6th longer maillard.alog" attached in
either v1.5.0 nor v1.6.2 of Artisan. Somehow this profile is broken. How
did you generate this. Does this shows anything on loading in your Artisan
v1.6.2 (or v1.5.0)?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#340 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADeqW5PuqZ0HJwPewWVaWyWq9Rli12zJks5vZ0T0gaJpZM4cFG2b>
.
|
I am totally puzzled with this report. The attached alog file is written with v1.5.0 not v1.6.2 as stated. It refers to a time index that does not exists and thus does not load in either version. Instead it fails with the error message (in the error console)
You should have received this dialog on starting the designer from a profile lacking the CHARGE DROP events I just discovered that on clicking OK in this dialog, the designer still starts up, but in a broken environment (just fixed). This might have led to your situation. Could this be possible? |
Ok, I see. I did get that error message, pressed OK and loaded a new set of
points that included charge and drop. I thought it simply worked as a
warning that the profile I loaded was missing some data, not that it would
corrupt the profile. I then upgraded to 1.6.2.
…On Mon, Mar 25, 2019, 07:09 Marko Luther ***@***.***> wrote:
I am totally puzzled with this report. The attached alog file is written
with v1.5.0 not v1.6.2 as stated. It refers to a time index that does not
exists and thus does not load in either version. Instead it fails with the
error message (in the error console)
1 07:08:59.660 Exception: redraw() list index out of ***@***.*** 5097
You should have received this dialog on starting the designer from a
profile lacking the CHARGE DROP events
[image: Screen Shot 2019-03-25 at 06 56 57]
<https://user-images.githubusercontent.com/13909011/54898441-a466b480-4ecc-11e9-8fce-784b9c3235e9.png>
I just discovered that on clicking OK in this dialog, the designer still
starts up, but in a broken environment (just fixed). This might have led to
your situation. Could this be possible?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#340 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ADeqW4Ivo91e9eKeWWdPdPUYpk9Q_iqeks5vaGg2gaJpZM4cFG2b>
.
|
fixed |
For the last half hour, whenever I start designer I get the following error. It started after I tried to start designer while having open measurements without events.
<class 'IndexError'>:
list index out of range
File "artisanlib\main.py", line 25193, in designerTriggered
File "artisanlib\main.py", line 25196, in startdesigner
File "artisanlib\main.py", line 9127, in designer
File "artisanlib\main.py", line 9229, in initfromprofile
artisanlib\main.py::designerTriggered:25193
self = <artisanlib.main.ApplicationWindow object at 0x000001D7F724B4C8>
artisanlib\main.py::startdesigner:25196
self = <artisanlib.main.ApplicationWindow object at 0x000001D7F724B4C8>
artisanlib\main.py::designer:9127
reply = 16384
self = <artisanlib.main.tgraphcanvas object at 0x000001D7F743E798>
artisanlib\main.py::initfromprofile:9229
i = 0
self = <artisanlib.main.tgraphcanvas object at 0x000001D7F743E798>
Specifications
bug files.zip
The text was updated successfully, but these errors were encountered: