Support

If you have a problem or need to report a bug please email : support@dsprobotics.com

There are 3 sections to this support area:

DOWNLOADS: access to product manuals, support files and drivers

HELP & INFORMATION: tutorials and example files for learning or finding pre-made modules for your projects

USER FORUMS: meet with other users and exchange ideas, you can also get help and assistance here

NEW REGISTRATIONS - please contact us if you wish to register on the forum

Users are reminded of the forum rules they sign up to which prohibits any activity that violates any laws including posting material covered by copyright

sample and hold for visuals

For general discussion related FlowStone

sample and hold for visuals

Postby tester » Mon Sep 22, 2014 6:50 pm

Ruby stuff tends to shut down when processing things related to graphics, like bitmaps, but the issue happens not only on bitmap nodes, but also on yellow "V" visual nodes. And what worse - it may permanently damage the schematic, producing some sort of intangible non-resetable (copy/paste/delete isn't helping) content on yellow nodes. So the question. Is there a way around, to get (or should I say - suck? these things goe in opposide wire direction) visuals from ruby module and hold/block them, so that visuals can be switched with selector - without re-sucking from ruby?
Need to take a break? I have something right for you.
Feel free to donate. Thank you for your contribution.
tester
 
Posts: 1786
Joined: Wed Jan 18, 2012 10:52 pm
Location: Poland, internet

Re: sample and hold for visuals

Postby billv » Mon Sep 22, 2014 9:46 pm

tester wrote:Ruby stuff tends to shut down when processing things related to graphics

any chance of an example of this ruby "shutdown"..?
billv
 
Posts: 1157
Joined: Tue Aug 31, 2010 3:34 pm
Location: Australia

Re: sample and hold for visuals

Postby tester » Mon Sep 22, 2014 10:29 pm

I played with many of these at once, and combined them through common mgui at some points (to export graphic mixtures). Basically, it's easy to create the problem, that stores somewhere on "v" (visual) nodes, because it starts then to shut down ruby's even at 1 pixel bitmaps loaded. And it's not buffered within the ruby window (created new one and entered everything from scratch; connecting visual node turned off the ruby's, while uncrashed seems to work at that point). But I'm still on FS 3.04.
Need to take a break? I have something right for you.
Feel free to donate. Thank you for your contribution.
tester
 
Posts: 1786
Joined: Wed Jan 18, 2012 10:52 pm
Location: Poland, internet


Return to General

Who is online

Users browsing this forum: No registered users and 56 guests