Skip to content

GitLab

    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    • Menu
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • Lazarus Lazarus
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,080
    • Issues 2,080
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 7
    • Merge requests 7
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • FPC
  • Lazarus
  • LazarusLazarus
  • Issues
  • #29646
Closed
Open
Created Feb 13, 2016 by FPC Admin account@fpc_adminOwner

TCalendar.HitTest method incorectly returns cpDate

Original Reporter info from Mantis: zoran
  • Reporter name: Zoran Vučenović

Description:

In recent Windows versions (probably since Windows 7), the native windows MontCalendar widget has new look. When the user clicks on month name in title (for example February 2016), then the calendar changes to grid of months (see attached file Capture.PNG). Then, when user clicks on a month, the Calendar.HitTest (http://lazarus-ccr.sourceforge.net/docs/lcl/calendar/tcustomcalendar.hittest.html) returns cpDate. I think that it should return cpTitleMonth.

Additional information:

This affects the incorrect behaviour of TDateTimePicker, TDateEdit and TCalendarDialog. All those controls ask Calendar.HitTest(aPoint) in [cpDate, cpNoWhere] and, when they get cpDate, they incorrectly close the calendar when the user hasn't chosen the date.

This is reported as TDateTimePicker bug (see issue 29617), but it should be solved in TCalendar for Win32/64 widgetset, so I'm creating this bug report.

Mantis conversion info:

  • Mantis ID: 29646
  • OS: Windows
  • OS Build: 8
  • Build: 51618
  • Version: 1.7 (SVN)
  • Fixed in version: 1.8
  • Fixed in revision: r51694 (#d0a37e16), r51695 (#3d710556), r51696 (#d03d42c5)
  • Target version: 1.8
Assignee
Assign to
Time tracking