TOPIC: Upcoming Features
Upcoming Features 3 Years, 5 Months ago
Here is what I have been working on lately:
  • Close button on tabs (e.g. in LibraryView. I got used to this in other programs and finally had to add it in Suneido.

  • External splash screen. Makes the exe smaller and allows you to make your own splash screen.

Post edited by: andrew, at: 2007/02/25 22:08
Re:Upcoming Features 3 Years, 5 Months ago
  • "Spell Check" for code in LibraryView - puts a red underline under global names that are not defined and local names that are used only once (in a method).

(Had to do a second post to get another screenshot.)
Re:Upcoming Features 3 Years, 5 Months ago
Sweet !

Hey can we add in the ability to split the scintilla controller too ?

Here are the files to accomplish it..

File Attachment:
File Name:
File Size: 2656
Re:Upcoming Features 3 Years, 5 Months ago
You bet, thanks for the contribution. This can be a handy feature. It is pretty cool how you can type in one pane and it shows in both. Nice that Scintilla supports this.

We could add it to the IDE > Views menu (via plugin). If it was persistent it would be easy to use it all the time.

I wonder if it would be less obtrusive if the splitter was at the bottom, i.e. if the top was open first.

Not sure if I did something wrong, but I just tried it out and it did not save my changes? May need to handle the Dirty? method (along with Set and Get)

PS. You can export multiple records to the same file.

Post edited by: andrew, at: 2007/02/26 20:15
Re:Upcoming Features 3 Years, 5 Months ago

Your right the SplitScintillaControl should have the
Dirty?(dirty = "")
return .ActiveEditor.Dirty?(dirty)

I originally had every method that was available on the editor redefined on this control. But then when new methods came along you would get errors so I changed the control SplitLibViewControl to redelegate the messages to the active editor. I left the (SplitScintillaControl) .Set & .Get methods as they were but missed the .Dirty? method. The issue is that a lot of times .Method?() is called against the object so even if the Default(@args) is defined the method is not invoked.

So should all the methods be duplicated in this control or is the default handler sufficient ?

Re:Upcoming Features 3 Years, 5 Months ago
I think Get, Set, and Dirty? are the main ones. I'll do a little more testing.

The way Send checks if the method exists is awkward. One alternative would be to use "try" but that is not always best because it "hides" real errors. If you only caught "method not found" it might be ok, but then you would have to remember to throw "method not found" from your Default method if you did not handle the method.