Overview
Examples
Screenshots
Comparisons
Applications
Download
Documentation
Tutorials
Bazaar
Status & Roadmap
FAQ
Authors & License
Forums
Funding Ultimate++
Search on this site
Search in forums












SourceForge.net Logo
Home » Community » U++ community news and announcements » 2023.2
Re: 2023.2 [message #60309 is a reply to message #60308] Wed, 15 November 2023 12:17 Go to previous messageGo to previous message
mirek is currently offline  mirek
Messages: 14265
Registered: November 2005
Ultimate Member
Tom1 wrote on Wed, 15 November 2023 11:14
Hi,

It does not make difference if I use [=] here. However, I would not dare to point to local temporary variables with timer anyway. Instead, my timer sets are mostly of type
timer.Set(THISBACK(UpdateRoutine));
In that case the reference is all about using 'this'.

INTERESTINGLY: The entire timer system freezes when I open the secondary window. Ctrl::TimerProc() does not get called at all until I close that secondary window.

UPDATE: While the secondary window is open, there is not a single WM_TIMER coming into Ctrl::UtilityProc(). The execution of thread is not frozen within TimerProc() though. Windows is just no longer sending WM_TIMER messages in.

Best regards,

Tom


Without seeing the whole logic of your app: Timer only runs when GUI is "idle". Any chance the secondory window is doing something like processing events itself?
 
Read Message
Read Message
Read Message icon14.gif
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: Ide: branch now displayed in editor bar
Next Topic: TheIDE and U++ have been released on Flathub
Goto Forum:
  


Current Time: Sat Jul 05 07:11:17 CEST 2025

Total time taken to generate the page: 0.04053 seconds