-
Notifications
You must be signed in to change notification settings - Fork 176
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
11.5.0 Unable to change event behavior #46
Comments
small update: I found out that the event triggers correctly on every page but not on the year page. Really strange. |
The callback's purpose is to bring up another UI when the user double clicks on an entry, e.g. a dialog or a popover, that allows the user to edit the entry. However, the switching between views is done by different code. When you double click a date in the year page / year view then a so-callled RequestEvent will be fired. This event "requests" the date and the CalendarView makes the DayView show up. If you want to see the events being created you can launch your application with -Dcalendarfx.developer=true. When this property is set you can bring up the "developer console" via SHORTCUT-D (CMD-D on Mac, CTRL-D on Windows). A drawer will show up at the bottom. Ideally you take full control of your UI by putting your calendar together yourself and simply use the YearPage and leave out anything else. |
CalendarView basically represents a full-fledged calendar solution. If you want just a piece of it then you need to put it together yourself. |
Thank you! |
I'm using CalendarFX 11.5.0 and want to restrict the user to only see the YearPage of the example. So I'm doing:
The problem is that when I'm double-clicking a day, it switches the view. To change that behavior as well, I thought I simply have to provide a custom callback for the setEntryDetailsCallback function but this doesn't work.
calendarView.setEntryDetailsCallback(param -> { System.out.println("Test"); return true; });
But I'm not even getting the "Test" printed. Am I missing something?
The text was updated successfully, but these errors were encountered: