With luck this will be the last 2.0 dev release… There are actually two versions of 2.0 now. The version that’s submitted to the Mac App Store (already submitted, waiting for review) and this version which will be sold through www.paddle.com.
Few things to note/try:
- This version isn’t sandboxed and uses a different app identifier then the App Store version. So different preferences, etc.
- This version should work on 10.7 since it’s not sandboxed. I think. Please test and let me know!
- This version is sold through paddle, but if you already own and run the App Store version once then you shouldn’t be asked to buy again.
- You can’t actually buy this version from Paddle yet (will get Product Not Found), I’ll make it available once the App Store version is approved.
Download FoldingText Dev
Jesse love your app/s and I hope you don’t mind me throwing in my comments on your new forum for FoldingText 2!
Full screen single does not hide second display (hides menu bar tho) and I could not figure out how to exit with knowing the keyboard shortcut ? Is this expected behaviour?
The markdown characters such as # > are counted as part of the standard word count plugin ? Is this expected
[quote=“adamprocter, post:2, topic:18, full:true”]
Jesse love your app/s and I hope you don’t mind me throwing in my comments on your new forum for FoldingText 2![/quote]
Thanks, and of course not. Post! Post! Thanks for making the first post!
Full screen single does not hide second display (hides menu bar tho) and I could not figure out how to exit with knowing the keyboard shortcut ? Is this expected behaviour?
I should probably just get ride of “Full Screen Single” at this point. The reason for it originally was because OS X default fullscreen covered all screens. But (least for me) when writing that’s usually not what you want. So fullscreen single just covers single screen.
But… looks like in Mavericks (maybe it happened earlier, but I just noticed recently) the default fullscreen also now only covers one screen too. The hidden menu bar… it is supposed to hide, but then autoshow when you move your mouse cursor to the top of the screen. Unfortunately it looks like that doesn’t always work. I just tried and for me it works fine on my main monitor, but not on secondary monitor.
The markdown characters such as # > are counted as part of the standard word count plugin ? Is this expected
This is “expected” right now, but I agree it should be improved.
Thanks, Mavericks did indeed stop the crazy textured second screen and other stuff which basically fixed fullscreen as it should have been from the start, so I say either remove Single mode or enhance it by blanking out the other monitor.
Glad you’ve got the release out.
As far as 10.7 goes, it “works”—it downloads and runs on 10.7.5 but there’s still the problem of not displaying any of the text besides the file’s title. So it runs but is effectively unusable.
Any plans to fix that?
When that happens do you see any errors logged in the console.app?
I’ve never used Console.app before, so I’m not sure how to distinguish what’s an error from just a logged action.
That said, it lists 12 actions that have to do with various objects of different classes being autoreleased, then 1 entry that says “FoldingText: Can’t open input server /Users/[my user name]/Library/InputManagers/Edit in WriteRoom”
If that’s not helpful enough, I can send/post screengrabs for you of the whole window. Just let me know.
Thanks for looking at this—I’m definitely looking forward to using the newest version of the app!
For a start can you just copy/paste the text output from the console app into this forum?
Apologies for the delay in getting this to you Jesse - v. busy weekend with very little inter-webbing shenanigans…
Here’s the FT related stuff from Console.app on 10.7.5:
01/06/2014 08:22:58.121 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80420fa0 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.121 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421220 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.121 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421400 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.121 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421490 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.121 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce8041bcc0 of class __NSArrayM autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.121 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421560 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.128 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421c60 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.128 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421b10 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.128 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421c90 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.128 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421d50 of class __NSArrayI autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.128 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80422150 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
01/06/2014 08:22:58.128 [0x0-0x46046].com.foldingtext.paddle.FoldingText objc[509]: Object 0x7fce80421f60 of class NSURL autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
I’m adding the log on mine as well, since I don’t see the thing about the input server in the previous log.
Thanks for looking at this!
2014-06-01 1:29:00.998 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0420fa0 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.998 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421240 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.998 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421420 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.998 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421530 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.998 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f041bd30 of class __NSArrayM autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.998 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f04216a0 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.999 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421c50 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.999 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421d00 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.999 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421fc0 of class NSPathStore2 autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.999 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421c30 of class __NSArrayI autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.999 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421f80 of class __NSCFString autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:00.999 PM [0x0-0x1c69c68].com.foldingtext.paddle.FoldingText: objc[39943]: Object 0x7f85f0421db0 of class NSURL autoreleased with no pool in place - just leaking - break on objc_autoreleaseNoPool() to debug
2014-06-01 1:29:01.225 PM FoldingText: Can't open input server /Users/[my user name]/Library/InputManagers/Edit in WriteRoom
@jonmoore @foureyedsoul I’m sorry but I’m reversing course on 10.7 support.
I thought it was just sandboxing which I could switch and have it fixed, or maybe a few API calls that I could conditionally exclude. But this seems to be something else that I need to debug manually. And I just spend much to long trying to get a virtual machine with 10.7 up and running and still don’t have that working yet. Even if I did get it working and debugged I see 10.7 as a potential bug/time sink for minimal benefits that will diminish over time.
For 10.7 work my recommendation is to use FoldingText 1.2. Sorry for the change of course.
Unfortunate, but I understand completely. Thanks for being clear about your choice & reasons why.
I’ll add this to my growing list of reasons I’m looking forward to being able to update my machine. 
I understand that you have bigger fish to fry here and that you perceive the install base of Lion is low.
However and this isn’t your fault Jesse, I’m getting very weary of a world where an operating system that was released in June 2011 is considered ‘over the hill’. The constant need of Apple to drive new hardware sales by making making it increasingly difficult for developers to support software on OS flavours that are 3 - 5 years old is a worrying trend.
I’m as excited as the next man about IOS 8 and Yosemite (and even more so about the interoperability features between the two) but not everybody has the luxury of being able to update their hardware every 2-3 years. I have an Apple ‘eco-system’ in my household which involves a lot of hand me downs to other family members. This is driven more by ethics than economics and it sours my relationship with Apple that they’re driving towards a 2-3 year obsolescence cycle for their software/hardware products.
I’m not quite at the stage of dropping Apple and becoming a bearded, Birkenstock wearing Linux customer - my despicable inherent need for shiny new things will see that that never happens. But it most definitely makes me sad when a 3 year old OS is no longer supported by developers of products I use on a regular basis.