8000 Calendar doesn't seem to work on Win10 · Issue #6 · White-Tiger/T-Clock · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Calendar doesn't seem to work on Win10 #6

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.

Sign up for GitHub

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

Jump to bottom
Closed
Baegus opened this issue Jul 31, 2015 · 15 comments
Closed

Calendar doesn't seem to work on Win10 #6

Baegus opened this issue Jul 31, 2015 · 15 comments

Comments

@Baegus
Copy link
Baegus commented Jul 31, 2015

Clicking the clock doesn't do anything on Windows 10.
@Baegus Baegus changed the title Calendar doesn't seem to work in Calendar doesn't seem to work on Win10 Jul 31, 2015
@White-Tiger
Copy link
Owner

I didn't fully check Win10 yet, but thanks for your support so far ;)
Will to a full check (and fixes when possible) shortly before next release.. (which to be honest, is due by 2-3 months already :/ And will take at least 2-4 days when I start to fully work on it)

@qwerty12
Copy link
qwerty12 commented Aug 2, 2015

It works if you call PostMessage to bring up the calendar instead of using SendMessage but I don't know if doing so breaks anything for past Windows versions and I just applied the Registry tweak to bring back the old, non-XAML based clock anyway...

@White-Tiger
Copy link
Owner

the reason why I've been using SendMessage is simply that I want to wait for the message to be received. Not sure if it's really needed, but it should be better. Not sure why PostMessage could make a difference here.

But what XAML based clock?

@qwerty12
Copy link
qwerty12 commented Aug 3, 2015

Honestly, I am not sure as to why it works, but I can confirm that it works for me in both a VMware install of 10 and my actual install. I guess a W10 user who has a copy of Visual Studio handy and can literally replace SendMessage with PostMessage can verify this.

But what XAML based clock?

In Windows 10, the Windows 7/8 clock and calendar applet has been replaced with a new one (in case of hotlink protection: here) and for this clock, T-Clock calling SendMessage would not display it at all. I used the Registry tweak on that page to bring back the old clock, and I'm presuming SendMessage does start working once again - I know that my build that still calls PostMessage has no problems showing the old clock.

@White-Tiger
Copy link
Owner

Good to know about that... I knew about that new calendar, but didn't knew that it can be changed.
So I'll add not only a way to open the new calendar, but also an option to re-enable the old one.

@verbatim
Copy link
verbatim commented Aug 4, 2015

White-Tiger - Thanks for the update. I also get the same error that the calendar cannot run

screen_cap_win10

XPCalendar.exe - Application Error
The application was unable to start corectly (0xc000007b). Click OK to close the application.

@bilago
Copy link
bilago commented Sep 11, 2015

Any update on this? Calendar still not working on Win10

I can verify changing the code in ToggleCalender() to

    PostMessage(g_hwndClock,WM_USER+102,1,0);//1=open, 0=close

does not work, the issue is something else.

@White-Tiger
Copy link
Owner

so... you can compile yourself?
I have a fix for it locally, not yet pushed to github, but could do so if you need it.
It currently only supports English versions of Windows though (the multi-monitor support)

PostMessage() should have worked.. but I'm using SendMessageCallback()

@bilago
Copy link
bilago commented Sep 13, 2015

Yes, I compiled it using Visual Studio 2013, clicking the calendar did not work with the change I mentioned above.

@White-Tiger
Copy link
Owner

I actually didn't want to close this (and other issues) until the final version is out.. but what ever xD
Anyway, can you try it @bilago and report back?

The version should be already more stable than my previous ones.. though it's not finalized and thus the settings converter runs at every start^^ (though, shouldn't be a problem unless you try to use the 12h and 24h format together..)

That much said, I try to publish a pre-release this weekend if I'm still not ready for the release (but 8000 it should be close)

@bilago
Copy link
bilago commented Sep 14, 2015

I'm not seeing a CI build available for download on https://travis-ci.org/White-Tiger/T-Clock or AppVeyor, should I just download your repo again and build myself?

@bilago
Copy link
bilago commented Sep 14, 2015

Unfortunately this latest build has 8 compilation errors when trying to build this version. What software are you using to compile this project?

@White-Tiger
Copy link
Owner

eh... yeah you would have to build it yourself..
Travis CI and AppVeyor are only supposed to build the final release (any commit I tag as such)

I didn't want them to waste storage :P (or Github in that matter)
Do you consider it useful to have "live" builds there?

Anyway, I've fixed those build "errors" now..
I'm currently using GCC to do my local builds.
Reason why I've started to develop T-Clock with GCC was mainly to make sure it's properly working there... it originally didn't and still crashed after I got it to compile... So I wanted to fully test if everything is working now and there aren't any more errors. (as sad as it is.. using both GCC and MSVC reveals more bugs than using just one..)
But back when I started to work with C/C++, I did use MSVC.. just couldn't really use it for long as I also tried to write cross-platform code which almost made me rewrite my source simply because MSVC didn't follow standards... So GCC was way easier to use for such purpose. I also had the feeling that just having Visual Studio installed messed up my system.

@bilago
Copy link
bilago commented Sep 14, 2015

Latest version compiles successfully on MSVC 2013, and the calendar now opens properly! Thanks :)

@White-Tiger
Copy link
Owner

new pre-release which includes this fix.

Though it isn't yet including the multilingual changes required to fully support the new calendar.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@qwerty12 @verbatim @White-Tiger @Baegus @bilago
0