How do synced modules manage parameter values?

[Spogg]

The video helped me reproducing the issue!

Btw., if I ever need a narrator for a video or something, might I ask you? Very cool voice!

Back to topic: I think it is a bug, or at least an issue with Flowstone handling key presses. While watching your video I noticed at one point you released ctrl before releasing the mouse button. And indeed, if I do the following, I can reproduce the issue:
-press ctrl
-click on a not currently selected element
-move the mouse just a tiny bit (just so that the graphic either doesn't move or just by a pixel)
-release ctrl
-release mouse

At that point the sync'd module's graphic will jump be a greater degree than the original and even in a different direction sometimes!

Yay! So it's not my age then

Thanks for the voice comment As a teenager I was chosen to be the DJ for the "discotheque" group me and a few friends created together, because they said I had the best voice. My hat size has increased significantly since that day I should have used a compressor for the video's audio but it was done very quickly. It's amazing how much the level varied; it got much quieter as I got more focused on the schematic. If you want me to offer my professional services how much should I charge per word?

Returning to the issue: I already thought of select-contrl-drag-uncntrl sequencing but it made no difference. I maybe should have mentioned that. Have you found a way of avoiding the issue by the sequencing? I did get the moving-in-wrong-direction thing once but I didn't find a way to reproduce it...

Thanks for this. Do you think I should send my video off as a bug report?

Cheers

Spogg

[tulamide]

If you want me to offer my professional services how much should I charge per word?

You can actually charge quite a lot. Professional voice talents on average charge about GBP 80-100 per 30 seconds (which is about 60-100 words, depending on demanded speed)

Returning to the issue: I already thought of select-contrl-drag-uncntrl sequencing but it made no difference. I maybe should have mentioned that. Have you found a way of avoiding the issue by the sequencing? I did get the moving-in-wrong-direction thing once but I didn't find a way to reproduce it...

Thanks for this. Do you think I should send my video off as a bug report?

Well, I never experienced this issue before, and I never before released CTRL before releasing the mouse. This tells something
In general, programmers are used to nested conditioning, so I would always recommend to do the opposite at end of what you do at start.

+CTRL
+LMB
-LMB
-CTRL

But of course it should work with any combination, so definitely send the video as a bug report! Maybe even with my description, so that MyCo/DSPR can reproduce it easier than we could

[Spogg]

Well, I never experienced this issue before, and I never before released CTRL before releasing the mouse. This tells something
In general, programmers are used to nested conditioning, so I would always recommend to do the opposite at end of what you do at start.

+CTRL
+LMB
-LMB
-CTRL

But of course it should work with any combination, so definitely send the video as a bug report! Maybe even with my description, so that MyCo/DSPR can reproduce it easier than we could

Well as usual you cracked it! The sequence above always works
I guess my keyboard/mouse combination sequence was random based on the assumption the the cntrl key simply altered the snap-to function whenever it was pressed (which, actually, it does seem to do).
Armed with this insight I managed to find possibly the worst sequence to use:
+LMB
+CTRL
<drag>
-CTRL
-LMB
This produces a disaster but it highlights the issue wonderfully.

I'll compose an email with this info and the video and I'll post if/when I get a response.

Thanks tulamide. One more step towards God status

Cheers

Spogg

[Spogg]

Well, DSPR responded within a couple of hours and said it would be fixed in the next version, so a good outcome.

Cheers

Spogg

[tulamide]

Well as usual you cracked it!

I'll tell a secret I never told before. It's hard training in the past

I started my work life as a city clerk, and 50% of my job was to teach teens (just a few years younger than me) how to work with Notator on the Atari ST with a Korg M1. That was at a time, where most teenies knew a computer from sci-fi-literature only. And so I had to do all the basics (what's a mouse, how to start programs, user interface, menu bar, etc.)

I also worked for a Macintosh-Reseller that focused on big companies as a so-called supporter. We were all trained by Apple in the most important applications of that time, like Adobe Photoshop, Adobe Illustrator, QuarkXPress, the MacOS and of course all of the hardware, including printers, displays and the like. My job then was to deliver and install the hardware, install all software, to repair whatever breaks (soft- or hardware) and help the customer with all questions arising. I also worked in our own phone-hotline for about 6 months. That was a funny experience ("Yes, I understand your issue. Please have a look at the desktop, there's an apple. Click on it" ... ... ... "Did you click?" "I'm sorry, but there is no apple on my desktop, I really looked for it!" It turned out he was looking at his real desktop )

Later I worked for Bauer Media Group as a chief system officer, where I was in charge for all things technical of an editorial office (130 workatations). Each minute of print delay cost €40000, so I had almost no pressure when solving issues (And of course, issues only arose 5 minutes before deadline^^)

I guess I can say that I'm used to finding solutions. Any solution that keeps people working on their PCs.

[RJHollins]

how to work with Notator on the Atari ST with a Korg M1

Those were the daze !

I had to start with C-Labs 'CREATOR', because NOTATOR was yet to be released.

I still have 2 Atari STe, both Color and Monochrome monitors, Notator with the UNITOR breakout box. ... and THOUSANDS of floppy disks.

Still have the original Korg M1. It was struck by lightening so the MIDI is shot Some of the top session players had been on those keys [including good friend Michael McDonald, Don Randy, Wizniak ... ah too many].

Anyway ... though it couldn't handle audio, I still think NOTATOR is better than most any sequencer out there now. LOGIC tried ... but they went full MAC ... I didn't.

ah ... fond memories

[Spogg]

Fascinating stuff guys. We seem to have a lot of history between us. If you can persuade BobF to spill some beans he has an interesting past. It's up to him of course...

What kinda bugs me is that I didn't work out the sequence that was causing the problem. I thought I'd tried the mouse/kbd sequence but I didn't try hard enough. And it was a classic mistake, one I've been caught out by quite a few times over the years: ASSUMPTIONS. It's really tricky to get around this because one's assumptions are often unconscious. In this case the assumption was that this was a bug so I didn't dig too deep to fully analyse it. Oh well, more experience.

I was told there is a German saying that experience is what you get just after you needed it! Maybe tula can verify...

Cheers

Spogg

[tulamide]

Well there is a sentence: Hinterher ist man immer klüger!
Translated more closely to the words it means: You're always wiser afterwards!

I found out that tracing an error (be it a bug or just some misbehaviour) is much like working as a doctor: Here are the symptoms, now find the cause. The best way to help yourself is to do, what your cousin does all the time. Act logically

(1) What was the situation when it happened?
(2) Are there other ways to produce the issue?
(3) What exactly could I have done, step by step?
(4) Humans are individuals and so is their work. Therefore expect to experience what you didn't expect.
(5) Humans make mistakes. That's just normal. Did I make a mistake?
(6) Find the unusual. If it is a bug you will always find at least one thing that's unusual.
(7) See the bigger picture. Appications have their parts connected through code. Some problem might occur at B, but also might have been introduced in A
(8) Don't be afraid to ask for help. But don't assume anything (see (4) ) or try to shortcut explanations. The more (and the more exact) information, the more help.

[Spogg]

Nice list!

Logic is important and emotion only hinders. Shouting at the monitor NEVER helps

Our equvalent saying to your German version is "Wise after the event". Which I am.

Cheers

Spogg