No that does not help
And a new files saved via TP does not open via Finder
== feek
No that does not help
And a new files saved via TP does not open via Finder
== feek
Thatās not so nice, so it would be nice when you could implement a custom style folder (via preferences) so one can e.g. sync the files.
== feek
Odd, I just checked and it doesnāt seem that I changed anything in the Info.plist (vrs 3.3) where this is configured. Iām adding to my bug list to investigate.
It looks like some styling rules have also changed. Is there a list of such changes?
Left side: 3.3.2, right side: 3.5 preview
A bit of nitpicking: the link provided in the 2 empty theme files is not live:
// See http://guide.taskpaper.com/creating_styleSheets.html to get started.
I donāt have a list, but I think the only changes right now are in font and line height. This stylesheet should get you close to 3.3 I think:
@base-font-size: 14;
@font-family: Source Sans Pro;
@line-height-multiple: 1.1;
Note that the font āSource Sans Proā is no longer embedded with TaskPaper, so youāll need to install that manually if you donāt already have it installed.
soā¦after all thisā¦would you ever go back to obj-c or is it swift from here out?
BugReport TP 3.5 Preview (236)
Crashed when i moved an item to another project with " Cmd + \ " Shortcut
In my view it is inconvenient that the searchbar only shows when a search is active. Could you include an option in preferences so that the searbar shows permanently?
Thanks
It seems that also the font-size of the project titles have been changed
Bug:
== feek
I tried to move two selected items using the keyboard shortcut (control+command+up arrow) and TaskPaper crashed multiple times.
I tried moving one item and it worked.
How to make the searchbar something other than white letters on black background, and to increase the searchbar font size? It is difficult to see for low-vision users like me.
Are you dropping support for Yosemite in all coming versions?
Thanks,
Hakan
Iām not able to reproduce this. Can you find a scenario in the āWelcome textā document that reproduces the problem every time?
I havenāt made a final decision, but I expect so now that Sierra is around the corner. Iāve only got two computers I like to keep one on the latest OS and one on the last. Developing for a OS that Iām not running is hard because it means I canāt easily do any testing.
Specifics might change going forward, but here are the search bars current styling rules. You can add these (and change the color values) to your own stylesheet to change searchbar:
searchbar {
appearance: NSAppearanceNameVibrantDark;
color: mix(@background-color, @text-color, 80%);
secondary-text-color: mix(@background-color, @text-color, 50%);
error-text-color: @tint-color;
placeholder-color: mix(@background-color, @text-color, 30%);
background-color: @text-color;
}
Yes, Iāll add a preference to not hide it when it becomes empty.
I tried with the Welcome Text and it didnāt happen. I went back to the document where it happened and it didnāt happen as it had happened before.
Thanks for your fast reply!
Iām stuck on Yosemite due to compatibility issues with soft-/hardware.
I would very much appreciate if you would support Yosemite a little longer, until my other stuff catches up.
All the best,
Hakan