in generally I have problems with the automatic update of Architect. It did not work till build 676.
This is the first time after a while, when it works again :).
But... it disappears from the desktop , when I try to open a project started with build 640.
I still see Architect as an active process under Windows -Task Manager.
It starts when I open a new project, but there are no errors in the log file. It disappears from the desktop, just when I try to open that project over the SA2 menu. I restored the build 640, but the problem ist still there :(. Or it shows just as attached and hungs up and whe I try to close it:

Looking at this now. I've isolated it to be an issue with GLineChart. Let you know when I do.

15 Nov 2012, 11:51 AM

Phil.Strong

Ok so the issue is in the GLineChart which is a Chart with a numeric and a time axis.

The time axis had an invalid step

Code:

"step": "['d',1/24]",

This was crashing the application which it should not so I'll investigate this further.

However if you open that file

metadata/view/GLineChart and find the 2nd child (cn) type: "timeaxis" and remove the line that has "step": "['d',1/24]",

this will work around the issue.

15 Nov 2012, 12:12 PM

Phil.Strong

This appears to be a bug in the framework.

you can use step: ['h', 1] (same as above)

15 Nov 2012, 12:22 PM

Phil.Strong

This is a bug in the documentation as time axis is only handling integers and not floating point.

15 Nov 2012, 11:11 PM

msinn

Thank you for the answer, I changed the metadata file and removed the fraction '1/24' and now I can open the project again, but without rendering the labels for hours anymore...

I'm a little bit confunsed, because it worked with fraction after publishing (without errors in the console showing all the labels for hours). The problem occurs when I attempt to open the project with Architect again.
So If I'm lucky and archived the project, then I'm able to open it from the archive, even if there is the fraction in the step property. So for now I have to archive the project at each saving, otherwise I'll not be able anymore to open that project again, till you'll find the problem.

Does this mean, that Architect will lock up, each time there is a bug in the library, and we are not able to open that project anymore, till you'll take a look into it?
Why don't you provide us with a debugging tool to be a little more independent in such cases?

Quote:

step : ArrayAn array with two components: The first is the unit of the step (day, month, year, etc). The second one is a number. If the number is an integer, it represents the number of units for the step ([Ext.Date.DAY, 2] means "Every other day"). If the number is a fraction, it represents the number of steps per unit ([Ext.Date.DAY, 1/2] means "Twice a day"). If the unit is the month, the steps may be adjusted depending on the month. For instance [Ext.Date.MONTH, 1/3], which means "Three times a month", generates steps on the 1st, the 10th and the 20th of every month regardless of whether a month has 28 days or 31 days. The steps are generated as follows: - [Ext.Date.MONTH, n]: on the current date every 'n' months, maxed to the number of days in the month. - [Ext.Date.MONTH, 1/2]: on the 1st and 15th of every month. - [Ext.Date.MONTH, 1/3]: on the 1st, 10th and 20th of every month. - [Ext.Date.MONTH, 1/4]: on the 1st, 8th, 15th and 22nd of every month.
Defaults to: [Ext.Date.DAY, 1].

I'm a little bit confunsed, because it worked with fraction after publishing (without errors in the console showing all the labels for hours). The problem occurs when I attempt to open the project with Architect again.

New information tells me that this does in fact work with later versions of Ext JS 4. Versions not released yet to the public.

You were not getting "script runs too long" on that page?

Quote:

Does this mean, that Architect will lock up, each time there is a bug in the library, and we are not able to open that project anymore, till you'll take a look into it?
Why don't you provide us with a debugging tool to be a little more independent in such cases?

Only bugs that create an infinite loop. However we are working on a way to isolate even these types of bugs to allow for recovery.

The archive thing is really quirky.

Bottom line is until Ext JS 4.2 is released I'd stick with using "h", 1