Why don't I have access to all the feedback drop-down options?

Laura,

Please make sure you are using either the multiple choice questions template or the word bank. (and not the multiple response or any other question type). Those are the only two with which those options are available.

Thanks, Charles. That helps explain part of my issue.

However, I created a question that's multiple response and the feedback option in the toolbar defaulted to none. I want to change it to By Question and there's no option in the drop-down box to do so. It's just blank except for the None option. I know I can include feedback by answer on a m/r question! I just can't figure out what's wrong with my toolbar functionality. Still looking for some help with that.

So just to confirm, you don't have a "By Question" choice in the Feedback field of the Multiple Response Question like this...

Correct. This is what I see for the feedback drop-down.

And this is what I see for the score drop-down.

 They're both just blank.

Well that isn't good. You may want to try to go to your Quiz Properties and make sure the "Provide Feedback by Default" box is checked. But still it should be showing regardless. Since you have already reinstalled, I am going to bring this to the attention of the Articulate help desk folks. It will probably require a more technical fix.

Hi Laura,

It looks like your DPI is set to 120 instead of 96.  Please see the following to resolve the issue:

http://www.articulate.com/support/quizmaker09/kb/?p=95

Wow, that worked, Brian! Thanks.

Thanks for confirming that it worked for you!

Unbelievable that you expect people to change their preferred dpi setting to suit QM (and Engage, I think) to 96 rather than supporting 120 (or other custom) dpi. One purpose of Microsoft offering this choice to users is accessibility. I for one cannot cope at all with 96 on large monitors (which I need for work purposes). More to the point, no other app that I use causes this erratic behaviour.

Surely this is something that requires an urgent fix?! (It certainly doesn't rate as a "feature request"!)

Hi Ben,

I apologize for the inconvenience.  However, the Articulate software does not currently support 120 DPI.  If you'd like to see that added in a future release, please submit it as a feature request to us:

http://www.articulate.com/support/contact/feature/

Hi Brian

Thanks for your quick reply (always a welcome proclivity from the Articulate support people).

I won't submit a feature request, because, as I intimated, this cannot reasonably be argued to be "feature" to be requested by a customer. It is pretty standard (not even "best") practice for software developers and should be one of the things that gets included in early (alpha!) versioning. As I said, I have not experienced any other of my many apps (large and tiny) failing in this area.

It's not as though high-dpi usage is a new thing. It went through its worst anxieties in the mid-noughties and has since 05-06 n pretty generally standard in all development houses, small and large. 

It seems as though your backroom fellows have been remiss in this area and may need to do some urgent homework.

Ben

You could perhaps press them to take a look at this seminal paper from 2001 (yes, 2001!) (And there’s much else, since.)

How to Write High-DPI Applications

http://msdn.microsoft.com/en-us/library/ms969894

Nick Kramer, Microsoft Corporation

March 2001

 QUOTE:

"...Does your application work on high-density displays? Probably not. The standard computer monitor today has a display of about 96 dots per inch (DPI), and most applications assume that they are running on a 96-DPI display. But that’s an increasingly dangerous assumption.... [[AHEM, this was written ten years ago!]] 

 “…Applications without high-DPI capability will range from ugly to unusable, depending on the application and the DPI. Most applications that have large font support are disproportionate but usable at 130 DPI. At 200 DPI, the same application is unusable. Sometimes the application will be uniformly smaller, but more often some elements will be drawn at the correct size (say, if the application uses DEFAULT_GUI_FONT, which gets bigger as the DPI grows), while other parts shrink..." [etc.]

They could also refer to

How to Ensure That Your Application Displays Properly on High-DPI Displays

http://msdn.microsoft.com/en-us/library/dd756596%28VS.85%29.aspx

Writing High-DPI Win32 Applications

http://msdn.microsoft.com/en-us/library/dd464660%28VS.85%29.aspx

And a series of Tutorials about Writing High-DPI Win32 Applications

http://msdn.microsoft.com/en-us/library/dd464646%28VS.85%29.aspx

Hi Ben,

Yes, I've submitted this as a feature request to our development team.  Thanks!

Thanks Ben.

Thanks everyone!  I was having the same issue as Laura and could not figure out why.  But I do have to echo Ben.  Really annoying to have your DPI much smaller than that which is visually comfortable.  Hopefully it will be fixed in the future.