Hide Functions

[Cristiano]

Hi,

I'm finishing my software and I'm already thinking of future implementations of the same (3 versions STANDARD, Pro and ADVANCED ), it would be possible to 'HIDE' or 'DISABLE' some buttons or functions of the software to those who bought the smaller version? If yes is correct tu use a table to create this future ?


Thank you

[Stan Mathews]

Re: Hide Functions

it would be possible to 'HIDE' or 'DISABLE' some buttons or functions of the software to those who bought the smaller version?

Are you asking how to do this manually or with code?

[MikeC]

Re: Hide Functions

Cristiano,
My initial thought would be to have a logical field that is then referenced for the objects you want to hide...using an if-then statement you could then hide or show objects. Of course you have to have some way to change the logical field for those with all priviledges---could even be a password protected button that when pushed does this.

Probably a ton of other methods, but this would be easy in my mind to do.

[Mike Wilson]

Re: Hide Functions

Why would you not have three completely different versions?

I'm easily confused so if all three "version" had to exist in the one application, I guess I might think about building the most advanced application, triplicate the layouts, one for each version, naming the layout as such, like main_menu_st, for the standard version, main_menu_pro for the pro, and main_menu_adv for the advanced, then change the layout as needed to a construct for the version it is to be part of, and have a startup function that removes the suffix of all the layouts for that version to the base name which the layout will run under using layout_rename(). I would have an application systems table that would have a field holding the value of the version the application was to run under, and then have a single system UDF called at the very start of the application UDF's that are needing the discrimination, that checks for the version, and directs whether that function will or will not run.

That's off the top of my head.

[glenschild]

Re: Hide Functions

Personally I am not sure I would want to have 3 of each forms which are fundamentally the same basic layout. If any of the basic stuff needed changing that would need to happen three times.

How about declaring a global variable at startup that sets the level and using that to show/hide the appropriate menu buttons etc. Would probably add to the original build time but longer term sure to save time.

You could probably build the level into a licence key which could be examined at start up to set the variable correctly.

Regards

Glen

[Cristiano]

Re: Hide Functions

Hi, guys and thanks for reply. In effect reading better my question, is not explained clearly.

The wersion that I have in mind would be 3, but only with some implementations on more of the minor version. For example the Advanced Version could be include some statistics of sales that the Standard version do not use .
In effect the 'form' will be only one, but if a client want to buy the STANDARD version, I need to 'HIDE' this form or some button of this form .

I think that the suggestions of MikeC and Mike Wilson could be interesting .

Thanks again

[CALocklin]

Re: Hide Functions

There are many ways to hide things.

One way is to use the <object_name>.hide() command for every object you want to hide. It works but it seems rather "non-intuitive" to me and requires that you write code for the OnActivate event to hide/unhide objects.

You can also use conditional objects. Each conditional object can have different layers which means that each layer will have its own "condition" and you can show various things for various user types (or other conditions). This would probably be my first choice.

ONE WARNING - Do NOT embed one conditional object inside another conditional object. This is especially true if your conditional objects are on a tabbed form. Apparently the tabbed object is almost like a third "conditional object" or sorts. My past experience showed that I could sometimes make it work IF I did everything exactly right and in the correct sequence. However, one little, tiny mistake and it was almost as easy to start over from scratch. It would take me 3-4 paragraphs to explain how to fix it.

See attached screenshots to see how I used this technique in one form to lead the user through the appropriate fields to fill in.

In case they don't come out in sequence, the correct order is "New_order..."
new
up
flier
rider
appt

and to show a completely different option:
replace

This is all done with conditional objects. It was done this way because the original "owner" had trouble when temp help came in - they kept filling in fields that shouldn't have been filled in. Apparently they thought that if the field was there, it should be filled in. We fixed that - the field isn't there now unless it should be filled in.

[jkukuda]

Re: Hide Functions

In my app I use a table called dummy, which is only one record with 6 fields. Then on startup I create six variables, vOption1,vOption2, etc. and check that the date for that option is valid. If it is I set the option to true. Then in my forms and menus I make the option buttons conditional. If the option is not true(paid for) the user dosen't see it,can't use it. The dummy table is encrypted so the user cannot alter it.

[Cristiano]

Re: Hide Functions

In my app I use a table called dummy, which is only one record with 6 fields. Then on startup I create six variables, vOption1,vOption2, etc. and check that the date for that option is valid. If it is I set the option to true. Then in my forms and menus I make the option buttons conditional. If the option is not true(paid for) the user dosen't see it,can't use it. The dummy table is encrypted so the user cannot alter it.

Great, but can you post a sample of your job? in that table you can, also, insert a date for the ending of all the job ( for example using for a demo) ?


Thanks

[Jerry Hartness]

Re: Hide Functions

Cal, (forgot how to do a quote, but you said)

ONE WARNING - Do NOT embed one conditional object inside another conditional object. This is especially true if your conditional objects are on a tabbed form. Apparently the tabbed object is almost like a third "conditional object" or sorts. My past experience showed that I could sometimes make it work IF I did everything exactly right and in the correct sequence. However, one little, tiny mistake and it was almost as easy to start over from scratch. It would take me 3-4 paragraphs to explain how to fix it.

I agree with the one little, tiny mistake and you're out and will have to start over. Attached is a 3-layer conditional object that did take me some time to
do to get it as close to perfect as possible. The left side is (where the tire sizes/tread depth, etc) a 3-layer object. One the other side the tread
patterns are a 3-layer object and each is selected based on the Wheel Conf field. When I click from different vehicles (on the right side) you will notice some slight movements in the fields. It's not perfect, but works well.

(Of course, a Ford Explorer does not have 8 tires on it)

Jerry

[CALocklin]

Re: Hide Functions

Keep a backup now that it's working - just in case.

As I recall, there was a certain sequence that caused the objects inside my conditional objects to "disappear". (Or, more correctly, a certain sequence to keep them from disappearing.) It turned out that the only way to "see" them once they disappeared was to lasso everything else one layer at a time using the keyboard "-" key to lasso only the visible objects, move those objects out of the way - repeating for each tab of the tabbed object until nothing was left in the original location. When finally "nothing was left" you would lasso everything in the original location but NOT use the "-" key and ... there they were - the 8 "handles" for each of the missing objects. You couldn't see the objects themselves - just the "handles" on each corner and side - and the only thing you could do with them was to delete them. There was no way to bring them forward and make them visible.

[jkukuda]

Re: Hide Functions

'_______________________Option Features______________________________
default_encryption_key_set("xxxx")
SLEEP(1)
dim option as d
vrecordnum=recno
y=.f.
tbl = table.open("Dummy",FILE_RW_SHARED)
tbl.fetch_first(recno)
Option = tbl.eval("Option1")
IF Option>=date() THEN
	OptionReports =.t.
END IF
Option = tbl.eval("Option2")
IF Option>=date() THEN
	OptionPrint =.t.
END IF
Option = tbl.eval("Option3")
IF Option>=date() THEN
	OptionInJail =.t.
END IF
Option = tbl.eval("Option4")
IF Option>=date() THEN
	OptionWeb =.t.
END IF
Option = tbl.eval("Option5")
IF Option>=date() THEN
	OptionWarrants =.t.
END IF
tbl.close()
default_encryption_key_set("")
end

Here is the code in my autoexec that reads the encrypted table and sets the variable. Is this what you wanted?