Alright guys, v18.104.22.168 is out, here's some of the changes: - added mirror modes to the image drawer - fixed alpha not updating on color switch in image editor - added bg to color box to see alpha colors - optimized image switching, no need to redraw bg if same sized images - changed folder browser for sphere executables to use a file dialog - added font editor to tree view - added error handling to the font editors, (it didn't filter for TT fonts) - fixed not enough margin for folding on larger script files. - made project tree show up first on project loads - quick fix for pausing the modification of the tree view when engine runs. - added an outline when drawing invisible rectangles in the image editor. - minor fixes and changesGet while it's hot! Thanks to some of LordEnglish's suggestions I think it's a bit more comfortable to use now.
g.SmoothingMode = SmoothingMode.None;
One more bug report, then I need to get some sleep: If two files have the same filename and you have one of them open, Sphere Studio gets confused if you try to open the other and just switches to the existing tab, even when the files are in different folders.
Oh, and you're not supposed to commit the .csproj.user files! Those are machine-specific I believe, similar to the hidden .suo file but at the individual project level instead of the solution.
g.TextRenderingHint = System.Drawing.Text.TextRenderingHint.SingleBitPerPixel
Sleep is overrated... I figured out how to solve the ClearType issue without changing the OS settings:Code: (csharp) [Select]g.TextRenderingHint = System.Drawing.Text.TextRenderingHint.SingleBitPerPixel
For the old editor's font-to-RFN, I was mostly fine with changing Windows' rendering settings before conversion. If you're going to force a particular rendering method in the conversion I really think you should allow the user to choose the setting (even through a simple toggle) instead of forcing one (the Adobe Font Folio version of Helvetica Neue, for example, will almost always look better at small sizes when rendered with anti-aliasing instead of turning it off; don't know if Adobe or Linotype updated the hinting since, but at least until Font Folio 11 this is the case).Keep in mind that allowing certain methods of anti-aliasing may not be supported outside of Windows. This is where something consistent like FreeType would come in handy, and if I ever add font conversion to my phoenix-based app I'll use it myself.
I don't know if I would split out the script editor myself--just sounds pointlessly idealistic for no real gain. The main strength of plugins is that you can pick and choose which ones you want to use based on your needs, but I can't think of a single use case where it makes sense to disable the script editor!
Quote from: Lord English on April 16, 2013, 02:51:17 pmI don't know if I would split out the script editor myself--just sounds pointlessly idealistic for no real gain. The main strength of plugins is that you can pick and choose which ones you want to use based on your needs, but I can't think of a single use case where it makes sense to disable the script editor! The reasons would be twofold: one, it would act as a nice test to ensure that the plugin system is sufficiently powerful to handle large plugins with lots of functionality, and two, it would make the core architecture cleaner and easier to maintain.Oh, and I would disable the script editor, seeing as I use Emacs for all my script editing.
And someone can then make a plugin that redirects all script files to "Open With..." Emacs, if it can be done. Do you use it standalone or in a shell such as cygwin? Doesn't really matter, it just changes the method of opening a file that's all.