#PB_Event_LeftClick : a left mouse button click has occurred on the window This can be useful to display a popup menu #PB_Event_GadgetDrop : a Drag & Drop operation was finished on a gadget #PB_Event_RightClick : a right mouse button click has occurred on the window. #PB_Event_WindowDrop : a Drag & Drop operation was finished on a window #PB_Event_DeactivateWindow: the window has been deactivated (lost the focus) #PB_Event_ActivateWindow : the window has been activated (got the focus) #PB_Event_RestoreWindow : the window has been restored to normal size (either from a minimum or maximum size) #PB_Event_MaximizeWindow : the window has been maximized #PB_Event_MinimizeWindow : the window has been minimized #PB_Event_MoveWindow : the window has been moved #PB_Event_SizeWindow : the window has been resized #PB_Event_Repaint : the window content has been destroyed and must be repainted (useful for 2D graphics operations) #PB_Event_CloseWindow : the window close gadget has been pushed #PB_Event_Timer : a timer has reached its timeout #PB_Event_SysTray : an icon in the systray zone was clicked #PB_Event_Gadget : a gadget has been pushed #PB_Event_Menu : a menu has been selected To get the window number in which the event occurred, use the EventWindow() function. In this case, either Delay() shouldīe used somewhere in the loop or WaitWindowEvent() with a small timeout value. WaitWindowEvent(), it will not give CPU time to other programs while waitingįor an event and therefore consume all CPU power. It must be handled with care though if used on a continuing basis, because unlike This makes it useful for window event loops, where other processing needs to be done without waitingįor an event to happen (e.g. Unlike WaitWindowEvent() it doesn't wait for the next event - it always returns immediately.Įvent() can be used to get back this value. The next event from the event queue or zero if there are no more events. But why would it and why after running precisely four different tabs and how does it remember which was the fourth tab?Ĭan anyone try to reproduce the problem? Just past the code I pasted above in four different tabs and then run them one after the other.Checks if an event has occurred on any of the opened windows. If the window was at 1920x1080 and upscaled to the 3840x2160 then that might look like what I'm getting. That is higher than the 1920x1080 that windows recommends but has never caused a problem before. I have a 2080 super card and a 65 inch tv as a monitor. Or maybe it is a problem with the specific hardware on my computer. I thought it might be a bug in the debugger but I turned it off and no difference. I thought it might be a compiler bug that generated code that left windows in a strange state. But the need to run four programs to get the problem suggests that that is not the problem. I have had problems with white space characters and corrupted characters causing compiler issues. And I could get a bad program into the clipboard and past it to another tab and still be bad. I was writing an application that used threads and the thread safe compiler option was sometimes checked and later unchecked.Īs far as I can tell the compiler options are the same in all of the tabs. I had some weird behavior with the editor recently where depending on which tab was focused I got different compiler options. Now the original works fine but I have a copy on my windows clipboard that if I post it to another tab will run with the incorrect resolution. I'm not sure how that will help since I cannot recreate the problem even with copy and pasted code. Until Event = #PB_Event_CloseWindow Or Quit = #True Life(invrt(flag), x, y) = life(flag, x, y) If StartDrawing(ImageOutput(#IMAGE_MAIN))ĭrawImage(ImageID(#IMAGE_MAIN), 15*x, 15*y) OpenWindowedScreen(WindowID(#WINDOW_MAIN), 0, 0, ScrW, ScrH, 0, 0, 0) OpenWindow(#WINDOW_MAIN, 0, 0, ScrW, ScrH, "Windowed Screen", #FLAGS) #FLAGS = #PB_Window_SystemMenu | #PB_Window_ScreenCentered
0 Comments
Leave a Reply. |