A few small FRs

galaa · 26 Mar 2005

beno wrote: 1. Add ability to make a single selected object into a module.

If you have a single item and you create a module in & out and connect these to your single item then you have 3 items selected so SM will allow you to create a module from these

beno wrote: 3. The option to not have SM load the example scematic at startup every time. It would be great if there was an option to either load the last used schematic, or a blank schematic.

A workaround for this one for the time being: If you rename the example.osm file within your SynthMaker directory then SM will be unable to find it and will open with a new schematic.

stefan · 26 Mar 2005

This is probably the first time I fully agree on everything said in a feature request for SM. usually I totally disgree, but these requests are all great. Small workflow obsticles that has nothing to do with design etc. Malc and jorge probably agrees as well 🙂

edit: galaa: most of the time when I add code modules I add them directly and specify ins and outs in the code, and later on I want to wrap the code component in a module. I don't think one should need to add stuff to do this.

jorge · 26 Mar 2005

Hi beno, thanks for your suggestions,

beno wrote: 1. Add ability to make a single selected object into a module.

That's something that I have wanted recently too, let's see what malc says, that's related with code he implemented.

beno wrote: 2. I'd like the oposite of Make Module available: Disolve Module.

At least if it is immediately after you made the module, you can use undo. I think it's a good idea for when you cant undo.

beno wrote: 3. The option to not have SM load the example scematic at startup every time.

That can be done by renaming the example.osm file that you'll find in the install folder. [edit] as galaa suggests

beno · 26 Mar 2005

galaa wrote: beno wrote: 1. Add ability to make a single selected object into a module.

If you have a single item and you create a module in & out and connect these to your single item then you have 3 items selected so SM will allow you to create a module from these.

Sorry if I wasn't clear, I just mean if I had a component with lines connecting to some of its inputs and some connecting to some of its outputs. I only want to wrap that single component in a module and have SMautomatically create the Iinput and Output connectors to the module.

Actually that was just an example, whether or not the component is connected, I would still like to be able to make a wrap a single component in a module.

Ben

Edit: I just reread your post. I see what your saying now but that is a lot more unnecesary steps.

beno · 26 Mar 2005

jorge wrote:

beno wrote: 2. I'd like the oposite of Make Module available: Disolve Module.

At least if it is immediately after you made the module, you can use undo. I think it's a good idea for when you cant undo.

Yeah, it was way past the time where I could undo. It was a situation where I had made a design decision and then decided much later on that I gouped things incorrectly so I couldn't undo.

Thanks for the tip about the example file. I'll rename it.

Thanks,

Ben

galaa · 26 Mar 2005

beno wrote: whether or not the component is connected, I would still like to be able to make a wrap a single component in a module.

Yeah sorry, beno, I misunderstood.

stefan wrote: This is probably the first time I fully agree on everything said in a feature request for SM. usually I totally disgree, but these requests are all great. Small workflow obsticles that has nothing to do with design etc

me too

beno · 26 Mar 2005

stefancrs wrote: This is probably the first time I fully agree on everything said in a feature request for SM. usually I totally disgree, but these requests are all great. Small workflow obsticles that has nothing to do with design etc. Malc and jorge probably agrees as well 🙂

Thanks stefancrs. My next one is when I'll request they change the whole thing, make it all text based, and loose the pretty graphics. 😉

Ben

stefan · 26 Mar 2005

beno wrote: stefancrs wrote: This is probably the first time I fully agree on everything said in a feature request for SM. usually I totally disgree, but these requests are all great. Small workflow obsticles that has nothing to do with design etc. Malc and jorge probably agrees as well 🙂

Thanks stefancrs. My next one is when I'll request they change the whole thing, make it all text based, and loose the pretty graphics. 😉

Ben

That's right before I look up your streed adress I guess... 🙂

Tom7777 · 26 Mar 2005

Nice ideas beno, I think i agree mostly with the blank/last used startup idea but then again there is a work around to start with blank project - copy the example to another folder then save a new project as example that way it would load up empty and you would still have the example file if you needed it.

stefan · 26 Mar 2005

Tom7777 wrote: Nice ideas beno, I think i agree mostly with the blank/last used startup idea but then again i think there is a work around to do this - copy the example to another folder then save a new project as example that way it would load up empty and you would still have the example file if you needed it.

But usually you want SM to open up the project that was open when you last shut SM down.

Tom7777 · 26 Mar 2005

But usually you want SM to open up the project that was open when you last shut SM down.

Sorry i made a mistake with the way i wrote my last post, just edited it 🙂

malc · 26 Mar 2005

Hi beno (et al),

I've been away today - Easter and all that 🙂

I have a long list of loose ends that need tying up on the interaction side, your first two suggestions have been on there for a while. Sorry they haven't been done already but prioritising all these things is a nightmare. Anyway, rest assured they will get done 🙂

Myself and Jorge have talked about the issue of the example file loading automatically before. Again it's another small thing that we left for dealing with later.

I think perhaps the best way to deal with this is to have an option to allow you to choose between the last opened file, example or a blank schematic on startup.

Thanks for your suggestions.

kingtubby · 26 Mar 2005

malc wrote: I think perhaps the best way to deal with this is to have an option to allow you to choose between the last opened file, example or a blank schematic on startup.

I concur.

Mart

beno · 27 Mar 2005

malc wrote: Hi beno (et al),

I've been away today - Easter and all that 🙂

I have a long list of loose ends that need tying up on the interaction side, your first two suggestions have been on there for a while. Sorry they haven't been done already but prioritising all these things is a nightmare. Anyway, rest assured they will get done 🙂

Myself and Jorge have talked about the issue of the example file loading automatically before. Again it's another small thing that we left for dealing with later.

I think perhaps the best way to deal with this is to have an option to allow you to choose between the last opened file, example or a blank schematic on startup.

Thanks for your suggestions.

Sounds good to me. Thanks Malc. Ben