Comments by Kyudos - CodeProject

Kyudos 29-Oct-23 18:01pm View

Deleted

I have (I hope it goes without saying!) read the documentation, and checked everything I can about the structure. Bear in mind this is code for a commercial product that we purchased along with the DLL it supposedly represents. It obviously works as intended in the DLL - but not in my rebuilt version. Hence my first assumption is that the problem relates to how I've reconstructed the build project, rather than the the code itself. As I said, I've copied in other ChooseFont example code which similarly fails. Other common dialog stuff (printer, open, save etc.) all seems fine....I just seem to have an issue with the fonts...

Kyudos 29-Oct-23 18:01pm View

I have (I hope it goes without saying!) read the documentation, and checked everything I can about the structure. Bear in mind this is code for a commercial product that we purchased along with the DLL it supposedly represents. It obviously works as intended in the DLL - but not in my rebuilt version. Hence my first assumption is that the problem relates to how I've reconstructed the build project, rather than the the code itself. As I said, I've copied in other ChooseFont example code which similarly fails. Other common dialog stuff (printer, open, save etc.) all seems fine....I just seem to have an issue with the fonts...

Kyudos 10-Jul-23 19:33pm View

Yes, particularly if you are using the built-in customisation functions, controlled by the "bVistaStyle" flag in the constructor. As I may not have quite got over in the original post, the dialog does seem to be centred if you leave it at the default size. However, the resizable version remembers its size, so will not be centred if you make it bigger. This may also be affected by my customisation - adding extra controls changes the dialog size also.

Kyudos 9-Jul-23 19:32pm View

So is the `CWnd* pParentWnd` in the CFileDialog constructor just for backward compatibility? Is doesn't actually do anything? I would have thought connecting the file dialog to the application which created it would be an inherent part of its functionality?

Kyudos 23-Nov-21 15:37pm View

It's not SQL server. My app is an interface to MDB / ACCDB files, and part of that interface allows the user to run SQL queries through CRecordset classes and/or CDatabase::ExecuteSQL. In this case the CDBException is "Syntax error in FROM clause." (State:37000,Native:-3506,Origin:[Microsoft][ODBC Microsoft Access Driver])

Kyudos 21-Nov-21 16:02pm View

Thanks, I've tried that but it doesn't recognise the FROM clause. I've found I can connect directly to an old (Access 97) format MDB like this:
SELECT Components.Description FROM `C:\Users\me\Desktop\database.mdb`.Components
But it complains about the file format for newer databases.

Kyudos 18-May-21 22:04pm View

Thanks - my initial thoughts were along the lines of some mod 26 maths :)

Kyudos 18-May-21 18:57pm View

I was wondering if there was some secret formatting trick I didn't know about, but this will certainly do the business.

Kyudos 21-Feb-19 18:14pm View

Thanks for this. I looked into it and it would seem to do the trick. But it is also quite complex. So I might just hit my problem with a slow but reliable hammer in the odd cases where my bitmap doesn't work.

Kyudos 20-Dec-17 15:14pm View

Setting the background colour doesn't seem to work at all, even setting to red. Obviously the colours involved aren't that different, but they are different enough for me to notice. Don't think it's worth owner-drawing the panels just for this though.

Kyudos 23-Nov-15 19:14pm View

Did you figure this out? I have the same issue...
Edit:
...OK I Found the sample that shows how :)

Kyudos 23-Apr-15 17:48pm View

Thanks for the reply - but this doesn't seem to help. wofstream and ofstream give the same problem - suggesting it is not UNICODE that is the problem but x64...

Kyudos 23-Jan-14 6:20am View

Does it make any difference? Its only a border because that's what it was when I inherited it. Looked at this some more, it seems like the control still has the "normal" size when maximised, then gets the 'maximised' size when restored again.

Kyudos 22-Jan-14 14:38pm View

No, I'm asking what is different about Maximising or Restoring the window vs resize via drag. The drag resize causes my control to redraw correctly, the window operations don't.

Kyudos 22-Jan-14 14:37pm View

This is just the framework for the control - the actual contents of each canvas are drawn in code, hence I need to redraw when changing size. The height and width of the control are bound to its containing element (a border), which lives in a grid in the main window. When the app opens (Normal Window) the control renders correctly (contents centered on the DrawCanvas). If I Maximise, the DrawCanvas content doesn't resize or recenter, if I then Restore the content again redraws incorrectly.

Kyudos 20-Jan-14 22:34pm View

Ron, yeah an outlined arc segment. I could add another path with the two top and bottom arcs and the two straight end segments, but I wondered if there was a built in way to draw an 'outlined' line.

Kyudos 12-Jan-14 14:38pm View

Hi Alexander, Thanks for the answer, which I'm sure is absolutely correct, but I'm not sure helps me out. I'm trying to add some curved text (actually, several dynamically created labels, all curved) to another UserControl. I'm assuming you can use a UserControl inside a UserControl in WPF? I have a limited understanding of MVVM and XAML etc. - for small things like this I'm not convinced that the added complication is worth it!

Kyudos 15-Dec-13 19:25pm View

The wheel is actually a chart control (info by spoke length), so things (may) need some sort of dynamic sizing / positioning. Perhaps with the straightforward circular arcs, short-ish labels etc. I might get away with manual text modification (e.g., manually adding carriage returns etc.). Another thought occurs - I'll need to control the text colour too, for maximum visibility on different colour backgrounds...I have the sneaking suspicion this "easy" change is not quite so simple!

Kyudos 12-Nov-13 15:33pm View

I don't know if you're being deliberately obtuse, but I'll give you the benefit of the doubt... don't you think it is easier to find the tab you want if all tabs have different names, rather than all having the same name?

Kyudos 11-Nov-13 18:58pm View

I'm not sure I fully understand your misunderstanding. The language / platform isn't particularly relevant, but in this case C++. If I'm editing three dialogs, all the (admittedly, shortened) tabs show something like "Dialogs.rc - ... - Dialog". It would be much more useful if the tabs were titled IDD_DIALOG1, IDD_DIALOG2 and IDD_DIALOG3...

Kyudos 20-May-13 23:02pm View

No, that removes the file from the project, I want to remove it from the build. See (on a file) Right-click|Properties|General|Excluded from build

Kyudos 13-Aug-12 0:45am View

I suppose the question remains, and I'm not quite sure about this, DO I need a shell extension? I only want to set these four 'default' PIDSI values when I save my files. Is there no way that Windows 7 can set and show them without any messing? I don't need to be able to edit the properties in Windows Explorer - just see them.

Kyudos 12-Aug-12 23:26pm View

Actually, I wasn't.. but the likely outcome is I'll take it out completely until I can develop a robust solution that works on XP, Vista and Seven

Kyudos 26-Jul-12 20:04pm View

Jochen - this works great thanks - I'd mark it as the answer:)

Kyudos 14-Jun-11 22:45pm View

Isn't that the point of defining _CRT_SECURE_CPP_OVERLOAD_STANDARD_NAMES? So I don't have to fix all the functions calls?

Kyudos 14-Jun-11 21:17pm View

Is defining the overload macro supposed to suppress the warnings? Or do I need to define _CRT_SECURE_NO_WARNINGS too?

Comments by Kyudos (Top 26 by date)