**
 
Mathew,
 
I would think having the Admin to have the ability to choose his preferences whether or not he wants to use the Lock feature might be a great idea too.. Didn't think of that one :-)
 
Joe D'Souza
Remedy Developer / Consultant,
BearingPoint,
Virginia.


----- Original Message ----
From: Carey Matthew Black <[EMAIL PROTECTED]>
To: [email protected]
Sent: Tuesday, August 8, 2006 1:41:30 PM
Subject: Re: Enhancement idea: Field Label for fields

Joe,

Or a similar idea I bumped into in IReports is that you lock all
objects to prevent movement with the mouse. (But still allow movement
via the field properties changes in X,Y values. :)

I am not sure I would like to need to unlock several fields on a tab
to be able to move them later. Rather I would be happy with a "safety"
that tells the tool to ignore those kinds of mouse inputs for now.
(But implemented at run time, and a transient value. Maybe the setting
gets pushed into the admin prefs, maybe not.)

--
Carey Matthew Black
Remedy Skilled Professional (RSP)
ARS = Action Request System(Remedy)

Solution = People + Process + Tools
Fast, Accurate, Cheap.... Pick two.
Never ascribe to malice, that which can be explained by incompetence.


On 8/8/06, Joe DeSouza <[EMAIL PROTECTED]> wrote:
> **
>
>
> Talking about enhancements, another one I wished they had was if they had
> the ability to 'lock' or 'stick' an object to the form so that it wouldn't
> be moved accidently due to an accidental point click and drag operation that
> happens so often especially if you are working from a laptop that has a
> touchpad on.. I love touchpads on laptops and hate to turn them off...
>
> So basically if they had an option on the properties of a field with a check
> box or drop list choice to Lock / Unlock. That would be a really handy one
> to have with the default on creation of the field to keep it unlocked...
> Once you have the form design close to final you start locking objects on
> the form so you wouldn't accidently move them around..
>
>
> Cheers
>
> Joe D'Souza
> Remedy Developer / Consultant,
> BearingPoint,
> Virginia.
>
>
>
> ----- Original Message ----
> From: Carey Matthew Black <[EMAIL PROTECTED]>
> To: [email protected]
> Sent: Tuesday, August 8, 2006 11:53:06 AM
> Subject: Re: Enhancement idea: Field Label for fields
>
>
>
> Joe,
>
> I would even be happen with "on focus" working for Text objects in a
> search window so that they could "simulate" what a field label does
> for the Advanced Search Bar(ASB). (So you could use a Text objects as
> the label for a field, and leave the field lable "blank".) I would
> prefer a special field for all fields to let the admin specify what
> the ASB string should be so that we do not need to build active links
> per field, but I would take what I could get. :)
>
> [basic logic:
> if field's ASB value is null then
>    do what it does now,
> if ( not null) then
>    use that string/keyword/field reference? instead of what it does now
>     keyword $ NULL $ would result in a "no change" on the ASB.
> ]
>
> --
> Carey Matthew Black
> Remedy Skilled Professional (RSP)
> ARS = Action Request System(Remedy)
>
> Solution = People + Process + Tools
> Fast, Accurate, Cheap.... Pick two.
> Never ascribe to malice, that which can be explained by incompetence.
>
>
>
>
> On 8/8/06, Joe DeSouza <[EMAIL PROTECTED]> wrote:
> > **
> >
> >
> > Would have been nice to have field labels having the capacity to use a
> > carriage return within the field name label.. This would mean you could
> > still have a reasonably short label lenght for a field even if the label
> > lenght was long.
> >
> > I tried copying the return character in the hope to see if it works but
> > apparently not...
> >
> > Cheers
> >
> > Joe D'Souza
> > Remedy Developer / Consultant,
> > BearingPoint,
> > Virginia.
__20060125_______________________This posting was submitted with HTML in it___

Reply via email to