Bugs before release

1 view
Skip to first unread message

denstar

unread,
Jun 22, 2009, 3:56:47 PM6/22/09
to cfecli...@googlegroups.com
Ok, I found one. Spaces in attributes.

action = blah is error, action=blah isn't.

Easy fix.

Randy

unread,
Jun 22, 2009, 5:00:33 PM6/22/09
to CFEclipse Developers
One other one that I have noticed before but just remembered as I was
working on some code:

http://trac.cfeclipse.org/cfeclipse/ticket/477

I'll play around with it and see if I can figure out hit works and
come up with a fix.

Randy

unread,
Jun 22, 2009, 6:38:23 PM6/22/09
to CFEclipse Developers
K, I think i fixed the auto-suggest for functions (#477). Need to test
it out and make sure that it doesn't blow anything else up, but it
should only affect the options that are strings on functions that are
not function calls ;)

Also I created a ticket for the spaces in attributes:

http://trac.cfeclipse.org/cfeclipse/ticket/478

Randy

denstar

unread,
Jun 22, 2009, 7:03:25 PM6/22/09
to cfecli...@googlegroups.com
Sweet! I think I fixed the attribute parser, and made it so that given:

<cfblah fun="yes" whack=#no# cool = 'beans' />

You'll get back three attributes w/ values (added hash as a delimiter,
nixed the space and equal sign, which I'd had in there before).
Betterer and betterer.

I'll go ahead and do another build, so folks can test the latest.
:D

--
It is normal to give away a little of one's life in order not to lose it all.
Albert Camus

Randy

unread,
Jun 22, 2009, 8:22:08 PM6/22/09
to CFEclipse Developers
K, there was a bug with the cfif statement from that change, I think
that I have updated the regex to handle the change.

Now I'm trying to figure out how to get the content assist to trigger
when its not in the attribute="value" format (ex trigger for attribute
= "value"<space>).

Randy

burnsra

unread,
Jun 22, 2009, 9:25:20 PM6/22/09
to CFEclipse Developers
Randy/Denny -

I am still seeing double click weirdness with the text selection
functionality. When I double click on text to the right of a "break-
at-char" such as ".", it selects the text to the left of the ".", not
to the right as expected.

denstar

unread,
Jun 22, 2009, 10:34:01 PM6/22/09
to cfecli...@googlegroups.com
On Mon, Jun 22, 2009 at 6:22 PM, Randy<Zora...@gmail.com> wrote:
>
> K, there was a bug with the cfif statement from that change, I think
> that I have updated the regex to handle the change.

Yeehaw!

> Now I'm trying to figure out how to get the content assist to trigger
> when its not in the attribute="value" format (ex trigger for attribute
> = "value"<space>).

Great minds! I'll stop tracing that and finish the text selection
wrong direction-ness.

Both are set as tickets for the 1.3.2 target, but we can move 'em if
we can't get 'em done prior, yadda yadda.

:D

--
It is not your paintings I like, it is your painting.
Albert Camus

Reply all
Reply to author
Forward
0 new messages