Selector checkmark

[tektoog]

Hey,
After all these years, I feel kind of dumb to ask for that but, I actually just realised that
When using submenus with the stock selector, how do you get the checkmark to also show up in the first menu branch?

Selector Checkmark.fsm

(3.55 KiB) Downloaded 1045 times

Is it only possible, or do I have to use a ruby type selector?
A great thanks in advance for your answers...

[trogluddite]

AFAIK, there isn't a way to check a sub-menu heading. It's only possible to check a single item, and it has to be one of the selectable indexes. It works the same way in Ruby, too (and the same for Ruby's option to "grey out" an item).

I'd really like the ability to use arrays to specify multiple ticks or grey-outs - it would be really handy for creating drop-down menus with multiple toggled options etc. There are really only two workarounds...

1) Dynamically modify the options-list string to include your own marker characters when they're needed. This is relatively simple, but it never looks as nice as a proper tick-mark, no matter what characters or font you choose.

2) Build a completely custom selector from basic GUI primitives. This can look very smart, but is a lot harder work, as you'd have to do all of the drawing and mouse handling yourself.

[tektoog]

Trog, thanks for your answer…
… which is the one I was afraid of...

There are really only two workarounds...

This is the conclusion I came to also… but,... I will live with the mark on the second layer
Another small detail, but which has all its importance when you want to present a polished end project…

Should be another small update that would present FS at its best...

[tulamide]

I would additionally also love the ability to insert seperator lines, as in other Windows menus. (I had this weird dream that since then feels like it was real, where I accidentally found an ascii sign that inserted a seperator line)

[Spogg]

...(I had this weird dream that since then feels like it was real, where I accidentally found an ascii sign that inserted a seperator line)

At least your dreams about FlowStone make sense!

[DaveyBoy]

Just came accross this post while searching for drop list posts . . . .

Tulamide wrote:

I would additionally also love the ability to insert seperator lines, as in other Windows menus.

well now you can



It won't be the prettiest code you've ever seen . . but it works

Trog wrote:

Build a completely custom selector from basic GUI primitives. This can look very smart, but is a lot harder work, as you'd have to do all of the drawing and mouse handling yourself.

Well I've had a lot of Flow_time recently and someone had to do it

This is still very much a work in progress. Tick marks and separaters are done . . I'm now looking at sub-menus and greying out . . could take a while!

Windows Menus 32.fsm

(18.46 KiB) Downloaded 959 times

Windows Menus 64.fsm

(18.72 KiB) Downloaded 957 times

Windows Menus 32 - repaired.fsm

Omitted to name wireless input causing cfg file to not be written - fixed

(18.47 KiB) Downloaded 969 times

Enjoy

[tulamide]

Tulamide wrote:

I would additionally also love the ability to insert seperator lines, as in other Windows menus.

well now you can

That's a really nice one! And the code is structered well, it is no problem to follow it. Maybe somewhere in the future we could outsource the graphics elements, so that it is easier for people to adapt it to their style. Other than that: hats off! I can imagine the time it took to create.
Thank you for sharing!

[RJHollins]

That is some nice work DaveyBoy

[tektoog]

well now you can

Haaaaaaaaaaa!!!!
What a good soul you are!!!
Nice work there!
I didn't get that part though... Maybe you could explain it?

Code: Select all

   #   ---------------------------------------   
   when 100   #   File - New               Put Droplist finished code here |
   #   if @menus[@menu_over][:items][@item_over] == true                  |
   #      Do Something                                          |
   #   else Do something else                                       |
   #   end                                                      |
   when 101   #   File - Open                                       |      
   #                                                         |
   when 203   #   Edit - Copy                                       |
   #                                                         |
   when 414   #   Options - Midi Stop                                 |
   #                                                         |
   when 502   #   Help - Check for updates                           V
   
   # etc
   
   # etc
   
   #   ---------------------------------------
   end


This is still very much a work in progress. Tick marks and separaters are done . . I'm now looking at sub-menus and greying out . . could take a while!

Could you maybe also post a functional example of the edit menu? like implementing the undo/redo, cut/copy/paste functions?
But maybe is it too much demanding?

As Tulamide already said

hats off!

It looks really "professional" and polished... Good job!!!

[DaveyBoy]

Thanks for the kind words guys.

Tulamide wrote:
I can imagine the time it took to create.

Writing 'Flow_time' instead of 'Flow-time' is a bit of a givaway

Tektoog - The best way I can think of to explain is to think of banks of switches.
The first bank (File) starts from 100 the second bank {Edit) from 200 . . and so on.

This could all have been put in the mouseLDown method but I thought it better to do it this way

The input numbers are virtual inputs (as opposed to physical inputs) to the Ruby code box and when you select or tick/untick a menu item the event method sees this and acts accordingly. You just need to put some logic in the appropriate event number to make it do what you want it to do.

in the attached example I've implemented the File - Open item and all the Options items. The latter are changing the state of boolean variables. I've put the outputs in the watch panel (was easier for me )

Windows Menus 32 v1.0.1.fsm

(23.76 KiB) Downloaded 968 times

I hope this explains it better

in my original reply, in the 32 bit version I omitted to name a wireless input which would have caused the config file not to be written, this has now been fixed.