Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #878 > unrolled thread
| Started by | Rob Smith <rasmithhalifax@googlemail.com> |
|---|---|
| First post | 2011-04-17 04:57 -0700 |
| Last post | 2011-04-26 07:25 +0200 |
| Articles | 17 — 5 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
bBrowser Editable Rob Smith <rasmithhalifax@googlemail.com> - 2011-04-17 04:57 -0700
Re: bBrowser Editable "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-04-17 22:12 +0000
Re: bBrowser Editable D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-18 06:47 +0200
Re: bBrowser Editable "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-04-19 22:15 +0000
Re: bBrowser Editable D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-20 09:19 +0200
Re: bBrowser Editable "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> - 2011-04-20 19:36 +1000
Re: bBrowser Editable D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-22 18:11 +0200
Re: bBrowser Editable "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-04-20 21:50 +0000
Re: bBrowser Editable D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-22 18:19 +0200
Re: bBrowser Editable "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-04-23 00:57 +0000
Re: bBrowser Editable D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-24 07:09 +0200
Re: bBrowser Editable "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-04-25 22:44 +0000
Re: bBrowser Editable D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-26 21:29 +0200
Re: bBrowser Editable "Geoff Schaller" <geoffx@softwarexobjectives.com.au> - 2011-04-26 22:19 +0000
Re: bBrowser Editable D.J.W. van Kooten <public@ic2remove.this.com> - 2011-04-27 17:48 +0200
Re: bBrowser Editable "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> - 2011-04-29 20:05 +1000
Re: bBrowser Editable Joachim Bieler <support@votools.com> - 2011-04-26 07:25 +0200
| From | Rob Smith <rasmithhalifax@googlemail.com> |
|---|---|
| Date | 2011-04-17 04:57 -0700 |
| Subject | bBrowser Editable |
| Message-ID | <566ea3b0-3e74-4588-ae9e-7f0b81204957@x37g2000prb.googlegroups.com> |
Hi I'm using bArrayServer and wish to disable editing the first column Relevant code is self:oDCbBrowserDataBS:Editable:=true self:oDCbBrowserDataCR:Editable:=true self:oDCbBrowserDataPL:Editable:=true oDataColumn:=self:oDCbBrowserDataBS:GetColumn(#YEAR) oDataColumn:Caption:="Year" oDataColumn:Width:=180 oDataColumn:Editable:=false The caption and width work fine, but it still allows editing of all columns, what am I doing wrong? Thanks Rob
[toc] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-04-17 22:12 +0000 |
| Message-ID | <4dab65c1$0$55568$c30e37c6@exi-reader.telstra.net> |
| In reply to | #878 |
Rob, Did you call Recalculate() on the browser where you changed the column after the change? Geoff "Rob Smith" <rasmithhalifax@googlemail.com> wrote in message news:566ea3b0-3e74-4588-ae9e-7f0b81204957@x37g2000prb.googlegroups.com: > Hi > > I'm using bArrayServer and wish to disable editing the first column > > Relevant code is > > self:oDCbBrowserDataBS:Editable:=true > self:oDCbBrowserDataCR:Editable:=true > self:oDCbBrowserDataPL:Editable:=true > > oDataColumn:=self:oDCbBrowserDataBS:GetColumn(#YEAR) > oDataColumn:Caption:="Year" > oDataColumn:Width:=180 > oDataColumn:Editable:=false > > The caption and width work fine, but it still allows editing of all > columns, what am I doing wrong? > > Thanks > > Rob
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2011-04-18 06:47 +0200 |
| Message-ID | <q8gnq6lr4p199ap6fg76b0k9d2mbdlrpir@4ax.com> |
| In reply to | #878 |
On Sun, 17 Apr 2011 04:57:29 -0700 (PDT), Rob Smith
<rasmithhalifax@googlemail.com> wrote:
Hello Rob,
>
>I'm using bArrayServer and wish to disable editing the first column
The trick is this:
In your bBrowser you add indeed:
SELF:odcbBrowser:Editable:=TRUE
But arranging which cells (then/not) to edit is done via the CellEdit
method. Below a working method where only one field (comment) can be
edited by the user. I've written this a few years back so don't know
many details anymore <g>.
METHOD CellEdit(oEvent) CLASS DelCenter
//#s Check if the column is editable and allow edit 8-8-2006 (only
#comment)
// // Callback method for editing a cell in the bBrowser.
// // The method is automatically called by bBrowser
// // Argumete:
// // oEvent : bCellEditEvent
LOCAL oColumn AS bDataColumn
LOCAL auType AS ARRAY
LOCAL cType AS STRING
LOCAL iPos AS INT
LOCAL nCol AS INT
IF oEvent:EditMode=BEDIT_CREATE // create edit control
oColumn := oEvent:Control:GetOpenColumn(oEvent:EditCell:Column)
IF oColumn:FieldSym<>#COMMENT
ErrorBox{SELF:Owner, "Editing not allowed"}:Show()
oEvent:Control:SetFocus()
RETURN FALSE
ELSE
nCol:=oDCbBrowser:CurrentColumn
auType :=oDCbBrowser:PropertyGet(#TypeSpec, {})
iPos := AScan(auType, {|auType| auType[1]==cType})
IF iPos>0 .AND. !auType[iPos, 12] // edit is
not allowed
oEvent:Control:SetFocus()
RETURN FALSE
ENDIF
ENDIF
ENDIF
RETURN TRUE
Dick
[toc] | [prev] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-04-19 22:15 +0000 |
| Message-ID | <4dae097a$0$55570$c30e37c6@exi-reader.telstra.net> |
| In reply to | #880 |
But Dick that is like opening the back door because you've forgotten how
to open the front door.
1. Set the browser to Editable= True
2. Set each of the columns editable = true/false as appropriate
3. Change editable on one or more columns at runtime if necessary
There is no need for such messy callback complexities.
Cheers,
Geoff
"D.J.W. van Kooten" <public@ic2remove.this.com> wrote in message
news:q8gnq6lr4p199ap6fg76b0k9d2mbdlrpir@4ax.com:
> On Sun, 17 Apr 2011 04:57:29 -0700 (PDT), Rob Smith
> <rasmithhalifax@googlemail.com> wrote:
>
> Hello Rob,
>
> >
> >I'm using bArrayServer and wish to disable editing the first column
>
>
>
> The trick is this:
>
> In your bBrowser you add indeed:
>
> SELF:odcbBrowser:Editable:=TRUE
>
> But arranging which cells (then/not) to edit is done via the CellEdit
> method. Below a working method where only one field (comment) can be
> edited by the user. I've written this a few years back so don't know
> many details anymore <g>.
>
> METHOD CellEdit(oEvent) CLASS DelCenter
> //#s Check if the column is editable and allow edit 8-8-2006 (only
> #comment)
> // // Callback method for editing a cell in the bBrowser.
> // // The method is automatically called by bBrowser
> // // Argumete:
> // // oEvent : bCellEditEvent
> LOCAL oColumn AS bDataColumn
> LOCAL auType AS ARRAY
> LOCAL cType AS STRING
> LOCAL iPos AS INT
> LOCAL nCol AS INT
>
> IF oEvent:EditMode=BEDIT_CREATE // create edit control
> oColumn := oEvent:Control:GetOpenColumn(oEvent:EditCell:Column)
> IF oColumn:FieldSym<>#COMMENT
> ErrorBox{SELF:Owner, "Editing not allowed"}:Show()
> oEvent:Control:SetFocus()
> RETURN FALSE
> ELSE
> nCol:=oDCbBrowser:CurrentColumn
> auType :=oDCbBrowser:PropertyGet(#TypeSpec, {})
> iPos := AScan(auType, {|auType| auType[1]==cType})
> IF iPos>0 .AND. !auType[iPos, 12] // edit is
> not allowed
> oEvent:Control:SetFocus()
> RETURN FALSE
> ENDIF
> ENDIF
> ENDIF
> RETURN TRUE
>
> Dick
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2011-04-20 09:19 +0200 |
| Message-ID | <c22tq6dcr26ddko2pcvbjni7d7mivmjmdd@4ax.com> |
| In reply to | #892 |
On Tue, 19 Apr 2011 22:15:20 +0000, "Geoff Schaller" <geoffx@softwarexobjectives.com.au> wrote: Hello Geoff, >But Dick that is like opening the back door because you've forgotten how >to open the front door. >There is no need for such messy callback complexities. I think the celledit is not particularely messy? It allows you to give messages to the user. I think a major problem with most software is that options are made unavailable (e.g. grayed out) without a way for the user to find out why. And altough it may seem obvious for the programmer, I know that it isn't many times for the end user. Dick
[toc] | [prev] | [next] | [standalone]
| From | "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> |
|---|---|
| Date | 2011-04-20 19:36 +1000 |
| Message-ID | <SNxrp.1876$CS3.362@viwinnwfe01.internal.bigpond.com> |
| In reply to | #893 |
Dick By disabling buttons you control the flow of the software (ie only make them active when the user does something that warrants them to be active) Why have a 'Cancel' button active when the user has made no changes, same with a 'Save' button or a 'Delete' button when there's no records to delete. If you make all controls active then you need to program stuff behind them to 'tell' the user why your not going to do anything because they haven't made any changes as yet (stoopid way of doing things IMO) M$ have the right idea with their design guidelines, you should read them<bg> CYA Steve
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2011-04-22 18:11 +0200 |
| Message-ID | <7p93r654rfifb1mqr2eqbd55hqnrg696t8@4ax.com> |
| In reply to | #896 |
On Wed, 20 Apr 2011 19:36:29 +1000, "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> wrote: Hello Steve, > >M$ have the right idea with their design guidelines, you should read >them<bg> > I totally disagree, but I usually do when it concerns MS guidelines. I repeat that in many cases (over 50%) when I encounter a greyed out menu or button I do not know why. And I am not the only one. I agree that disabling options when they should/can't be selected is good, only I think the user should always made clear why not. What I think to be the best solution would be to add a message (tooltip) to the menuitem/control you disable something. Clear for the user, ease to make and elegant. Instead of a tooltop Cut it should say Nothing selected to cut. Dick
[toc] | [prev] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-04-20 21:50 +0000 |
| Message-ID | <4daf5533$0$55570$c30e37c6@exi-reader.telstra.net> |
| In reply to | #893 |
Hmmmm... are we talking about Browsers? But I think you are wrong on several levels. The main one being that I am going to be super frustrated if there are 10 options "available" and I have to click on 9 of them to find out they are not actually available. But hey, a nice little message will pop up to tell me they are not accessible! I'd go nuts. No. Much better that they are greyed out or disabled so that I can see immediately what I can do. Here is how I approach the browser thing: 1. Mostly I DO NOT allow editing in a browser. I find it abhorrent. However, when it is demanded of me and the user is in column edit mode, I grey out the columns not editable. I place the user in the active cell of the current row and automatically invoke Edit. 2. I have a status fixed text on the form advising the client of the current "mode". So that they know what is going on and why certain things are not possible. 3. I change the context menu to display only the available options under the current mode. The context menu will be column specific and sometimes cell specific. It will certainly be mode specific. The trouble is that the Cell Edit approach (whilst useful for validation purposes) is very complex to manage control from. You end up with Gi-normous case statements that look like spaghetti code. Cheers, Geoff "D.J.W. van Kooten" <public@ic2remove.this.com> wrote in message news:c22tq6dcr26ddko2pcvbjni7d7mivmjmdd@4ax.com: > On Tue, 19 Apr 2011 22:15:20 +0000, "Geoff Schaller" > <geoffx@softwarexobjectives.com.au> wrote: > > Hello Geoff, > > > >But Dick that is like opening the back door because you've forgotten how > >to open the front door. > >There is no need for such messy callback complexities. > > > I think the celledit is not particularely messy? It allows you to give > messages to the user. > > I think a major problem with most software is that options are made > unavailable (e.g. grayed out) without a way for the user to find out > why. And altough it may seem obvious for the programmer, I know that > it isn't many times for the end user. > > Dick
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2011-04-22 18:19 +0200 |
| Message-ID | <b9a3r6dblmn27igjaafhcue4imuoss034b@4ax.com> |
| In reply to | #907 |
On Wed, 20 Apr 2011 21:50:42 +0000, "Geoff Schaller" <geoffx@softwarexobjectives.com.au> wrote: Hello Geoff, >But hey, a nice little message will pop up to tell me they >are not accessible! I'd go nuts. No. Much better that they are greyed >out or disabled so that I can see immediately what I can do. Consider MS software. Let's take a very standard W7 program like Wordpad. When (and only when) I move my mouse to e.g. the Paste section of the ribbon I see a full sized tooltip explaining what Paste does. So as this appearing apparently already drivers you nuts anyway, it could as well tell the user something like (Paste: Paste the content of the clipboard - nothing on the clipboard yet). Of course this is a pretty clear but often things are not. I think you get the idea: tooltip appears anyway, so better let it be informative to th user. Unless you prefer your users to be kept in the dark. > > >The trouble is that the Cell Edit approach (whilst useful for validation >purposes) is very complex to manage control from. You end up with >Gi-normous case statements that look like spaghetti code. > I agree. In my sampe I think it is not less manageable than your solution but with some more fields to edit, your solution sounds good. Dick
[toc] | [prev] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-04-23 00:57 +0000 |
| Message-ID | <4db22404$0$55571$c30e37c6@exi-reader.telstra.net> |
| In reply to | #923 |
Hmmm... I don't think we agree at all. I have never used word pad so I don't understand your issues with it (in fact, I don't know anyone who has ever used it). But if I right-click this news pos I get a fairly full menu that has available functionality greyed out. When paste is possible, the paste options display. This is good. Now this is a small menu so I guess it is OK. But what when there are 50 options? Certainly I do not want my context menus to become a pseudo help manual to the application. It is better that stuff not even remotely possible just should not be there. I definitely don't want it available to select and then have a pop up telling me I was stupid for even trying it <g>. Geoff "D.J.W. van Kooten" <public@ic2remove.this.com> wrote in message news:b9a3r6dblmn27igjaafhcue4imuoss034b@4ax.com: > On Wed, 20 Apr 2011 21:50:42 +0000, "Geoff Schaller" > <geoffx@softwarexobjectives.com.au> wrote: > > Hello Geoff, > > > >But hey, a nice little message will pop up to tell me they > >are not accessible! I'd go nuts. No. Much better that they are greyed > >out or disabled so that I can see immediately what I can do. > > > Consider MS software. Let's take a very standard W7 program like > Wordpad. When (and only when) I move my mouse to e.g. the Paste > section of the ribbon I see a full sized tooltip explaining what Paste > does. So as this appearing apparently already drivers you nuts anyway, > it could as well tell the user something like (Paste: Paste the > content of the clipboard - nothing on the clipboard yet). > > Of course this is a pretty clear but often things are not. I think you > get the idea: tooltip appears anyway, so better let it be informative > to th user. Unless you prefer your users to be kept in the dark. > > > > > > >The trouble is that the Cell Edit approach (whilst useful for validation > >purposes) is very complex to manage control from. You end up with > >Gi-normous case statements that look like spaghetti code. > > > > > I agree. In my sampe I think it is not less manageable than your > solution but with some more fields to edit, your solution sounds good. > > Dick
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2011-04-24 07:09 +0200 |
| Message-ID | <qmb7r6hrfej2dg53o2o81p7nuq7934268q@4ax.com> |
| In reply to | #924 |
On Sat, 23 Apr 2011 00:57:39 +0000, "Geoff Schaller" <geoffx@softwarexobjectives.com.au> wrote: Hi Geoff, >Hmmm... I don't think we agree at all. Or you don't get the point: consider this: > >I have never used word pad so I don't understand your issues with it I don't use Wordpad either and don't have an issue with it. I'll just use it to illustrate that most programs show a tooltip explaining what the menu item does anyway (of which you said it drives you nuts). So what would that matter if that tooltip simply adds WHY it is not selectable? It would just make it easier for users but that seems to be something most softwaremakers do not want to happen. Another example. I use Agent for news reading. In the insert menu I have one greyed out option: Signature. Status message is: Insert a signature in the body of the message. No idea why I can't do that or what I need to do to have it working. Would be user friendely if it says why it is grayed out. Simple, elegant. Why would someone be against that? Dick
[toc] | [prev] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-04-25 22:44 +0000 |
| Message-ID | <4db5f969$0$77723$c30e37c6@exi-reader.telstra.net> |
| In reply to | #925 |
Menu items don't usually have tool tips - that wouldn't make sense. But it is really starting to sound like you don't want to read the manual or learn how to use a product. You are expecting almost full help automation within the app. No-one has the time or money to do such a thing. Let's take your signature thing: there might be 10 valid reasons why a signature cannot be added at this point. Which one does the app choose to display you? All 10? What about context? Can't we at least ascribe some intelligence to the user? This is why MS's new ribbon format in Office 2007/1010 has been so successful and so universally praised. The ribbon shows most of the key functionality available for the current mode of use, without limiting your access to other stuff should you need it. Geoff "D.J.W. van Kooten" <public@ic2remove.this.com> wrote in message news:qmb7r6hrfej2dg53o2o81p7nuq7934268q@4ax.com: > On Sat, 23 Apr 2011 00:57:39 +0000, "Geoff Schaller" > <geoffx@softwarexobjectives.com.au> wrote: > > Hi Geoff, > > > >Hmmm... I don't think we agree at all. > > > Or you don't get the point: consider this: > > > > >I have never used word pad so I don't understand your issues with it > > > I don't use Wordpad either and don't have an issue with it. I'll just > use it to illustrate that most programs show a tooltip explaining what > the menu item does anyway (of which you said it drives you nuts). So > what would that matter if that tooltip simply adds WHY it is not > selectable? It would just make it easier for users but that seems to > be something most softwaremakers do not want to happen. > > Another example. I use Agent for news reading. In the insert menu I > have one greyed out option: Signature. Status message is: Insert a > signature in the body of the message. No idea why I can't do that or > what I need to do to have it working. Would be user friendely if it > says why it is grayed out. Simple, elegant. Why would someone be > against that? > > Dick
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2011-04-26 21:29 +0200 |
| Message-ID | <1k6er6d9m4khh0jjn064fh140v1ks159sk@4ax.com> |
| In reply to | #939 |
On Mon, 25 Apr 2011 22:44:56 +0000, "Geoff Schaller" <geoffx@softwarexobjectives.com.au> wrote: Hello Geoff, >Menu items don't usually have tool tips - that wouldn't make sense. Every part of the ribbon so praised by you has a tooltip. Menu's often have status line info. >No-one has the time or money to do such a thing. >Let's take your signature thing: there might be 10 valid reasons >why a signature cannot be added at this point. It's 30 seconds work per tooltip. Once you have programmed the line to disable it you write a line of code changing the explanation in the tooltip as at that point you know which of the 10 reasons it is disabled applies. Mind, I don't ask you to put it in your software. I simply don't understand why such a simple thing to make software more user friendly isn't done more often. >Can't we at least ascribe some intelligence to the user? No. Users don't read the manual. And if you do: the times I have been myself unable to make a certain choise (because disabled) I have hardly ever been able to find the reason why in the manual. So it could be better programmed in the menu anyway. I agree with one thing: you have to be careful what you write. E.g. I was trying to synchronize my Nokia via W7 contacts where I could import a "comma seperated CSV file" . Even the helpfile (Dutch) says: CSV (komma gescheiden waarden). Dit is een algemene bestandsindeling die wordt gebruikt voor het importeren en.... Except that it does not accept a comma! After replacing all my comma's in the dbf fields I finally found out that it had to be a ; Microsoft products... >This is why MS's new ribbon format in Office 2007/1010 has been so >successful and so universally praised. Maybe you live in another universe then? Our clients: 50% not satisfied (I give them one of the classic menu apps), 30% don't mind, 20% happy. Google : "class menu" office : 343000 hits. Dick
[toc] | [prev] | [next] | [standalone]
| From | "Geoff Schaller" <geoffx@softwarexobjectives.com.au> |
|---|---|
| Date | 2011-04-26 22:19 +0000 |
| Message-ID | <4db744d9$0$77725$c30e37c6@exi-reader.telstra.net> |
| In reply to | #952 |
Ribbons are not menus so I expect a tooltip. But Dick, you seem to invent difficulty just to prove your argument. "D.J.W. van Kooten" <public@ic2remove.this.com> wrote in message news:1k6er6d9m4khh0jjn064fh140v1ks159sk@4ax.com: > On Mon, 25 Apr 2011 22:44:56 +0000, "Geoff Schaller" > <geoffx@softwarexobjectives.com.au> wrote: > > Hello Geoff, > > > >Menu items don't usually have tool tips - that wouldn't make sense. > > > Every part of the ribbon so praised by you has a tooltip. Menu's often > have status line info. > > > >No-one has the time or money to do such a thing. > >Let's take your signature thing: there might be 10 valid reasons > >why a signature cannot be added at this point. > > > It's 30 seconds work per tooltip. Once you have programmed the line to > disable it you write a line of code changing the explanation in the > tooltip as at that point you know which of the 10 reasons it is > disabled applies. Mind, I don't ask you to put it in your software. I > simply don't understand why such a simple thing to make software more > user friendly isn't done more often. > > > >Can't we at least ascribe some intelligence to the user? > > > No. Users don't read the manual. And if you do: the times I have been > myself unable to make a certain choise (because disabled) I have > hardly ever been able to find the reason why in the manual. So it > could be better programmed in the menu anyway. > > I agree with one thing: you have to be careful what you write. E.g. I > was trying to synchronize my Nokia via W7 contacts where I could > import a "comma seperated CSV file" . Even the helpfile (Dutch) says: > > CSV (komma gescheiden waarden). Dit is een algemene bestandsindeling > die wordt gebruikt voor het importeren en.... > > Except that it does not accept a comma! After replacing all my comma's > in the dbf fields I finally found out that it had to be a ; > > Microsoft products... > > > >This is why MS's new ribbon format in Office 2007/1010 has been so > >successful and so universally praised. > > > Maybe you live in another universe then? Our clients: 50% not > satisfied (I give them one of the classic menu apps), 30% don't mind, > 20% happy. Google : "class menu" office : 343000 hits. > > Dick
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <public@ic2remove.this.com> |
|---|---|
| Date | 2011-04-27 17:48 +0200 |
| Message-ID | <egegr61gmj8mn2j5khq0fttmp95o85lt21@4ax.com> |
| In reply to | #958 |
On Tue, 26 Apr 2011 22:19:04 +0000, "Geoff Schaller" <geoffx@softwarexobjectives.com.au> wrote: Hello Geoff, >Ribbons are not menus so I expect a tooltip. You're right in there. >But Dick, you seem to invent difficulty just to prove your argument. > I did mean: a tooltip for toolbar buttons and a status line for menu items. About half of the program's I use have this. Only one works as I like it: Winzip. Going through the grayed out options I find e.g. This feature is not available in the Classic mode or You must open an archive before using this menu entry. Very user friendly. Dick
[toc] | [prev] | [next] | [standalone]
| From | "Stephen Quinn" <stevejqNO@bigpondSPAM.net.au> |
|---|---|
| Date | 2011-04-29 20:05 +1000 |
| Message-ID | <48wup.2879$CS3.2170@viwinnwfe01.internal.bigpond.com> |
| In reply to | #923 |
Dick > it could as well tell the user something like (Paste: Paste the > content of the clipboard - nothing on the clipboard yet). Did you actually 'paste' the clipboard contents into the doco (I did and I saw the text I copied in OE). You don't have to cut/copy from within 'WordPad' to paste into 'WordPad'. The 'Paste' option is ACTIVE because there's something on the Clipboard to be pasted. Probably the only time the Clipboard on my machne is empty is right after boot up - I'm not going to re-boot just to test the thought though<bg>. You can write tooltips for every control in VO but the control must be ACTIVE for the user to see them. It doesn't mean they understand what they're reading. They can/will press/select the option, you will have to write the intelligence behind every control then to be sure there's something for the app to do and popup windows saying there's bugger all to do because they haven't selected/changed anything. Much simpler to disable on creation and enable IF the user does something intelligent. CYA Steve
[toc] | [prev] | [next] | [standalone]
| From | Joachim Bieler <support@votools.com> |
|---|---|
| Date | 2011-04-26 07:25 +0200 |
| Message-ID | <91n3b4FskoU1@mid.individual.net> |
| In reply to | #878 |
Hi Rob,
your code is right and should work. One reason why it nevertheless does not work could be that
several columns exist with the name. You can check this with the code below:
iDuplicate := 0
for iPos := 1 upto oBrowser:ColumnCount
oColumn := oBrowser:GetColumn(iPos)
if oColumn:NameSym = #YEAR
iDuplicate += 1
endif
next
if iDuplicate > 1
? "Column exists repeatedly."
endif
Regards,
Joachim Bieler
Am 17.04.2011 13:57, schrieb Rob Smith:
> Hi
>
> I'm using bArrayServer and wish to disable editing the first column
>
> Relevant code is
>
> self:oDCbBrowserDataBS:Editable:=true
> self:oDCbBrowserDataCR:Editable:=true
> self:oDCbBrowserDataPL:Editable:=true
>
> oDataColumn:=self:oDCbBrowserDataBS:GetColumn(#YEAR)
> oDataColumn:Caption:="Year"
> oDataColumn:Width:=180
> oDataColumn:Editable:=false
>
> The caption and width work fine, but it still allows editing of all
> columns, what am I doing wrong?
>
> Thanks
>
> Rob
>
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web