Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bitmap relative path #75

Closed
wxfbint opened this issue Dec 18, 2010 · 5 comments
Closed

Bitmap relative path #75

wxfbint opened this issue Dec 18, 2010 · 5 comments
Assignees
Labels
Milestone

Comments

@wxfbint
Copy link

wxfbint commented Dec 18, 2010

Migrating this bug from the old bug tracker.

I have my source located in a directory called "Source", my final executable builds to a directory called "Bin", and images are found in "Bin/Data/Images"; this means that any paths in the automatically generated code look like "../Bin/Data/Icons/" due to it exporting the paths relative to the code export location.

This actually works ok providing that the executable is ALWAYS in a directory called "Bin", my suggestion would have been to have two paths, one for where you wanted the exported code to be sent (in my case "Source"), and another for your executables working directory (in my case "Bin"),

Then the exported code could use wxTheApp->GetPath() followed by the image location relative to the working directory set.

Example:
working path = Bin/
image path = Bin/Data/Images/add.png
Exported code: wxTheApp->GetPath() + wxT("/Data/Images/add.png")

Reported by: *anonymous

@wxfbint
Copy link
Author

wxfbint commented Dec 18, 2010

I'm going to raise the priority of this if you don't mind. The original bug was raised over a year ago now, and this problem continues to cause me issues when working with images. I really can't imagine it being that hard to fix.

Original comment by: *anonymous

@wxfbint
Copy link
Author

wxfbint commented Dec 18, 2010

  • priority: 5 --> 7

Original comment by: *anonymous

@wxfbint
Copy link
Author

wxfbint commented Sep 4, 2012

Bumping and raising priority again. Was this ever addressed?

Note that there are two other bugs about this same issue: 3142680, 3142799.

Original comment by: *anonymous

@wxfbint
Copy link
Author

wxfbint commented Sep 4, 2012

  • priority: 7 --> 8

Original comment by: *anonymous

@wxfbint wxfbint self-assigned this Sep 3, 2016
jhasse pushed a commit that referenced this issue Feb 15, 2019
#496)

Python: Add wrapper function to bitmap paths for easier runtime-path configuration. Addresses #204 #104 #75 #78
@jhasse
Copy link
Member

jhasse commented Feb 15, 2019

Fixed by #496.

@jhasse jhasse closed this as completed Feb 15, 2019
@jhasse jhasse added this to the 3.9.1 milestone Feb 15, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants