Welcome, Guest
Username: Password: Remember me
  • Page:
  • 1

TOPIC:

MIssing option for relations 17 Aug 2016 15:55 #14462

  • MorganL
  • MorganL's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • Posts: 438
  • Thank you received: 53
I may be going insane, but when you first introduced relations type fields (pivots) there were two options

The multi-select fancy combo box (which is what we get now) which is awesome

but there was another option where all the options were laid out like.. for want or a better term.. radio buttons where you just clicked on what you wanted and they changed colour

We now only seem to have the combo box options.. or maybe I am wrong and this was only for enumerations.

Is this an error, or am I making stuff up
Morgan Leecy MCSE

Novell / Linux
PHP. MYSQL, Apache, node.js
Coldfusion, JQuery, HTML5
Joomla

Please Log in or Create an account to join the conversation.

MIssing option for relations 24 Aug 2016 20:49 #14478

I think it was only for enums, but not sure actually....

Please Log in or Create an account to join the conversation.

MIssing option for relations 24 Aug 2016 21:01 #14481

  • MorganL
  • MorganL's Avatar Topic Author
  • Offline
  • Platinum Member
  • Platinum Member
  • Posts: 438
  • Thank you received: 53
I think you are correct, i likely just had a tiny list in an earlier version before I moved to n:n
Morgan Leecy MCSE

Novell / Linux
PHP. MYSQL, Apache, node.js
Coldfusion, JQuery, HTML5
Joomla

Please Log in or Create an account to join the conversation.

MIssing option for relations 25 Aug 2016 12:24 #14489

  • admin
  • admin's Avatar
  • Offline
  • Administrator
  • Administrator
  • Chef
  • Posts: 3711
  • Thank you received: 986
It was only for enumetations in facts, not for n:m
The reason is simple, radio buttons do not allow multiple selections.
Coding is now a piece of cake

Please Log in or Create an account to join the conversation.

  • Page:
  • 1
Time to create page: 0.119 seconds

I jumped and started to work on a demo component... but 2 days later this demo component became the real component. I just showed today the end result to my customer and he turned to me and said... "this is more than I expected"... All of this is because Cook did cut about 70% of my work and provided me more ways to improve the usability of the component. The end result was 17 tables all related between than to generate a full dashboard for the travel agents. Thanks for Cook developers for such great tool. This component would not be possible to be done at short time with all the features in it
Griiettner (Forum)  

Get Started