#BRICSCAD DOCSTAB 64 BITS CODE#
#BRICSCAD DOCSTAB 64 BITS WINDOWS#

What you added here is a crash report created by the operating system, not created by the Bricscad application. No other apps running other than Thunderbird. This was known good memory taken from another computer. We changed put the memory this morning, going from 2GB to 4GB. The crash report isĪdditional information about the problem: We find that we have to zoom many, many times a day because the scrollbars do not work well (the arrow keys on the scrollbars work, but dragging the bar is at best unpredictable). The program continued to run for a few seconds, during which time it appeared to respond to the mouse, then we had a blue screen. We saw multiple copies of the screen image at different zoom factors. The crash happened during a zoom command. There were four drawings open at the time. We just had another crash and hopefully have better data. The good news is that we have not had a blue screen with Bricscad 10.4.11. We will try to make notes when we see shutdowns and will send files when appropriate. In some cases the crosshairs (set at 100%) freeze in position but the aperture continues to be movable, with the program disappearing several seconds later.

In some cases we see multiple images on the screen at multiple zoom levels, after which the program hangs for several seconds then disappears. Some (maybe most) shutdowns seem to occur during zooming. Some shutdowns come without warning - one moment Bricscad is running and the next moment it has disappeared. He also reports that there are three failure modes. The designer said he had 12 tabs open at the time of the crash. I did remove the block of my engineer's seal but otherwise the file is unchanged. I have sent a copy of a file made immediately after a crash today.

#BRICSCAD DOCSTAB 64 BITS WINDOWS#

If ((GetAsyncKeyState(VK_ESCAPE) & 0x01) & bRunning)Įxample from Windows Classic Samples on GitHub.We continued to work on the files yesterday after the crashes so I doubt that there would be much of value. If (!TranslateAccelerator(msg.hwnd, hAccelTable, &msg)) Example while (GetMessage(&msg, nullptr, 0, 0)) These left- and right-distinguishing constants are only available when you call the GetKeyboardState, SetKeyboardState, GetAsyncKeyState, GetKeyState, and MapVirtualKey functions. VKey to distinguish between the left and right instances of those keys.

#BRICSCAD DOCSTAB 64 BITS CODE#

You can use the following virtual-key code constants as values for This gives the state of the SHIFT, CTRL, or ALT keys without distinguishing between left and right. You can use the virtual-key code constants VK_SHIFT, VK_CONTROL, and VK_MENU as values for the The behavior of the least significant bit of the return value is retained strictly for compatibility with 16-bit Windows applications (which are non-preemptive) and should not be relied upon. Which returns TRUE if the mouse buttons have been swapped.Īlthough the least significant bit of the return value indicates whether the key has been pressed since the last query, due to the preemptive multitasking nature of Windows, another application can call GetAsyncKeyState and receive the 'recently pressed' bit instead of your application. You can determine the system's current mapping of physical mouse buttons to logical mouse buttons by calling GetSystemMetrics(SM_SWAPBUTTON). For example, the call GetAsyncKeyState(VK_LBUTTON) always returns the state of the left physical mouse button, regardless of whether it is mapped to the left or right logical mouse button. However, it checks on the state of the physical mouse buttons, not on the logical mouse buttons that the physical buttons are mapped to. The GetAsyncKeyState function works with mouse buttons.

The foreground thread belongs to another process and the desktop does not allow the hook or the journal record.

The current desktop is not the active desktop.

The return value is zero for the following cases: However, you should not rely on this last behavior for more information, see the Remarks. If the most significant bit is set, the key is down, and if the least significant bit is set, the key was pressed after the previous call to GetAsyncKeyState. If the function succeeds, the return value specifies whether the key was pressed since the last call to GetAsyncKeyState, and whether the key is currently up or down.

See the Remarks section for further information. You can use left- and right-distinguishing constants to specify certain keys.

For more information, see Virtual Key Codes. Determines whether a key is up or down at the time the function is called, and whether the key was pressed after a previous call to GetAsyncKeyState.

Bricscad docstab 64 bits