Tab Panel problem

[bjb007]

I've put a tab panel on a main stack
with four tabs.

Objects I've put on the fourth tab
also appear on the other three - which
is not what I want.

How do I restrict objects to the tab
on which I put them?

[malte]

what do you do in the tabs script?

I would either put the tab into a group with backgroudbehaviour set to true and create a card for each tab, then in the script of the tab:

on menupick pWhich
go cd pWhich
end menuPick

or work with groups of objects you dynamically hide or show.

All the best,

Malte

[bjb007]

I naively assumed that once I set up
the various tabs I could just - tab between
them without further effort. The way other
languages work.

Seems not.

This and the "a combobox is a button" thing
is the kind of perverse idiosyncrasy that
condemns Rev to stay forever in the back-
woods of languages. Who would want to
switch to Rev knowing they had to re-learn
just about everything they know about
programming?

[keyless]

I naively assumed that once I set up
the various tabs I could just - tab between
them without further effort. The way other
languages work.

Seems not.

This and the "a combobox is a button" thing
is the kind of perverse idiosyncrasy that
condemns Rev to stay forever in the back-
woods of languages. Who would want to
switch to Rev knowing they had to re-learn
just about everything they know about
programming?

Think about it some more, the fact that the tab panal is card or stack based makes it wildly more functional then the same widget in most other languages (i.e you can switch up and change the tabs contents and controls at runtime with ease).

Making it work any other way would make it a idiosycrasy of the card based logic of revolution itself.

Quite simple learn how to use cards and stacks in Revolution as you really have too, and you will already know how to use the combobox.

[Klaus]

...Who would want to
switch to Rev knowing they had to re-learn
just about everything they know about
programming?

That's what YOU are asking US????

[bjb007]

Klaus

No, not asking. Just expressing an
opinion. Wondering if there's a
Gordon Ramsey of software.

Found a video "Window Objects" and
after watching it a number of times
I've got a tabbed interface working.

Each "card" title has (1)*, (2)* or (3)*
added to it.

Can I get rig of these extraneous characters?

Edit: Put your title in the "Title" field of the
property inspector and it replaces the
"Name" used by Rev. which has the
(1)* appended.

[malte]

Nobody forces you to use it.

*sigh*

[Klaus]

With all due respect, but do not use your grumpyness (which you do not stop to emphasize and is apparently your way of life) to really annoy us!

"Other languages do this, other languages do that, other languages do something else..."

A Malte says, nobody forces you to use this software, obviously you didn't even bother to take a look at any of the learning resources that we already posted here, especially the Rev "scripting conferences", which in my opinion EVERYONE should be forced to work through before he can post here or to the "use-revolution-list"

Life is definitvely too short to be annoyed by (too) grumpy old men!


Ciao stizzito...

[bjb007]

Klaus

I spent, I would say, two hours at least trying
to figure out the combobox conundrum without
finding that it's called a button in Rev.

English is the language of the internet and
a large percent of the world (much to the annoyance
of the French) but the advantages of having
a common language are lost the moment a
user decided that he'll give a particular object
a different name or a particular word a
different meaning.

In this case someone has decided that a combobox
will be called a button and that has caused a
breakdown in the communication.

[mcgrath3]

I spent, I would say, two hours at least trying
to figure out the combobox conundrum without
finding that it's called a button in Rev

It only takes two seconds to search the Revolution Dictionary for Combobox to find:


The menuMode of a button is one of pullDown, cascade, popup, tabbed, comboBox, or option.

[mcgrath3]

Search The Revolution Dictionary:


-------------------
Search the Rev Dictionary for ComboBox
MenuMode
Use the menuMode property to specify the appearance and behavior of the menu associated with a button.

Value:
The menuMode of a button is one of pullDown, cascade, popup, tabbed, comboBox, or option.

Comments:
Any button's contents can be viewed as a menu if the button's style property is set to "menu". The menuMode setting creates menus of different types from the button's contents. (You set the button's contents with the text property.)

-------------------
Search the Rev Dictionary for Menu
Comments:
If a button's style is set to "menu", its menuMode property determines how the menu is displayed when the user clicks the button.

You can use the menu keyword to refer to one of the buttons in the current menu bar.

--------------------
Search the Rev Dictionary for Button
Comments:
Button objects can be push buttons, checkboxes, radio buttons, or menus, depending on the setting of their style property.

A button whose style is set to "menu" can be a popup or contextual menu, pulldown menu, option menu, tabbed button, or combo box, depending on the setting of its menuMode property.

[FourthWorld]

English is the language of the internet and
a large percent of the world (much to the annoyance
of the French) but the advantages of having
a common language are lost the moment a
user decided that he'll give a particular object
a different name or a particular word a
different meaning.

It's worse than you think: in the Windows API comboboxes are windows. No, really. In fact, every control is a window. Even windows, which aren't controls.

In HTML, option controls and text lists are considered the same object.

This isn't a conspiracy to drive English teachers mad. It's merely an attempt to identify common underpinning, and classify things accordingly.


The joshua tree looks like a cactus, and is often confused for being a mutant yucca, but is -- I kid you not -- actually in the lily family. Only the most superficial aspects of the joshua tree resemble a yucca or catcus, but on closer examination it meets all the definitions of a lily.

Taxonomies are difficult things to do well. To have completely separate words for everything denies us the opportunity to exercise the benefits of referring to collections of things by a larger group name.

I have my own mixed feelings about the use of "button" for all selector objects, and perhaps one could argue that they might deprecate "button" in favor of "selector".

But in practice, once you understand that "button" is used in Rev as a simple, less formal-sounding replacement for "selector", it all becomes clear. Or at least clearer than both the Windows and JavaScript APIs.

[mcgrath3]

Yeah, Except in this case it is less about whether or not the combobox is 'called' a button but rather that 'menu' is a STYLE of a button.

A button whose style is set to "menu" can be a

This is deeper than where to 'put' or associate the combobox in relation to menu's or button's or control's or selector's. Instead it is buried in the fact that 'menu' is a style of a button object.

That is very interesting to me.

Tom McG

[bjb007]

FourthWorld

As you say "The joshua tree looks like a cactus".

But don't tell me that a combobox looks or acts
like a button!

[bjb007]

Nobody forces you to use it.

*sigh*

If you download and try the latest
free "lite" version of VB (Visual Studio)
you might come to the conclusion that
Bill Gates is forcing me to use Rev.