Minor issues with 0.9.2g

galaa · 27 Mar 2005

I seem to be missing the freq to Pitch component. Is this intentional? If so, whats the reasoning?

malc · 27 Mar 2005

Wow Frits, you've really been putting it through its paces!

(we're aiming for perfection, right? )

But of course 🙂

Q: I repeatedly mix up the use of the Page Up/Down keys. When I press the page up key, I expect to go 'up' in the schematic hierarchy, towards the navigator frame with 'top' written at the bottom (forgive me). What is the reasoning behind using the 'page down' key to go up?

Interesting that you should mention this. Jorge and I talked about this quite a bit. My initial reaction when programming it was to do it the way you're suggesting. However, when I came to use it I found myself expecting the opposite behaviour.

The reason for having PGUP go down the hierarchy is that the arrow on the PGUP key points towards the screen and gives a sense of going into a module. The opposite applies for PGDN.

I guess it depends on your mental picture. It was just natural for me to do it the way it is now. Maybe this is something that we'll have to have a switch for in the options - unless I'm the only person out there that thinks this way.

Anyway it's a good point so thanks for raising it.

The entry for SynthMaker in the 'Add or Remove Programs' control panel is labeled 'NSIS Example2'. It appears you need to replace the example project name created by the Nullsoft installer tool.

Nice spot.

When SM is starting up, the window client area is not painted for about 5 seconds, leaving only the window frame and (oddly enough) the shadow line between the toolbox and the navigator drawn on top of the windows desktop. It would be nicer to have the white background (which appears for a few seconds later on) from the start.

I'm a real stickler for these kind of details and this one has been on my todo list for ages. I spent a while trying to work out why it was happening and in the end had to stop and do something 'more important' - you know how it is.

Anyway this really annoys me. It's there every time I run the software so rest assured it will get fixed soon. Just hard to justify looking at such details when we can't do things like ASIO yet 😉

Regarding the other graphics bugs, many thanks. I didn't know about those so I will add them to the list.

The way you were describing them instantly brought a classic Tommy Cooper joke to mind:

"Man goes to the doctors. He says, doctor it hurts when I do this. Doctor says, well don't do it then". 🙂

Anyway, please do do it (double do intentional), it's great to have someone poking at all the nooks and crannies 😀

malc · 27 Mar 2005

Was the Freq to Pitch component introduced in g? May be one for Jorge this, I've been out of the loop a bit over the weekend.

Zynewave · 27 Mar 2005

I spent a while trying to work out why it was happening and in the end had to stop and do something 'more important' - you know how it is.

Anyway this really annoys me. It's there every time I run the software so rest assured it will get fixed soon. Just hard to justify looking at such details when we can't do things like ASIO yet

Yes, I know how it is. I also prefer having ASIO instead of a white screen during startup 😀 But would a simple UpdateWindow() immediately after creating the main window not do the trick? Or are you using MFC?

kingtubby · 28 Mar 2005

Zynewave wrote: Q: I repeatedly mix up the use of the Page Up/Down keys. When I press the page up key, I expect to go 'up' in the schematic hierarchy, towards the navigator frame with 'top' written at the bottom (forgive me). What is the reasoning behind using the 'page down' key to go up?

I have to agree with Frits on this point.

Mart

Shifrin · 28 Mar 2005

kingtubby wrote: Zynewave wrote: Q: I repeatedly mix up the use of the Page Up/Down keys. When I press the page up key, I expect to go 'up' in the schematic hierarchy, towards the navigator frame with 'top' written at the bottom (forgive me). What is the reasoning behind using the 'page down' key to go up?

I have to agree with Frits on this point.

Mart

And I'll have to agree with Frits and Mart 🙂

Maybe you could make it an option in the preferences Malc? Or your won internal build with it the 'right' way around for you 😉

Shif.

rl · 28 Mar 2005

Shifrin wrote: And I'll have to agree with Frits and Mart 🙂

I also opt for PGDOWN to go DOWN the hierarchie.

I would also like to have a "move into module in new window" option. Then I could have some "non maximized" windows open simulataneously

BTW: in 0.9.2h the d,f,s,i,o,... hotkeys do not work in example.osm (but in other schematics they do)

Shifrin · 28 Mar 2005

rl wrote: BTW: in 0.9.2h the d,f,s,i,o,... hotkeys do not work in example.osm (but in other schematics they do)

This couldn't have something to do with the 'PC Keyboard' being used for MIDI input could it? As when it is those hotkeys won't work! Just an idea 😉

Shif.

malc · 28 Mar 2005

Thanks all,

I can see exactly the point you're all making re. the PGUP/DN keys so I'll change it so that the default behaviour suits the majority and also make it an option to have it work the opposite way if your mind just happens to work like mine 😉

rl wrote: BTW: in 0.9.2h the d,f,s,i,o,... hotkeys do not work in example.osm (but in other schematics they do)

Shif is right here, the keyboard shortcuts for adding components will not work if PC Keyboard is selected on the MIDI In component.

This is a conflict we are aware of and it's on the list of issues to be sorted out.

malc · 29 Mar 2005

Zynewave wrote: But would a simple UpdateWindow() immediately after creating the main window not do the trick? Or are you using MFC?

Err...yes. That sorts it nicely! I was falling into the trap of looking for something far more complicated. Now, where's that embarrased smiley...

Thanks muchly.