Search Results
Search results 1-20 of 64.
This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.
-
I noticed y'all released a new revision. The windowing issues appear to not be resolved, all I did to get this screen was attempt to move the Memory window. After about 30 seconds after this screen capture, the program faulted. [img]blob:https://forum.segger.com/0c47f91f-0171-40da-939f-adda975ffaf8[/img]
-
Quote from danngreen: “I can confirm this is the case on Mac OS Big Sur, at least on Ozone v3.22b. When the dialog box pops up ("The program file has been modified..."), none of the buttons are highlighted. See the first screen shot attached. ” Thanks, I can't remember trying 3.22b recently. I'll give it a shot if I have time today. The font commands, could you pass those along for me? Thank you!
-
Here is another picture that is easier to see. As well, as far as model boxes, it would be awesome to add a 4th option to the second one here, "No, and do not show again" As always, thank you. And stability improvements should always be first I would think. forum.segger.com/index.php/Attachment/4750/ forum.segger.com/index.php/Attachment/4751/
-
With the current round of debugging I like to be able to control if I want to reload or not I do not have the reload be automatic. It would be cool if the focus was given to the yes button so a user can just hit enter for yes, or left arrow; enter for no. Anything to reduce the number of times you need to move my hand to the mouse is appreciated. [img]blob:https://forum.segger.com/f00f55b2-c45d-4b67-becd-cf1ce5c3d1fd[/img] for reference, Big Sur, V3.22d (V3.22e is not usable on Big Sur)
-
Nino, Thank you again. Thomas
-
Nino, Any idea when you expect the next release for your MacOS customers using Ozone? Again, thank you, Thomas
-
Nino, Sorry, to reiterate what I wrote above with a little more detail. Host: 2020 MBP with 16G RAM. Device: STM32F405 Code: > 200kB of FLASH, and 30 or 35 C files. At Ozone startup/locading the elf, it scans, or loading the code profile. That scanning takes a long time, 10+ seconds. During that scanning mouse events don't always get handled correctly. Once the code profile is loaded, all is good. I managed to disable the loading of the code profile when an ELF image is loaded, and Ozone behaves…
-
Nino, Further, got rid of the code profile window [first disabled some of the code profile options] and the very long ELF load time, which appears to have gone away. Are there any plans to make that more effecient, or keep in completely in the background with the Code Profile window gr[a|e]y while loading? many thanks, thomas
-
Second, when do you expect a subsequent reals from 3.22e? many thanks, Thomas