Page 1 of 1

5.3.1 Dropping events past noon gives unexpected results

Posted: Fri Mar 17, 2023 11:54 pm
by jk@datapult.dk

Hi,

On 5.3.1, I am experiencing this issue where dropping an event will jump to the previous day if the event starts after noon. Look at this video where events starting prior to noon ends on the drop target but events starting after noon jumps to the previous day: https://www.dropbox.com/s/i0itjahydogvx7j/past-noon-fails.mov?dl=0

REPLICATING THE ISSUE
Download the zip file.

Since we do need a backend to server a few things, it is a multi-step setup.

In the project root:

python3 server.py

In another terminal window, do this to get an interactive session with npm 16:

docker run -it --rm -p 3000:3000 -v $PWD:/home/node/app node:16-buster /bin/bash

Inside the container do:

cd /home/node/app/ && npm install && npm run dev

Once done, you can now open this in your browser: http://localhost:3030/public/index.html


Re: 5.3.1 Dropping events past noon gives unexpected results

Posted: Mon Mar 20, 2023 8:52 am
by alex.l

Thanks for the report, I've opened a ticket to investigate this problem https://github.com/bryntum/support/issues/6403


Re: 5.3.1 Dropping events past noon gives unexpected results

Posted: Fri Mar 31, 2023 3:36 pm
by jk@datapult.dk

Hi all. Sorry. This one is so obvious that my clients are squeezing me after 2 weeks. Could you help?


Re: 5.3.1 Dropping events past noon gives unexpected results

Posted: Fri Mar 31, 2023 4:01 pm
by marcio

Hey,

We'll be looking into that one shortly! I added a note to the ticket. :)


Re: 5.3.1 Dropping events past noon gives unexpected results

Posted: Sun Apr 23, 2023 2:19 pm
by jk@datapult.dk

Hi. Just reviewing your release from yesterday. This did not make it?


Re: 5.3.1 Dropping events past noon gives unexpected results

Posted: Mon Apr 24, 2023 8:38 am
by mats

Unfortunately not but we'll try hard to add it in the upcoming patch release.