Text editor built into Blender.
Tue, Aug 15
Tue, Aug 8
I have been using my own hacks to center the text and create my own text hitboxes.
Jun 6 2017
Jun 5 2017
Yep, known issue with our undo system, that is considered a TODO currently. Thanks for the report anyway.
Jun 4 2017
This seems to be a long standing issue with the Undo and the Text Editor T24543 and also a ToDo in
May 22 2017
This is our infamous undo design limitation biting us again, Text editor has own undo for most of text editing, which does not affect global undo, and is ignored by it, so redoing 'global undo' operator reset states to previous 'global undo' point and wipes out all text editing done in-between.
Confirmed. In fact it happens for any operator in the viewport in object mode. Another way of reproducing this is:
- Write some text
- Do some operation (e.g., Duplicate Object)
Mar 24 2017
I confirm the problem on ubuntu 16.04 64bits
Mar 18 2017
Mar 17 2017
Feb 11 2017
Oct 25 2016
the addon we are talking about is called Macro.
Oct 20 2016
Thanks for the report, but it is not really a bug, but a specific behavior of how keymap matching currently works.
Sep 4 2016
Aug 11 2016
Mar 16 2016
Yep, not real high priority.
Mar 15 2016
Noticed comment toggling is pretty much useless as it is (doesn't work in common cases, unusual shortcuts, missing shortcuts - as reported here, ...). So decided to improve this a bit, starting with rB0f6f1908c586c. Will do further work in temp_textedit_comment_toggling branch (probably not this week though since I'd like to focus on other stuff as long as I'm in the institute).
Meanwhile, we will handle this as ToDo.
@Julian Eisel (Severin), something liek this could work:
Jan 9 2016
Jan 8 2016
Dec 1 2015
Nov 6 2015
Oct 25 2015
- Call txt_merge_sels in delete operator
- rename text->n_sels to text->nsels
- post-increment in for loop
Oct 21 2015
- Update for latest master
- Fix crash when reading in old files containing Texts
- Fix crash when reading in new files created with patched build
- Minor cleanup
Oct 20 2015
Oct 19 2015
- Patch can be applied to latest master again
Oct 1 2015
Sep 28 2015
Sep 27 2015
Yuck! that piece of code is totally ignoring non-ASCII UTF8 encoded chars (which take more than one byte)!
Sep 8 2015
Where would communication take place(In this differential? Somewhere else?)
Should fixes unrelated to this feature(e.g. weird scrollbar behavior) be done in the branch?
Sep 3 2015
- Forgot calling selection unification code in word selection operator
- Cleaned up selection unification code(txt_merge_sels(text))
Sep 2 2015
Regarding the branch, I was suggesting this patch could be finished in a feature-branch. Which is a bit nicer then updating this patch (longer running projects. The merge with master would happen later, once the branch was reviewed and accepted.
Looking at Scintilla, though I think it might be a useful thing, if the text editor is planned to be rewritten it might be a bad idea to do the thing twice. Took a look at the github repo, it seems like Scintilla is implemented in C++ and there is a wrapper to interface with the C code and do the drawing? I'm not sure about this, but making Scintilla work with Blender's DNA/RNA structure and C architecture might be more of hassle than just rewriting the entire thing from scratch. Plus, we might then have less trouble keeping everything in sync with their additions/fixes/improvements or providing more functionality on our own. I don't know. (Then again, Scintilla looks really powerful and we might not even have to do that)
When it comes to maintenance, I don't know if I'm familiar/experienced enough with Blender's codebase.
As it currently stands, the text editor is not really likely to be used by a developer. Working with file and especially directory structures is just a HUGE mess. As long as that problem is not addressed, developers probably won't consider writing their scripts in Blender itself. So functionality like this one might not really be interesting to anyone.
With the branch, does that mean that I should also make other improvements in the branch or should I be adding them after the merge?