How about improving on the Modify Expression Editor a bit? We have some quite complicated expressions, and the tiny little MLE control that PB uses to allow us to edit expression is very clumsy (and yes, I do realize about the elipse to bring up the modal Modify Expression window - which contains an only slight less tiny MLE for editing the Expression). Not to mention that embedded Returns in the expression can cause the computed field to behave funny. How about a real editor, complete with color markups, support for indentation and carrage returns, AutoScript even!
![]() |
0 |
![]() |
Oooh, yes! I'd like that. Allow new lines and indentations by pressing enter and tab instead of ctrlArnoud wrote in message news:[email protected]... > How about improving on the Modify Expression Editor a bit? We have some > quite complicated expressions, and the tiny little MLE control that PB uses > to allow us to edit expression is very clumsy (and yes, I do realize about > the elipse to bring up the modal Modify Expression window - which contains > an only slight less tiny MLE for editing the Expression). > > Not to mention that embedded Returns in the expression can cause the > computed field to behave funny. > > How about a real editor, complete with color markups, support for > indentation and carrage returns, AutoScript even!
![]() |
0 |
![]() |
Yes, and while we are at it, make this available at run time as well. Like filter() & sort() expression editor is available at run time. "Arnoud Oortwijk"wrote in message news:[email protected]... > Oooh, yes! > I'd like that. Allow new lines and indentations by pressing enter and tab > instead of ctrl > > Arnoud > > > wrote in message > news:[email protected]... > > How about improving on the Modify Expression Editor a bit? We have some > > quite complicated expressions, and the tiny little MLE control that PB > uses > > to allow us to edit expression is very clumsy (and yes, I do realize about > > the elipse to bring up the modal Modify Expression window - which contains > > an only slight less tiny MLE for editing the Expression). > > > > Not to mention that embedded Returns in the expression can cause the > > computed field to behave funny. > > > > How about a real editor, complete with color markups, support for > > indentation and carrage returns, AutoScript even! > >
![]() |
0 |
![]() |
I voted for this suggestion in the general group by mistake. I again vote for it here. -- Rahul Jainwrote in message news:[email protected]... > How about improving on the Modify Expression Editor a bit? We have some > quite complicated expressions, and the tiny little MLE control that PB uses > to allow us to edit expression is very clumsy (and yes, I do realize about > the elipse to bring up the modal Modify Expression window - which contains > an only slight less tiny MLE for editing the Expression). > > Not to mention that embedded Returns in the expression can cause the > computed field to behave funny. > > How about a real editor, complete with color markups, support for > indentation and carrage returns, AutoScript even!
![]() |
0 |
![]() |
Yess!! Count me in too Something like the formula-editor in CrystalReports??? Grtz harryschreef in bericht news:[email protected]... > How about improving on the Modify Expression Editor a bit? We have some > quite complicated expressions, and the tiny little MLE control that PB uses > to allow us to edit expression is very clumsy (and yes, I do realize about > the elipse to bring up the modal Modify Expression window - which contains > an only slight less tiny MLE for editing the Expression). > > Not to mention that embedded Returns in the expression can cause the > computed field to behave funny. > > How about a real editor, complete with color markups, support for > indentation and carrage returns, AutoScript even!
![]() |
0 |
![]() |
My $0.02 FOR this one!
![]() |
0 |
![]() |