PlanetSquires Forums

Support Forums => Other Software and Code => Topic started by: David Kenny on November 04, 2009, 12:38:30 PM

Title: Folded routines should be Read-only?
Post by: David Kenny on November 04, 2009, 12:38:30 PM
I think that they should.  You should have to unfold them to edit.

For instance, look at the strangeness that happens (ok, not so strange when you know about it first) if you place your caret in the keyword 'Function' (when folded) and type a character. If you type additional characters, they are now inserted in the same column but in the Sub/Function below.

I can live with the 'strangeness' if the solution is difficult. And it's definitely not a high priority. BTW, undo will fix it for you.

David

Title: Re: Folded routines should be Read-only?
Post by: Paul Squires on November 06, 2009, 08:45:58 AM
Thanks David - I have logged this into my bug tracker. Lots of work to do ont he code editor. Luckily, the code editor is 100% PB code so it should be easier to fix and extend functionality than when I had to work with the C++ based CodeMax/CodeSense control.
Title: Re: Folded routines should be Read-only?
Post by: Mark Strickland on November 06, 2009, 12:59:55 PM
My 2 cents

Building in a SQL engine that makes everybody happy would nearly be impossible.  Sometimes SQLite would be the right tool and sometimes I am forced to interface with some other DB engine.  So you could not even make me happy all of the time.

As much as it would be nice for little "quick and dirty projects" this idea also tries to abstract what is a very complex thing and standardize it.  Putting some of the SQLitening code in the code library probably is helpful and I may give that a shot.  If somebody posted some detailed instructions that might help others to more easily accomplish this task.

SQL is not as simple as managing indexed files like Cheetah.  To do things right you must understand concepts like JOIN (LEFT, RIGHT, INNER, OUTER, and even why you might want to JOIN a table to itself) and many other concepts.  SQL is non-procedural and to use it effectively you must approach a problem differently than with something like Cheetah.  If you understand it SQL becomes very powerful but if you don't you probably will be frustrated or do a bad job designing a database.

With this said ... any integration of SQLitening via the code library would be appreciated.
Title: Re: Folded routines should be Read-only?
Post by: John Montenigro on November 07, 2009, 04:05:21 PM
I'm confused...

First of all, what is "folding", where is it in FF3, and why should I know about it? (What does it do for me?)

Second, how is it related to SQL? Mark's comments make me think I'm missing a BIG chunk of info here...

Halp!
-John
Title: Re: Folded routines should be Read-only?
Post by: Paul Squires on November 07, 2009, 04:10:29 PM
Mark's post was meant for another thread. He accidentally posted it here.

"Folding" allows you fold entire sub/function procedures so that just the first Sub/Function line displays and the End Sub / End Function displays. Folding is triggered by clicking on the
Title: Re: Folded routines should be Read-only?
Post by: John Montenigro on November 07, 2009, 04:28:58 PM
Hot stuff!!! That is a NEAT feature!

And I like that there are already functions for FoldAll/UnfoldAll...

Wowza!