Announcement

**Isomorphic** · 26 Aug 2015, 13:44

You say "all my events are loaded from the server" - do you mean they are always loaded all at once, and never incrementally (as a ResultSet does)?

If you never use load on demand, this suggests that you call some kind of Timeline API that requires the widget to look at the set of events, but you do this before any of the events have loaded. Or similarly, you do so right after clearing cache while events are still being re-loaded from the server.

**mathias** · 27 Aug 2015, 05:49

I just meant that i don't create any data in the client code.

I have defined a datasource that fetches all data with start-end dates from a springcomponent i have defined in my .ds-file. It gets called correctly from the server with startrow and endrow, i do calcs and set the totalrows in the response, as i do with all other datasources that work fine.

This is my Timeitem class constructor that causes the explosion in the logs, when it is displayed and fetches data from the server, since autofetchdata is set.

EDIT: as you can see, i load and set the lanes in the constructor, which i guess would mean that it happens in parallell to the autofetchdata call. Surely that should not be an issue?

Code:

public GenericTimeline(DataSource dataSource, DataSource laneDS, final String laneNameField) {
        super();
        this.laneNameField = laneNameField;
        this.laneDS = laneDS;
        setDataSource(dataSource);
        setAutoFetchData(true);
        setWidth100();
        setHeight100();
        loadLanes();//sets the rows
        
        setCanEditEvents(canEditEvents);
        Date begin = new Date();
        Date end = new Date();
        CalendarUtil.addMonthsToDate(end, 1);
        setStartDate(begin);
        setEndDate(end);
        setCanEditLane(false);
        setShowEventDescriptions(true);
        setLaneNameField(ClientServerConstants.FIELD_REPORTERID);//this is what must match the "id" values for the lane data

        setStartDateField("inTime");
        setEndDateField("outTime");
        setNameField(ClientServerConstants.FIELD_LOCATIONNAME);
        setShowEventDescriptions(true);
        setDescriptionField("note");


        setMinLaneWidth(130);
        setTimeFormatter(TimeDisplayFormat.TOSHORTPADDED24HOURTIME);

        setHeaderLevels(createHeaderLevels());
        setLaneFields(new ListGridField[]{new ListGridField("title", CommonConstants.constants.reportUser(), CommonConstants.FIELD_WIDTH_REPORTERNAME)});
        setLaneEventPadding(2);
        setEventStyleName("nubaEventWindow");
        setDataSource(ds);

    }
    
    
    public void loadLanes(){
        Criteria crit = new Criteria();
        crit.setAttribute("enabled", true);
        laneDS.fetchData(crit, new DSCallback() {
            @Override
            public void execute(DSResponse dsResponse, Object o, DSRequest dsRequest) {
                Record[] data = dsResponse.getData();
                Lane[] lanes = new Lane[dsResponse.getData().length];
                for (int i = 0; i < data.length; i++) {
                    lanes[i] = new Lane(data[i].getAttribute("id"), data[i].getAttribute(laneNameField));
                }
                setLanes(lanes);              
            }
        });
    }

**Isomorphic** · 17 Dec 2015, 10:22

Our apologies - we neglected to update this thread.

Many changes have been made since your post that should address these logs you were seeing (which were related to CalendarView.refreshEvents() running before data had actually arrived at the client) - please retest with the most recent build from smartclient.com/builds - if you still see these logs, please provide a minimal, runnable test-case that we can run on our end to see the issue, and we'll take another look.

**mathias** · 19 Dec 2015, 04:52

No worries, it's only been 4 months... i had given up on this, so not sure about current status. Will look when i have time.

**Isomorphic** · 19 Dec 2015, 05:16

Yes, it's been a while, and it's also been fixed for a while - as we noted, we neglected to update the thread.

If you need responses with fixed ETAs, consider purchasing support.

Announcement

Strange errorlog in TimeLine when loading data

Comment

Comment

Comment

Comment

Comment