korman

Commit Graph

Author	SHA1	Message	Date
Adam Johnson	e5eba455f3	Simplify log indentation management. Previously, the indentation level was hardcoded everywhere. This was tedious before in that changing the log structure would require changing many manual indentation values. Now that objects can be trivially generated at export time, the export code might be much more nested that before. So, it's better to let indentation be more implicit. This, therefore, adds a context manager to increase the indentation using `with` blocks. Manual indentation specification remains for compatibility with Python 2.2 where required.	1 year ago
Adam Johnson	c3157fc256	Close #159 .	5 years ago
Adam Johnson	b5d3f87c66	Fix #137 Unfortunately, this does not prevent "DAG zero..." from appearing period. Rather, it just overwrites any junk printed to the console during the export. The ANSI version is rather limited compared to the Windows version and completely untested...	5 years ago
Adam Johnson	51b5a44bf5	Improve whitespace generation in progress monitor	6 years ago
Adam Johnson	b2120aba10	Add new "nonfatal error" handling for exporter There are some cases where errors, while bad, are not the end of the world. I'm thinking namely about compyling the age python. The age still exports just fine, but the ancillary data is flawed. This new system collects nonfatal errors until the export is done, then raises them all at once.	6 years ago
Adam Johnson	8c0396839b	Fix issue with verbose logger not logging when there is no backing file	6 years ago
Adam Johnson	b7ac558035	Fix verbose logging crash It appears that when the progress logger was broken up into separate classes, the progress_end function was not properly split and some threading functionality remained in the base class.	7 years ago
Adam Johnson	80ce28ddc8	Show the console during exports The only major issue with the console based progress solution is that the user would have to remember to press "Toggle System Console" before the export. This button corresponds to the operator `bpy.ops.wm.console_toggle`. Unfortunately, Blender does not expose a way for us to query the console state. So, we have to get nasty and use ctypes to ask the OS if the console window is active. The user may already have it open and hidden behind Blender's UI, after all. This changeset causes the console to open during the export (unless disabled in the export operator). If the console was closed before the export, it closes again once the export is finished, unless there is an error. If the console was open, it remains open. Unfortunately, this only works on Windows. But, according to the source code of `bpy.ops.wm.console_toggle`, Blender's `ghost_toggleConsole` only functions on the Win32 subsystem... SDL, X11, and Cocoa are all no-ops. Future work would include a patch submitted to Blender adding an enum property to the console operator to avoid this code duplication.	7 years ago
Adam Johnson	5c8a9253fe	Sirius said he liked watching the PyPRP log... ... So now he can watch the Korman log in real time	7 years ago
Adam Johnson	d465b86f9c	Handle errors better in the progress manager Now the progress display will recognize errors using the `__exit__` magic method and print out an error header with the actual error message. This is useful because when the mouse leaves the Blender operator's report error, the error "window" is destroyed. This led to potential silent failures.	7 years ago
Adam Johnson	4842731a44	Better long-running progress report behavior For sanity, I stripped the progress manager into a subclass. From there, I moved all of the progress printing into a thread so that we can accept signals for step progress. If there is no step progress for a time, we show the user a rolling set of ellipses to prove we're not dead (yet).	7 years ago
Adam Johnson	98d5480024	Implement rudimentary progress reporter A common complaint that I have heard (and have nyself) is that there is little indication of what Korman is doing in the background. In PyPRP, the raw export log was dumped to the console, and many liked to watch it travel by as an indicator of progress. As such, I have implemented a rudimentary progress monitor that outputs to the console into the export logger. Unfortunately, there is no "easy" way to show progress in the Blender UI currently. Korman makes the assumption that nothing will touch Blender's context while it is executing. Attempts to mvoe the exporter into a background thread have all resulted in spectacular failures. So, this will have to do for now.	7 years ago
Adam Johnson	6a3b09b747	Refactor export logging The export logger and export reporter have been merged together to form an eventually much more powerful export analysis feature. For now, the benefit is that general log messages don't have to be so fiddly with print statements and string formatting. You're welcome.	7 years ago
Adam Johnson	55566c908a	Convert os.path usage to pathlib. ++code_quality This closes #26	9 years ago
Adam Johnson	290408847c	Ensure alpha textures have transparency	9 years ago
Adam Johnson	f2d4485515	Fix potential issue with export log creation	9 years ago
Adam Johnson	de5125b079	Correctly handle logger flushing	10 years ago
Adam Johnson	106ed1fb7d	Basic opaque meshes exporting... There are no textures, there are no vertex colors, there are no UVWs... Just the mesh. Deal with it.	10 years ago
Adam Johnson	242ed01afb	Move exporter logic out of prop_object... ... And commence more work on the exporter. We now export CoordinateInterfaces! Go us.	10 years ago

19 Commits (8d3387c330cae9bef8561706850398f446fd61f3)